This article describes how to use Action Frequency Capping and Prioritization features in AudienceStream to control and prioritize action triggers.
In this article
By default, actions in AudienceStream fire as soon as their conditions are met. Depending on your connector choice, the actions configured fire when a user joins or leaves an audience or when a user is in the audience at the beginning or end of the visit.
The highest priority number specified becomes the highest priority. For example, a priority of "2" is higher than a priority of "1”. All non-capped actions trigger independently without delay and are not affected by the cooldown.
If two actions in the same cooldown group have the same priority, only one of them will trigger. If you need both actions to trigger, use separate cooldown groups.
Cooldown only applies when an action is enabled for Frequency Cap and the connector configuration is assigned an action priority number. The action priority number dictates which actions to trigger in the event that several actions in the same cooldown are fulfilled simultaneously.
When you add a new Cooldown Group, the group is available to all frequency capped actions in your profile.
Use the following steps to add a new cooldown group:
The Default Cooldown Group applies to frequency capped actions when no other cooldown is configured in your profile. You can edit the color and duration settings for the Default Cooldown Group and apply it to selected frequency capped actions but you cannot edit the name.
This section describes how to apply a Cooldown Group to a Connector action. You may apply a cooldown group to one or more frequency capped actions in the same connector.
Use the following steps to apply a Cooldown Group to a connector action:
Do not set to zero or a negative number. Assign the priorities in increments of 10 instead of consecutive numbers. This makes it easier to insert a new action later without having to update the priority values for other actions.
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.
|Action Name||Cooldown Group||Cooldown Hours||Priority Number||Additional Delay|
|A||Group 1||48 hours||40||—|
|B||Group 1||48 hours||30||2 hours|
In this scenario, cooldowns are applied to the actions as follows: