Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
As part of building Templates, Rules, Parameters etc, the key consideration for Data Analytics is ensuring that the Rules capture the correct data to populate the Event History Schema to ensure it can be utilised in the Data Analytics layer.
The following items all analyse this CX Data Analytics Event History Schema, and this schema is the only repository for Data Analytics
Data Transformation
Journey Discovery
Journey Analytics/Journey Visualisation
Standard Dashboards (shipped with the CX product)
Bespoke Dashboards (any Dashboards requested by End Users)
If these Rules are not constructed correctly and do not collect the correct data, the Analytics will not meet the needs of the Analysts.
The standard CX Data Analytics Event History Schema, is comprised of a single table in the back end database, which can logically be divided into two sections:
Event History Data
Customer Attribute Data
IMPORTANT NOTES
There is no direct access to this table but rather, the column data is exposed or analysed in the appropriate area of the UI depending on the analytics being provided.
Data in the columns can ONLY be populated via the use of Rules. Data here cannot be populated with external data sources.
Any Bespoke Dashboards created by Alterian Professional Services or via an Alterian Partner can only be created based on the columns listed below.
Event History Data
This data is a standard named set of column data that is populated by the Rules that are created.
Column Name
Details
Column Name
Details
Event DateTime
Auto-populated by the application
Captured for all Rule Types
Captures the Date/Time of the Event
Captured in UTC
Format CCYYMMDD HHMMSS
Event Type
Auto-populated by the application
Captured for all Rule Types
Defines classification of the Rule Type
Value set automatically based on Rule construction and is always one of:
Requires manually configuration to capture correct data
Captured on Conversion Rules only
May be a specific monetary amount if used as part of a sales process or an implied value if used for a conversion that does not naturally have a monetary value
Primary Value
Not currently utilised - internal only
Secondary Value
Not currently utilised - internal only
Service Cost
Requires manually configuration to capture correct data
Captured for Influencer Rules only
Configuration at a tile level
Service Cost Detail
Not currently utilised - internal only
Offer Cost
Requires manually configuration to capture correct data
Captured on Influencer and Conversion Rules only
Allows an Offer Cost to be passed in with the event allowing better success calculations.
Configuration done using the Offer Management Public Template and will auto map if this Public Template is used, or can me manually input
Once Customer Attributes have been defined and populated into the CX cache, the values for each Customer Attribute are then passed to the Event History with every Event.
These columns are typically defined by the Alterian Client based on their needs, but the key point is, as mentioned previously, that any analytics that are required, either filtering of the Journey Visualisation or to populate a bespoke Dashboard. If the Customer Attribute is not defined in the Customer Attribute Schema, it will not be available to any Analytics within the CX platform.