Influencer Rules, Templates and Fields Required
- Ben Clark
Influencer Rules provide a decision or value back from Alterian CX that a calling system can use to make a active decision upon. To be able to make this decision the rule needs to understand “who” is being exposed to the rule. This allows it to make the optimal decision where more then one decision is available and to record that this individual was exposed to this rule for success reporting purposes.
These Rules should have the Rule Type “Influencer” so they can be shown and mapped correctly in the Opportunity Matrix.
Templates Required
Templates Required | Public Template | Description | Required |
|---|---|---|---|
Realtime Input Step | Yes | Normally 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 |
Realtime Output Step | Yes | Provides a response back to the calling solution | Either this or Other Active Step |
Other Active Step | Maybe | Provides an Active “Response” triggered by this rule, Email Sent out, Other API call, Direct Mail sent, Call Centre triggered etc. | Either this or Other Active Step |
Event Queue - Influencer | Yes | Allows the information generated by the Influencer Rule to be passed into Journey Analytics and the labelling of this Rule as an Influencer 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 through 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. |