Migrating from Data Connector 1.0

If you are migrating from the previous version of Data Connector, this section is for you.

Motivation

We are constantly improving our Enterprise reporting to gain insights and make tracking your users' progress on our platform even more straightforward.

The most significant change in this 2.0 version is the data model. We have simplified the data structure to make it more intuitive and easier to query.

We have reduced the number of tables, added mobile usage data, and included metric tables to make it easy to build a dashboard using your organization's BI tools.

Additionally, by moving to this improved data model, Data Connector now uses the same data as the rest of our Enterprise reporting. This allows for faster iteration and ensures that every report matches everywhere.

What is changing?

Data Model

In version 1.0, we had a robust data model allowing a lot of granularity and detail. The downside is that it had a steeper learning curve.

We have simplified the model, going from this:

Data Connector 1.0 Data Model

To this:

Data Connector 2.0 Data Model

Finding the correct table for your queries is now quicker and easier!

Improvements

We have reduced the number of tables from 29 to 13, added mobile usage data, and included metric tables to make it easy to build a dashboard using your organization's BI tools.

	Data Connector 1.0	Data Connector 2.0
Mart Tables	29	13
Metric Tables	0	3
Mobile Data	No	Yes
Queries that require joins	ALL	~25*

Sample queries (1.0 vs. 2.0)

Comparing the SQL code required to answer the same question on both data models illustrates why we decided to change.

For example, let's calculate the total time in Learn content (assessments, courses, practices, and projects) between January 15 and February 14, 2025.

On Data Connector 1.0, you needed to do this:

WITH time_per_type AS (
        SELECT sum(time_spent) AS total_time_spent
        FROM data_connector_1234.exercise_fact
        WHERE date_id BETWEEN 20250115 AND 20250214
        ​
        UNION ALL
        ​
        SELECT sum(time_spent) AS total_time_spent
        FROM data_connector_1234.practice_fact
        WHERE date_id BETWEEN 20250115 AND 20250214
        ​
        UNION ALL
        ​
        SELECT sum(time_spent) AS total_time_spent
        FROM data_connector_1234.project_fact
        WHERE date_id BETWEEN 20250115 AND 20250214
        
        UNION ALL
        
        SELECT sum(time_spent) AS total_time_spent
        FROM data_connector_1234.assessment_fact
        WHERE date_id BETWEEN 20250115 AND 20250214
)
​
SELECT sum(total_time_spent) AS time_spent_seconds
FROM time_per_type

The granularity built into the model made it harder to answer more general questions that are frequently asked.

With Data Connector 2.0's model, the same question can be answered with the following query:

SELECT sum(duration_engaged) AS time_spent_seconds
FROM data_connector_1234.fact_learn_events
WHERE occurred_at BETWEEN TIMESTAMP '2025-01-15 00:00:00' AND TIMESTAMP '2025-02-14 23:59:59'

What do I need to do to switch?

Data Connector 2.0 still uses AWS S3 buckets to hold your organization's data, so connecting to the new version is straightforward.

For more details, please refer to our Getting started with Data Connector and Using Data Connector sections.