Your Rules can run independently within Alterian Journey Orchestration. In most cases however you will want the running of the rule, the information contained within the rule and the CX decisions created to be used in your reporting. This could be your Journey Analytics, your success calculations or our integrated CX Reports
Getting the required information into your reporting is easy. A Public Tempalte exists called Event Queue
Input Data
Field | Description | Example |
|---|---|---|
cxid | CXID as created by the use of the GET CXID Public Template | |
conversationid | Created by the GET CXID Public Template and used in billing | |
is known | Taken from the original call into the Rule. Is the information we have on this user enought to positively identify them | Y |
business goal | What Business Goal does this Influencer Rule meet. Automatically Populated when a rule is mapped in the Opportunity Matrix. | Increasesales |
opportunity group | For Future Use. Not Mandatory | |
opportunity name | For Future Use. Not Mandatory | |
event type | What type of event this Rule is. Influencer, Tracking or Conversion. Added in Rule Designer. | Influencer |
channel | What Channel is this Rule running on, Web, Call Centre, POS etc. Passed through in the original call to Alterian Journey Orchestration | Web |
initiative | What Inititative this Influencer Rule meets. Automatically Populated when a Rule is mapped in the Opportunity Matrix. | PersonalisePOS |
initiative step | For Future Use | |
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. | acadiantravel.co.uk/sales/salespage1 |
rule name | Name of the Rule being called. Automatically Populated. | Sales Personalisation Offers |
rule group | Then Rule Group the Rule was in if any when the rule was called. Automatically Populated. | Sales Offers Carousel |
control group | Is the Individual (by CXID) exposed to this Rule in the Control Group for the Rule. Allows us to calculate success. | Y |
priority score | If the Rule was called as part of a Rule Group what was the priority score of this the winning Rule. Automatically Populated. | 12 |
event datetime | Date and time when the Rule was called. Automatically Populated. | |
cx decision | What CX Decision was passed through by the Rule | offer12, 1233, Gold |
cx output step | For Future Use. Not Mandatory | |
cx engagement | Engagement score generated by this Rule. Populated automatically if the Engagement Score or Content Group Public Templates are used | 4 |
Configuration
The configuration item is focused on identifying the queue to pass the events into.
Parameter | Description | Example |
|---|---|---|
AlterianCX_defaultQueue | location of your reporting queue. We would recommend that this is setup as a Forced Global Parameter so this does not need to be set in each Rule. | cxqueue1 |
Processing
This Template passes information linked to the running of Rules into the Alterian backend.
Output Data
Not fields are created by the Event Queue. All Fields pass through for use further down the Rule flow.