Domain Gotchas

In this section, we'll explore some common gotchas and pitfalls that can arise when working with Data Connector 2.0. These pitfalls can lead to inaccurate reports if not considered.

Calculating XP

The correct way to count XP is not to simply do a SUM on the xp_earned column of the fact_learn_events table, as this will end up in double counting. For example, for course XP, we have both course_engagement and exercise_completed events with a non-null xp_earned value; both contain XP gained from completing an exercise, so including both would lead to double counting XP earned in courses.

To correctly count XP and have it match what is reported in the Groups tab, only use the following events:

• assessment_engaged

• course_engagement

• practice_engagement

• project_engagement

• b2b_onboarding_xp_boost

• alpa_onboarding

The sum of a user's XP in this table should not be expected to equal the total XP they have on the platform. This is because, in the Data Connector, admins can only see the activity that a user completed while they were part of the group. Any XP earned outside of the group—such as before joining, or after leaving—will not be reflected in this dataset.

Missing Content Items in dim_content

Not all events in the fact_learn_events table will have a corresponding content item in dim_content. This is because some content items may be hard deleted in our system, meaning they are permanently removed rather than being soft deleted or archived. As a result, any events tied to these deleted content items will no longer have a valid content_id reference in dim_content.

Despite this limitation, we still retain these events in the fact_learn_events table. These events represent real user activity, including time spent and XP earned, and are valuable for tracking engagement. When analyzing data, be aware that some events may not join to dim_content, but they remain important for understanding overall user behavior.