Push frequency capping
Limit how often push notifications are sent
OneSignal helps you reach your users effectively—without overwhelming them. Sending too many messages can lead to unsubscribes, disengagement, or a poor user experience. Frequency Capping allows you to control how often users receive push notifications from your app by setting limits on the number of messages sent per minute, hour, day, or week.
Frequency Capping is available on selected Paid Plans.
When to use frequency capping
Frequency Capping is particularly useful in scenarios where messaging volume may become excessive:
- Complex Campaign Environments: Large organizations with multiple teams or overlapping marketing campaigns.
- High-Frequency Triggers: Systems that send notifications based on frequent events (e.g., stock price updates or automated news alerts).
How to enable frequency capping
You can configure frequency capping at the app level via the OneSignal Dashboard:
Navigate to Settings > Push & In-app > Frequency Capping.
Set the maximum number of messages a user can receive in a given time period.
Notifications can be capped at x notifications per any time frame.
Important notes
- Capping applies to all push messages, regardless of source (API, Journeys, or manual sends).
- Messages blocked due to capping are dropped, not queued for later.
For example, if the cap is set to 2/day and a user already received 2 API messages, a Journey message will be dropped unless capping is overridden.
Override frequency capping
In some cases, you may want to send a message even if it exceeds the cap. You can override frequency capping on a per-message basis:
- In the message’s Delivery Schedule.
- Select Override frequency capping settings.
- In the message’s Delivery Schedule.
- Select Override frequency capping settings.
Using the Create Push notification API you can override the frequency capping with the parameter:
enable_frequency_capset tofalse
Notes on overriding
- Frequency capping must be enabled in the OneSignal dashboard.
- Overridden messages still count toward the cap. This affects whether future messages are delivered.
Reporting
When capping is enabled, you can monitor how it impacts your notifications via dashboard messages reports or view message API.
Each message with capping enabled will show a status of:
- Capped: Frequency capping is enabled for the app and how many were capped.
- Overridden: Frequency capping is enabled for the app, but was overridden for the notification.
Push frequency capping
Limit how often push notifications are sent
OneSignal helps you reach your users effectively—without overwhelming them. Sending too many messages can lead to unsubscribes, disengagement, or a poor user experience. Frequency Capping allows you to control how often users receive push notifications from your app by setting limits on the number of messages sent per minute, hour, day, or week.
Frequency Capping is available on selected Paid Plans.
When to use frequency capping
Frequency Capping is particularly useful in scenarios where messaging volume may become excessive:
- Complex Campaign Environments: Large organizations with multiple teams or overlapping marketing campaigns.
- High-Frequency Triggers: Systems that send notifications based on frequent events (e.g., stock price updates or automated news alerts).
How to enable frequency capping
You can configure frequency capping at the app level via the OneSignal Dashboard:
Navigate to Settings > Push & In-app > Frequency Capping.
Set the maximum number of messages a user can receive in a given time period.
Notifications can be capped at x notifications per any time frame.
Important notes
- Capping applies to all push messages, regardless of source (API, Journeys, or manual sends).
- Messages blocked due to capping are dropped, not queued for later.
For example, if the cap is set to 2/day and a user already received 2 API messages, a Journey message will be dropped unless capping is overridden.
Override frequency capping
In some cases, you may want to send a message even if it exceeds the cap. You can override frequency capping on a per-message basis:
- In the message’s Delivery Schedule.
- Select Override frequency capping settings.
- In the message’s Delivery Schedule.
- Select Override frequency capping settings.
Using the Create Push notification API you can override the frequency capping with the parameter:
enable_frequency_capset tofalse
Notes on overriding
- Frequency capping must be enabled in the OneSignal dashboard.
- Overridden messages still count toward the cap. This affects whether future messages are delivered.
Reporting
When capping is enabled, you can monitor how it impacts your notifications via dashboard messages reports or view message API.
Each message with capping enabled will show a status of:
- Capped: Frequency capping is enabled for the app and how many were capped.
- Overridden: Frequency capping is enabled for the app, but was overridden for the notification.