Trackers is a powerful tool to track custom values over a specific period. You can use trackers for Eligibility and Renewal strategies and also in Workflows for certain milestones. The custom values are 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 custom values.

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

To set trackers for transaction events, do the following.

  1. On Intouch, navigate to Loyalty+ > Programs.
  2. In Programs, select the program you want to edit.
  3. Click Edit Program and select Trackers.
  4. Click Add Trackers.
  5. In Name, enter the tracker name.
  6. In Tracked entity, select any of the following entities that you want to track.
    EntityDescription
    Transaction amountCreate 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.
    Transaction discountCreate tracker cases based on the discount amount of a transaction.
    Transaction gross amountCreate 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.
    Transaction total quantityCreate tracker cases based on the total quantity of all line items purchased during the tracker period. For example, if a customer makes 10 transactions with 20 line items of quantity 3 each in 90 days, then the bill total quantity is 60.
    Lineitem amountCreate tracker cases based on the purchase value of individual line items.
    Lineitem countCreate tracker cases based on the number of line items purchased. For example, a customer can have 10 transactions for 20 days where the line items are 200.
    Lineitem quantityCreate 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 visitsCreate tracker cases based on the count of unique bills of a customer.
    PointsCreate tracker cases based on the number of points earned during the tracking period.
    Transaction extended fieldCreate tracker cases on a transaction-level extended field. You can use extended fields with datatypes Integer or Double.
    Lineitem extended fieldCreate tracker cases on a transaction lineitem-level extended field. You can use extended fields with datatypes Integer or Double.
  7. In Tracking Method, select any of the following methods to track entities.
    MethodDescription
    Moving WindowIn 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.
    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.


    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 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.

    Tier Change WindowCalculates tracker values considering the last tier change date. For example, if a customer's tier changed on Aug 2, 2020, tracker values will be calculated from Aug 2, 2020, until the current date.
  8. In Maximum times to track per customer, enter the limit of tracking the selected metric for a single customer.
    Trackers need to be incorporated in Workflows to define when they need to be evaluated and what happens when the milestone conditions are met.
  9. In Case Name, enter the name for the current tracker case.
  10. In Track For__days, enter the duration of the window to evaluate the tracker case.
  11. In What are the tracker's milestones, select any of the following options for two fields and enter the desired value.
    Define the condition of that tracker case in this field. For example, if the Sum of transactions in 365 days are Equal to$1000.
    1. Field 1:
      OptionDescription
      SumIt is the total of tracked entity values for the specified duration. For example for Bill Amount, the sum is the total value of all transactions (amount) tracked for a set duration.
      CountIt is the number of times the entity is tracked in a specified duration. For example, for Bill Amount, the count is the number of transactions tracked for a specified time period.
    2. Field 2:
      OptionDescription
      Equal toThe condition becomes true if the Sum or Count is the same as the configured value
      Greater thanThe condition becomes true if the Sum or Count is more than the configured value.
      Less thanThe condition becomes true if the Sum or Count is less than the configured value.
      Greater than or Equal toThe condition becomes true if the Sum or Count is either equal to or more than the configured value.
      Less than or Equal toThe condition becomes true if the Sum or Count is either equal to or less than the configured value.
      Mod of
      BetweenThe condition becomes true if the Sum or Count falls between the two configured values.
  12. Enable Limit No. of forwards per customer and enter the value to limit the 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.
  13. Click Save.
  • You can see the configured tracker case in Preview.
  • You can add multiple tracker cases by clicking Add Tracker Case.



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 Workflow page and select Make a transaction.

The first parent set (Set1) is for new transaction activity, the second one is the TrackerSet where you can define rules on tracker cases. The last parent set is for the transaction finished activity.

  • First Parent Set (Transaction start activity): 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.
  • TrackerSet: 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 activity): 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 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 navigate to TrackerSet.
  2. Click +Condition.

  1. Leave Expression and Expression equals to true.
  2. In When field, click and select the default Forward to Set action using +Add action > Click Save > Enable transaction item > Click Save.
     A new tracker is created under the TrackerSet as shown above. The tracker name is generated by default. You cannot modify the tracker name. You can tag a tracker strategy to the tracker.Tag a tracker strategy to the tracker as explained in the following
    • Navigate to the child tracker set
    • In the When condition click +
    • Select the Tracker Evaluation action and click Save.
       
  1. In Add tracker evaluation action, choose the tracker case for which you want to configure rules.

  • In Trackers (Action field), choose the tracker strategy that you want to tag for the tracker and click Save.
Similarly, you can create multiple child tracker sets under the parent set. To know how to configure rules, see Configuring Events.