Offer Retention Rate explained
It is possible to configure a retention rate at the offer level. This is an optional setting, so there is no need to configure it unless required.
Each time an event is received through the postback URL, the platform checks whether a retention rate has been configured for the offer. If so, the system reviews which events have been processed and which have been retained since 00:00 of the current day, and applies the configured retention rate if necessary.
This is the basic setup. However, an advanced configuration is also available, which allows for more granular control based on the following criteria:
Minimum number of events before applying the retention rate (i.e. retention will not be used until this threshold is met).
Time window over which statistical data is analysed to determine whether the retention rate should be applied.
This mechanism helps fine-tune the retention logic to better align with your traffic patterns and business needs.
Advanced Configuration
In the advanced configuration, you can specify both a minimum number of events that the retention rate will not apply to and a time window during which statistical data will be analysed to determine if the retention rate should be enforced.
Minimum count: This refers to the number of events that are unaffected by the configured retention percentage. These events are counted at the start of the period.
Time windows: This explains how to determine the period for analysing the statistics.
Fixed: The period is the current day, from 00:00, or the current hour.
Rolling: The period is relative; the platform will analyse data from the moment the event is received, considering the period of time set in "In period".
In period: This is the timeframe from now backwards that will be considered for applying the appropriate retention rate and ensuring that the number of events specified in "Minimum count" is not influenced by the retention rate in that period.
