Event Queue - conversion
Event Queue specifically created for Conversion Rules. This differs from the other event queues by providing the opportunity to map in conversion specific fields.
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. Automatically Populated based on Event Queue used. In this case Conversion. | Conversion |
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. | |
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 |
The fields below are specific to the event queue - conversion public template. This Template should be used when collecting events linked to conversions. | ||
Offer Code | Allows an Offer Code used by the user to be passed in with the event allowing better success calculations. Offer Code is provided by the Offer Lookup Public Template and will auto map if this Public Template is used. | birthday1 |
Offer Cost | Allows an Offer Cost to be passed in with the event allowing better success calculations. Offer Cost is provided by the Offer Lookup Public Template and will auto map if this Public Template is used. |
|
Monetary Value | Primary way to indicating the success of the conversion- this 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 | For Future Use. Not Mandatory |
|
Secondary value | For Future Use. Not Mandatory |
|
Configuration
Allows addition of queue location.
Parameter | Description | Example |
---|---|---|
AlterianCX_defaultQueue | location of your reporting queue | cxqueue1 |
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.