Trackers let you track a specific value for a certain period. It could be bill amount, gross bill amount, line-item count, line-item quantity, line item price, and customer visits. You can create tracker strategies and define rule sets based on these entities.

Trackers are executed based on the TILL time but not based on the time specified for a transaction.

This topic covers how to:

  • Create tracker strategies - this includes creating tracker strategies with different tracker cases.
  • Configure rule sets for tracker strategies - this includes creating a tracker, assigning a tracker strategy to the tracker, and configuring rules for each tracker case.

Create a tracker strategy

To create a tracker strategy, follow these steps.

  1. On the loyalty program configuration page, go to the Trackers tab.

  1. Click Create Tracker Strategy.You will see the Tracker Strategy pop-up screen

  1. Configure each field of the tracker strategy based on the descriptions provided in the following table. You can create multiple tracker cases in a tracker strategy. 
OPTIONDESCRIPTION
Tracker NameSpecify a meaningful name for the current tracker strategy. Example: Transactions_month.
ModeChoose the window (duration) based on which you wish to evaluate the tracker case.
  • Moving Window: In Moving Window mode, when a customer makes a transaction, the tracker condition is checked for the previous X days (number of days set in Track for ___ days) until the transaction date.
  • Cyclic Window: In Cyclic Window mode, when a customer makes a transaction for the first time after the tracker is configured, cycles of equal intervals are created for that customer based on the transaction date. The duration of each cycle depends on the value set in Track for ___ days. 
Based on the cycle in which a transaction falls, the tracker cases are evaluated from starting of that cycle until the transaction date.
Consider the following example:
A tracker was created on Apr 5, 2019, with a condition to reward a bonus of 200 points on a transaction of $1000 in 20 days ( Track for ___ days ).
Assume that a customer makes subsequent transactions on Apr 7, May 4, 10, and 22. 
  • In Moving Window mode, for the transaction made on Apr 7, a cycle of the last 20 days will be created (Mar 18 - Apr 7). Similarly, for the transaction made on May 4, a new cycle is created with the last 20 days from May 4, which is Apr 15 - May 4 and so on.


  • In Cyclic Window mode, based on the first transaction date (Apr 7) of the customer (after the strategy is configured), cycles are created with equal intervals of 20 days each.


For the first transaction ( Apr 7) the condition is checked only for that day. As the second transaction falls in Cycle 2 (May 4), the condition is checked from starting of the second cycle until the transaction day (Apr 27 - May 4). Similarly, the fourth transaction falls in Cycle 3 and the condition is checked from May 27 - May 22.

  • Calendar based Cyclic Window: Cycles of calendar months are created based on the Start Date and the number of months set irrespective of the transaction date.

For example, if a Calendar based Cyclic Window is created with the start date Apr 5 and the number of months 3, then the cycles are created for three calendar months as shown in the illustration below. Then, based on the date of the transaction, the corresponding cycle will be considered.

 

EntityChoose the entity that you want to track for the current tracker strategy

  • Bill Amount: To create tracker cases based on the net transaction amount (with discount). For example, if the gross bill amount is $120 and the discount is $20, the (net) bill amount is $100.
  • Bill Discount: To create tracker cases based on the discount amount of a transaction.
  • Bill Gross Amount: To create tracker cases based on the gross transaction amount ( without discount). For example, if the net bill amount is $100 after a discount of $20, the gross bill amount is $120.
  • Bill Total Quantity: To create tracker cases based on the total quantity of all line items purchased during the tracker period. For example, if a customer made 10 transactions with 20 line items of quantity 3 each in 90 days, then the Bill Total uantity would be 60.
  • Lineitem Amount: To create tracker cases based on the purchase value of individual line items. For example, a customer can have 10 transactions with 22 line items for 90 days where the sum of all line item amount is $700.
  • Lineitem Count: To create tracker cases based on the number of line items purchased. For example, a customer can have 10 transactions for 90 days where the line items could be 22.
  • Lineitem Quantity: To create tracker cases based on the number of line items purchased. For example, a customer can have 10 transactions with 22 line items for 90 days. The number of line items purchased could be 50.
  • Customer Visits: To create tracker cases based on the count of unique bills of a customer. In the above example, the customer visit count in 90 days is 22. 
  • Points: To create tracker cases based on the number of points earned during the tracker period.
Number of times to signal (per customer)Limit the number of successful executions of the current tracker case for a customer. The maximum value allowed is 9999. If a condition is then Once the tracker condition is successfully evaluated for the specified number of times for a customer, the tracker condition will not be evaluated for that customer again.
Case NameSpecify a meaningful name for the current tracker case
Track for ___ daysSpecify the duration of the window for which the tracker case needs to be evaluated. The mode of the window could be cyclic or moving as explained in Mode 
 If ____  ____


Define the condition of that tracker case in this field. For example, if the sum of transactions in 365 days are greater than $1000


  • Sum: Sum of the tracked entity values in the specified duration. For example for Bill Amount, the sum is the sum of all transactions (amount) tracked
  • Count: Number of times the entity has been tracked in the specified duration. For example, for Bill Amount, the count is the number of transactions tracked
Limit number of forwards per customerLimit the number of times of execution of the current tracker case. Once the case is executed successfully for X times for a customer (where X is the value specified in this field), the tracker case will not be evaluated for that customer again. 
Add Forward (Tracker Case) Click to create a new tracker case. You can create multiple tracker cases if required. When the tracker is evaluated, all the subsequent tracker cases of that tracker strategy will be evaluated. You can define actions to be performed upon successful execution of a tracker case in rule sets
Once you create tracker strategies, you need to configure rule sets to enable tracking the desired entity(bill amount, line-item count, line-item cost, etc) configured in the tracker strategy and trigger actions to be performed upon successful execution of each tracker case. 
To know how to configure rule sets for trackers, see Configuring Rules for a Tracker Strategy section.

Configuring a Tracker (Tracker Rules)

Once you create a tracker strategy, it is important to configure rule sets to start tracking entities set in tracker strategies, evaluate tracker cases and trigger actions upon successful execution of tracker cases.

To configure tracker based rules, go to the EventsView page and set the event as TransactionAdd.


You will see Set1 in which you can define rules on a new transaction event. Once you define a rule in Set1 and save it, you will see the second parent set which corresponds to tracker event. Similarly, once you save the rules of the second parent set, you will see the third parent in which you can create rules on a transaction finished event. You can see all the three parent sets in the screenshot below.

  • First Parent Set (Transaction Start Event ): The first parent set represents a new transaction event. This set is invoked whenever a new transaction happens. In this set, you can create rules based on new transaction events. This is always be represented by Set1.
  • Second Parent Set (Trackers Event): The middle parent set represents tracker events. In this set, you can create rules based on tracker strategies and tracker cases. You can also configure multiple tracker conditions in this set.
  • Third Parent Set (Transaction Finished Event): The last parent set represents the transaction finished event. This set completes a transaction once all the trackers configured in the trackers set are completely evaluated. You can also define rules on a tracker finished event.

You can create multiple child sets for a parent set. Each child set consists of conditions and actions. In the case of trackers, a tracker strategy is considered as a child set and all the respective tracker cases are sub-sets of that child set. The numbering of parent sets varies based on the number of child sets created under each parent set.

When a transaction is made, the first set is invoked and forwards it to the second set. The second set validates all the trackers and executes actions based on the rules and actions configured. The event then gets forwarded to the third set which completes the transaction event.


To create tracker based rules, do the following:

  1. On the EventsView page, choose TransactionAdd event and select the tracker related parent set (trackers set)
  2. Click +Condition

  1. Leave Expression and Expression equals to true
  2. In When field, click + and and select the default Forward to Set action

  1. Enable transaction item unroller to create rules based on transaction line-items and then click Save

A new tracker will be created under the trackers parent set as shown below. The tracker name is set by default. You cannot modify the tracker name. You can tag a tracker strategy to the tracker.

  1. Tag a tracker strategy to the tracker as explained in the following
  • Click on the tracker
  • In the When condition click +
  • Select the Tracker Evaluation action

  • In Tracker (Action field), choose the tracker strategy that you want to tag for the tracker and click Save.

You will see a list of tracker cases created in the tracker strategy, under the new tracker as shown below.

Create rules for individual tracker cases as explained in the Configuring Events topic. You could also have forward sets under a tracker case set. 
Similarly, you can add multiple trackers to define separate rules for each tracker strategy.

Configuring Multiple Trackers

To configure rules for multiple tracker strategies, add a separate condition  and configure a rule set for that condition as explained in the previous section. 

  1. Click on the set corresponding to trackers and then click another condition by clicking +Condition in the All Conditions pane and click When

  1. Click + and select Forward to Set

  1. To configure rules based on line-items, enable transaction item unroller and click Save

You will a new tracker created under the trackers parent set as shown below.

Once the tracker is created, assign a tracker strategy to the new tracker and configure a rule set as explained in Configuring Events.