◾Smartico DWH \ Gamification views
This page is describing dimensional and fact tables related to the gamification module
Last updated
This page is describing dimensional and fact tables related to the gamification module
Last updated
Note that Bonus related structures are used by both - CRM & Gamification modules and described in CRM Views
The table contains information about missions and badges.
Column | Type | Note |
---|---|---|
.The table contains information about mini-game templates
Column | Type | Note |
---|---|---|
The table contains information about missions and badges.
The table contains information about missions and badges.
List of all bonus templates with their label, id, type and name.
The table contains information about tournaments and tournament instances.
Lookup table with possible sources for the points transactions.
The table represents the history of all completed missions & badges.
Partitioned by: create_date
Data availability: last 180 days by create_date
Primary key: ach_completed_id
Example of the query returning a count of users completed missions in the last 3 days
The table represents the history of all opt-ins in the missions that require explicit opt-ins to participate.
Partitioned by: create_date
Data availability: last 180 days by create_date
Primary key: ach_id, user_id, create_date
Example of the query returning up to 1000 rows of missions that were active in the past 30 days with counts of opted in customers and customers that completed the mission in that period.
The table represents facts of prizes claiming for the missions for which a claim is required.
Read more about "claiming" in the Missions guide.
Partitioned by: create_date
Data availability: last 180 days by create_date
Primary key: ach_completed_id
The table represents all changes in the gamification points
Partitioned by: create_date
Data availability: last 180 days by create_date
Primary key: NA
Example of query showing the source of the points credit and deposit
The table represents mini-game gameplay results.
Partitioned by: create_date
Data availability: last 180 days by create_date
Primary key: spin_id
The table contains information about various tournaments and relevant analytics events.
Each tournament can be represented in the table multiple times, where each time it reflects different tournament instances (different runs).
Note that there is data nested under progress.
Partitioned by: event_time
Data availability: last 180 days by create_date
Primary key: id
This example provides a comprehensive summary of each tournament instance, focusing on score distributions and rule applications. It allows for easy comparison between different tournament instances and can help identify patterns in performance and rule usage across various tournaments.
The results are ordered by tournament_id and then tournament_instance_id, making it easy to view all instances of a particular tournament together. This structure can be particularly useful for analyzing trends or changes in tournament performance over time or across different instances of the same tournament.
The table represents all purchases in the store.
Partitioned by: create_date
Data availability: last 180 days by create_date
Primary key: transaction_id
The table represents the UI interactions of users with the Gamification widget
Partitioned by: create_date
Data availability: last 180 days by create_date
Primary key: NA
ScreenNameIds:
The table represents the log of level upgrades/downgrades for each user.
Partitioned by: fact_date
Data availability: last 180 days by fact_date
Primary key: level_change_id
Column | Type | Note |
---|---|---|
Column | Type | Note |
---|---|---|
Column | Type | Note |
---|---|---|
Column | Type | Note |
---|---|---|
Column | Type | Note |
---|---|---|
Column | Type | Note |
---|---|---|
Column | Type | Note |
---|---|---|
Column | Type | Note |
---|---|---|
Column | Type | Note |
---|---|---|
Column | Type | Note |
---|---|---|
Column | Type | Note |
---|---|---|
ID | Name of screen |
---|---|
Column | Type | Note |
---|---|---|