This section provides detailed descriptions for all data points related to user interaction and engagement in Thrive. Each article includes the table name, the columns within each table, the data type for each column, and a user-friendly description of what each column represents.
Table Relationships
To help you visualise how the tables connect, the following Entity-Relationship Diagram (ERD) serves as a visual map of the tables and their primary and foreign keys.
erDiagram
"FCT_ENGAGEMENT_RECORD_STORE_ACTIVITY_VIEWED" ||--o{ "FCT_ENGAGEMENT_RECORD_STORE_ACTIVITY" : "includes"
"FCT_RECORD_STORE_ACTIVITY_EARNED" ||--o{ "FCT_ENGAGEMENT_RECORD_STORE_ACTIVITY" : "includes"
"FCT_ENGAGEMENT_RECORD_STORE_ACTIVITY_SEARCHED" ||--o{ "FCT_ENGAGEMENT_RECORD_STORE_ACTIVITY" : "includes"
"FCT_RECORD_STORE_ACTIVITY_PROGRESSED" ||--o{ "FCT_ENGAGEMENT_RECORD_STORE_ACTIVITY" : "includes"
"DIM_USER_SERVICE_USERS" ||--o{ "BRG_AUDIENCE_PEOPLE_MANAGER_PERMISSIONS" : "manages"
"DIM_USER_SERVICE_USERS" ||--o{ "BRG_USER_AUDIENCE" : "member of"
"DIM_USER_SERVICE_USERS" ||--o{ "DIM_USER_SERVICE_USERS_ADDITIONAL_FIELDS" : "extends"
"FCT_ENGAGEMENT_RECORD_STORE_ACTIVITY" }o--|| "DIM_CONTENT_SERVICE_CONTENTS" : "activity"
"FCT_ENGAGEMENT_RECORD_STORE_ACTIVITY" }o--|| "DIM_USER_SERVICE_USERS" : "user activity"
"FCT_LEARNING_HISTORY_SERVICE_COMPLETIONS" }o--|| "DIM_CONTENT_SERVICE_CONTENTS" : "completions"
"FCT_LEARNING_HISTORY_SERVICE_COMPLETIONS" }o--|| "DIM_USER_SERVICE_USERS" : "user completions"
"DIM_AUDIENCE_SERVICE_AUDIENCES" ||--o{ "BRG_USER_AUDIENCE" : "has users"
"DIM_AUDIENCE_SERVICE_AUDIENCES" ||--o{ "BRG_AUDIENCE_PEOPLE_MANAGER_PERMISSIONS" : "manages"
"DIM_CONTENT_SERVICE_CONTENTS" ||--o{ "BRG_CONTENT_TAGS" : "tagged with"
FCT_ENGAGEMENT_RECORD_STORE_ACTIVITY {
text Activity_ID PK
text Content_ID PK,FK
text User_ID PK,FK
text Tenant_ID PK,FK
}
FCT_ENGAGEMENT_RECORD_STORE_ACTIVITY_VIEWED {
text Activity_ID PK, FK
text Content_ID PK,FK
text User_ID PK,FK
text Tenant_ID PK,FK
}
FCT_ENGAGEMENT_RECORD_STORE_ACTIVITY_SEARCHED {
text Activity_ID PK, FK
text Tenant_ID PK,FK
}
FCT_LEARNING_HISTORY_SERVICE_COMPLETIONS {
text Completion_ID PK
text Content_ID PK,FK
text User_ID PK,FK
text Tenant_ID PK,FK
}
FCT_RECORD_STORE_ACTIVITY_EARNED {
text Activity_ID PK, FK
text Content_ID PK,FK
text User_ID PK,FK
text Tenant_ID PK,FK
}
FCT_RECORD_STORE_ACTIVITY_PROGRESSED {
text Activity_ID PK, FK
text Content_ID PK,FK
text User_ID PK,FK
text Tenant_ID PK,FK
}
DIM_USER_SERVICE_USERS {
text User_ID PK, FK
text Tenant_ID PK
}
DIM_USER_SERVICE_USERS_ADDITIONAL_FIELDS {
text User_ID PK,FK
text Additional_Field_Key PK
text Tenant_ID PK,FK
}
DIM_AUDIENCE_SERVICE_AUDIENCES {
text Audience_ID PK
text Tenant_ID PK,FK
}
DIM_CONTENT_SERVICE_CONTENTS {
text Content_ID PK
text Tenant_ID PK
}
BRG_USER_AUDIENCE {
text User_ID PK,FK
text Audience_ID PK,FK
text Tenant_ID PK,FK
}
BRG_CONTENT_TAGS {
text Content_Tag PK
text Content_ID PK,FK
text Tenant_ID PK,FK
}
BRG_AUDIENCE_PEOPLE_MANAGER_PERMISSIONS {
text Audience_ID PK,FK
text Manager_User_ID FK
text Tenant_ID PK,FK
}Note:
Underscores are included in the ERD for syntax compliance, but the corresponding field names in Snowflake do not include the underscore.