Batch's frequency capping allows you to limit the number of notifications a device can receive in a customisable time frame.
That marketing pressure limit is useful when you accidentally target the same users several times in a short period of time, encouraging them to disable notifications or uninstall your app. This can happen when you are sending many different types of push notifications:
You can adjust the frequency capping for your app in two different ways from the dashboard settings > Cappings.
Frequency capping is available on the Enterprise plan and, as an option, on other paid plans.
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 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.
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.
As a reminder, labels are "tags" you can attach to your campaigns when you create them on Batch dashboard or using the Transactional or the Campaigns API. They enable you to group similar campaigns together and find them easily on the dashboard:
You can create a frequency capping for all the notifications attached to a specific label. This will work for notifications sent from the dashboard or Batch's APIs:
Please note all rules are dynamic. Batch will check the number of notifications that have been sent in the last X hours/days to see if the notification has to be sent or not.
For all your push campaigns, Batch will display the number of notifications that were not delivered because users already reached the limit defined in your dashboard settings: