Configuring Rules

Each event supports a specific set of actions as specified in the following table. Hence, it is important to understand what actions can be used for each event. All action names are self-explanatory.

In the following example, you can see how to configure rules for a sample use case in TransactionAdd event.

Note: TransactionAdd event consists of 3 parent sets by default. The first parent allows creating rules based on the transaction add activity, the second one for creating rules tracker strategies and the last one for creating rules on the transaction finish activity.

Use Case:

1. Issue points of 10% the transaction amount to the loyalty customers not in base tier only when the transaction amount >= $200
2. Issue 50 bonus points if the customer's cumulative transaction amount in the last 365 days exceeds $10,000 with the current transaction
3. Send transaction details to the customer through email

Approach:

1. Step 1: Create two points allocation strategies – one with 10% prorated allocation type and another with 50 points fixed allocation type
2. Step 2: Create a tracker condition to track the last 1 year’s transaction amount
3. Step 3: Go the EventsView page and set the Event as TransactionAdd
4. Step  4: In the first parent rule set, write the rule for the transaction add activity – tier>=0 & transaction value > 200 - and set the respective points allocation action
5. Step 5: In the second parent rule set, first create a forward set, and set evaluate  tracker in the subset and then write tracker based condition and set the points allocation action in the next subset
6. Step 6: In the last ruleset, set Send Email action and configure the email template
7. Step 7: Save the changes and Reconfigure the loyalty program

Important points to consider while writing rule expressions:

• Use Tracker Strategies for duration based conditions. For example, transactions made in the last 365 days, points earned in the last 200 days and so on.
• Always set the Action of the parent rule set corresponding to tracker event as Forward to Set
• To evaluate a condition even before tracking the value write in the child rule set and to evaluate conditions on the tracked value use the actual tracker set (3rd level)
• If points allocation type is prorated, choose whether to consider the percentage of bill amount or tracker value. If bill amount, choose current event, if tracker, choose current aggregate or previous aggregate