Cappings

Frequency capping allows you to limit the number of messages a profile can receive in a certain time frame.

The feature is restricted to users with App or Administrate rights.

Label-based Capping

If you are looking for a more granular way of capping the number of push notifications a single device can receive, you can set a label-based frequency capping.

You can create a frequency capping for all the orchestrations attached to a specific labels. It work for orchestrations created via the Dashboard or Batch's APIs.

Batch dynamically checks the number of messages that have been sent in the last X hours/days to see if the notification has to be sent or not.

If you send a multiplatform push message, it counts as one sending even if the person might receive the push on several devices.

Important note: Messagages sent very closely or at the same time may not be taken into account by the capping feature.

Global Capping

You can either define a simple limit that will be applied to all the notifications you send or fine-tune your global frequency capping:

• All push notifications: The capping rules affects all your push notifications.
• Orchestrations: The capping rules only affects notifications coming from campaigns and automations created on the dashboard or with the Campaign API.
• Transactional: The capping rules only affects notifications sent with the Transactional API.
• In-app messages: This capping rules only affects In-app messages. It can be setup by session or interval of time.

All these rules can work together. For example, you can set a global capping of 5 push notifications per day and create two additional rules that will ensure users won't receive more than 1 transactional push every 2 hours and 1 push from a marketing campaign per week.

Gloal capping is only available on Push v1 and thus siloed by platform (iOS, Android, Web). In Push v2, it is possible to apply the same capping rule on all orchestrations putting on them the same label.

Capping analytics

You can see the number of messages that were not delivered because users already reached the limit defined in your dashboard settings. The corresponding metric is called "Skipped".