Rule Types and the Information Required
- Ben Clark
Rules built within Rule Designer are created for various purposes. To focus different types of Rules to the correct functionality we need apply a label identifying what they do and how they should be used. We call this label the Rule Type.
The Rule Type is automatically set by the selection of certain event queue Public templates. So if you choose an “Conversion event queue” your Rule will be identified as a Conversion Rule.
The current Rule Types and the event queues that identify them are shown below.
Rule Type | Definition | How is it defined? |
|---|---|---|
No selection | Default, any rule that does not fall into the scenarios covered by the other Rule Types. | Does not contain the Event Queues that identify it as a Influencer, Tracking, Conversion or Satisfaction Rule. |
Influencer | Rules that provide a decision or value back from Alterian CX that a calling system can use to make a active decision upon. This could be to show specific content or a specific email to send. Anything that has been designed to sway a user's behaviour would be assigned as an influencer Rule. These play a large part in the new Opportunity Matrix.
|  Influencer Rules are identified by the use of the Event Queue - Influencer Public Template in your rule. |
Tracking | Rules to track movement between locations but does not provide actionable decisions back. These Rules would be used where you are tracking the user's movement through a website, app or through various call scripts in a call centre. Tracking rules do not provide active responses back to the calling system it simply records where the user was when they were exposed to the Influencer Rules. Journey Analytics will show Tracking / Location rules. |  Tracking Rules are identified by the use of the Track Location Public Template in your rule. |
Conversion | Records 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 events are shown in Journey Analytics and are used in our success calculations. |  Conversion Rules are identified by the use of the Event Queue - Conversion Public Template in your rule. |
Satisfaction | These Rules allow the collection of Satisfaction scores, they do not influence behaviour or mark a conversion. The Events created by Satisfaction Rules are used in our business reporting to allow our users to identify processes that may not be working or to undertand broad levels of satisfaction wiht the brand. |  Satisfaction Rules are identified by the use of the Write Satisfaction Public Template in your rule. |