Conversion Rules, Templates and Fields Required
- Ben Clark
Conversion Rules record an action has occurred but does not provide anything back to influence the decision or action made. This Rule is recording the conversion has occurred it does not alter or attempt to alter the outcome, it simply reports on it.
These rules are shown in Journey Analytics and are used in our success calculations . They are mapped to Initiatives forming the conversions for them.
Examples could be the sales thank you page or PDF download confirmation page.
Conversion Rules may create and pass through Conversion Rule specific fields such as Monetary Value, Primary Value and Secondary Value.
Templates Required
Templates Required | Public Template | Description | Required |
|---|---|---|---|
Realtime Input Step | Yes | Often specific to each Rule. This provides the method for the calling solution to contact Alterian CX and provides clarity on the fields required in each call. | Yes |
Get CXID | Yes | Identifies the Individual, matches them to previous ids and creates values to aid future CX decisions and reporting. | Yes |
Event Queue - Conversion | Yes | Allows the information generated by the Conversion Rule to be passed into Journey Analytics and allows the identification of this Rule as a Conversion rule | Yes |
Fields Required
Field | Description | Required |
|---|---|---|
ChannelAgentid(#) | At least one identifier should be provided. If more can be provided this will increase the chance of a identification match and better more accurate data. | Mandatory, at least one ChannelAgentID should be provided |
AlterianQueue_location | Where the Rule is being called from. Provided via parameter or automatically by using the referrer. | Optional, If being provided by separate Tracking / Location rules. Please provide if available |
AlterianQueue_Position | The position within the Location where the Rule was being used. This is important to understand whether a Rule running in a Hero banner is more successful than a Rule running in a footer banner . | Optional, future developments will use this to augment Journey Analytics so please provide if it is available. It will also be used in success calculations if provided. |
AlterianQueue_Channel | Channel in which the Rule is being called. Rules can be generically used through multiple channels we need to identify which one this call is coming from. | Mandatory |
AlterianCX_isknown | Is this identification value for a person known to the brand? | Optional, providing this will improve reporting |
AlterianCX_referrer | Referrer | Optional, providing this will improve reporting. This value will be used as the location if one is not provided. |