Counters are used for taking into account quantitative indicators of events registered in the system.

Application Field

The functionality of the counters enables count the appearance of various events in the system in the context of the field of application. Thus, it is possible to motivate LP Mebers to perform actions in the Loyalty Program, and vice versa, to limit the number of issued preferences during the period, for example: 

• the number of purchases by each customer in a given period of time,
• the number of preferences issued in each point of sale,
• the amount of purchases by account (a group of cards) for a certain period,
• the number of reposts in social networks for each customer,
• the number of friends invented to the LP, etc.

Counting Period

The time period in which the counter value is accumulated may not be limited. In this case, the counter records events for the entire duration of the offer in which it is configured.

It is also possible to limit the period for recording counter values:

• one day,
• one month,
• one year.

For example, if the counter period is set to one day, then every day the counter value will be recalculated starting from zero. At the same time, the system stores all previous counter values for the previous period, and they can be used in the mechanics of offers.

Types of Counters

The system provides several types of counters:

• The simple counter keeps a simple record of events (the number of friends, the number of offers, etc.).
• The counter associated with the purchase counts values from the context of the purchase (amount of purchases, the number of purchases, etc.). This counter fixes canceled purchases and purchase refunds.
• The multiplicity counter takes into account the multiple value from the purchase context (every n-th purchase, every n dollars of the purchase amount, every n-th discount).

Configuring an Offer with the Counter

Configuring offers with counters is performed in three stages:

1. Creating a counter

   When creating a counter, it is necessary to specify:

   • events that the counter will record,
   • parameters limiting the application field,
   • counter type - simple, purchase-related or multiplicity counter.

2. Configuring the Counter action

   Using the Counter action, it is possible to configure the change in the value of the counter when the events recorded appear in the system.

   Depending on the type of the counter the step of counter change, variable value from the event context or provided preferences are to be specified.

   • Simple counter simply counts events. It can be assigned only the type of step - Constant.
   • Counter bounded with the purchase can simply record or record variables from the purchase context.
   • Multiplicity counter can simply record or record variables from the purchase context and at the same time counts the number of the provided preferences.

3. Configuring the Counter filter

   With the help of the Counter, the limit of the counter value under which the offer actions will be performed. In this case, it is possible to take into account the accumulated counter value or the number of counter changes over a certain period of time. When filtering by the number of changes, the accumulated counter value is not taken into account. For example, in this way it is possible to take into account the frequency of purchases, but not more often than once in 15 minutes.

   For counters that keep track of time (every day, every month or every year), it is possible to set the conditions for checking their values for the past recording period. For example, it is possible to configure offer condition based on the amount of purchases made in the last month.

Storing Counter Values

Counter values are stored in the database for the entire period of its validity. If the metering period (day, month or year) is specified in the counter parameters, it is possible to get the counter value for the past period. For example, in the Counter filter settings, it is possible to select a specific date in the past to check the value of a counter that counts daily events. Or check the value for the previous month with a monthly meter.

In addition, the database stores statistics about the number of counter changes. This value can also be used when configuring offer conditions. For example, it is possible to find out how many times the purchase counter has changed in January of the current year.

At the moment, statistics of counter changes and their values are not transmitted or processed in the analytics module.