Event Queue - Tracking
- Ben Clark
For my Campaign Rules I need to be able to identify where users are clicking and what they are clicking through. This Template allows the precise details needed for Campaign tracking to be collected.
If you are tracking movement Emails, SMS, banners etc where the location does nto change this is the Template you should use.
Input Data
Field | Description | Example |
|---|---|---|
AlterianCX_cxid | Standard CXID created by the Get CXID Public Template and passed into the Rule flow |
|
AlterianCX_conversationid | Standard Conversation ID created by the Get CXID Public Template and passed into the Rule flow |
|
AlterianCX_isknown | Taken from the original call into the Rule. Is the information we have on this user enought to positively identify them | Y |
AlterianQueue_channel | What Channel is this Rule running on, Web, Call Centre, POS etc. Passed through in the original call to Alterian Journey Orchestration | Web |
Is Control | Standard field created to allow us to understand whether the rule and the decisions presented were made to an individual in the control group for this rule or not. | Y / N |
category | Category of the event | Email, SMS |
AlterianQueue_location | Taken from the original call into the Rule. What location this rule was called from. This allows the Journey Analytics to understand the Rules a individual has moved through. | |
AlterianQueue_position | What position in the specific location this event occured. For tracking Rules this is used for tracking emails. | email banner |
rule name | Name of the Rule being called. Automatically Populated. | Sales Personalisation Offers |
engagementScore | Engagement score generated by this Rule. Populated automatically if the Engagement Score or Content Group Public Templates are used | 4 |
event datetime | Date and time when the Rule was called. Automatically Populated. |
|
AlterianCX_inboundCampaignName | This is taken from the standard utm_campaign tag and renamed for Alterian CX use. Normally created by the parse campaign tracking tags Public Template. | Summer2022Campaign1 |
AlterianCX_inboundSource | This is taken from the standard utm_source tag and renamed for Alterian CX use. This is the minimal subset of values we accept. If the utm_source is not present we remove any remaining UTM as these are likely to be incorrect or invalid. Normally created by the parse campaign tracking tags Public Template. | |
AlterianCX_inboundMedium | This is taken from the standard utm_medium tag and renamed for Alterian CX use. Normally created by the parse campaign tracking tags Public Template.
| |
AlterianCX_inboundTerm | This is taken from the standard utm_term tag and renamed for Alterian CX use. Normally created by the parse campaign tracking tags Public Template. | holidays |
AlterianCX_inboundContent | This is taken from the standard utm_content tag and renamed for Alterian CX use. Normally created by the parse campaign tracking tags Public Template. | Acadianholidayslink |
Parameter | Description | Example |
|---|---|---|
AlterianCX_defaultQueue | Your standard event queue | acadiantravel/prod/queue1 |
AlterianQueue_customerttributeTable | The Parameter (AlterianQueue_customerAttributeTable) can reference a Customer attribute table with the CXID as the key. Once configured ,each time an event is passed to Alterian Journey Analyics any data from the Customer Attribute Table linked to the corresponding CXID will also be passed through in the same event . |
|
Processing
Takes the fields as mapped and pass these into a queue that feeds the Journey Analytics and Success and BI reports.
Lookup the CXID in any linked Customer Attribute Table and pass any vaues within this table into the queue to allow better reporting and filtering
Output Data
Field | Description | Example |
|---|---|---|
|
|
|
|
|
|