Frequency capping example

This section provides a usage example using a sample scenario. In this scenario, it is assumed that your profile has two cooldown groups and one connector with four actions.

In this scenario, cooldown periods are applied to the actions as follows:

• Cooldown Group 1

  • If Action A evaluates to true before Action B, only Action A triggers.
  • The 48-hour cooldown starts, during which time neither Action A or B trigger.
  • If Action B evaluates to true before Action A, only Action B triggers after the 2 hours configured as an additional delay.
  • The 48-hour cooldown starts, during which time neither Action A or B trigger.
  • If Actions A and B are both true at the same time, only Action A triggers because it is assigned the highest priority number.
  • The 48-hour cooldown starts, during which time neither Action A or B trigger.

• Default Cooldown

  • When Action C evaluates to true, it is triggered instantly.
  • The 24-hour cooldown starts, during which time Action C will not trigger again.
  • Action D triggers immediately after its condition is met and is not throttled by any cooldown.