Global frequency capping FAQ

How does Global frequency capping calculate time?

It depends on the counting mode:

• Rolling window (default): a day is exactly 24 hours from the time a message is sent. For example, if a message is sent on January 12, 2024, at 01:00 AM, the capping period applies until January 13, 2024, at 01:00 AM.
• Calendar day: the period starts at midnight N-1 days before today, in the selected capping timezone, and runs to the current moment. For a 1-day cap, it’s since midnight today. For a 3-day cap, it’s today plus the two previous calendar days, not the last 72 hours.

Which messages are affected by Global frequency capping?

Global capping limits marketing messages. Transactional messages are not subject to frequency capping. The rule applies across channels and sources, including API-based messages, Customer Journey messages, one-time push notifications and emails, in-app campaigns, SMS and WhatsApp messages, and App Inbox messages, which are counted separately from every other channel. Silent pushes and Live Activity updates aren’t subject to frequency capping.

Can I exclude specific users from Global frequency capping?

Yes. In Settings > Message delivery settings > Frequency capping, add a User ID or email to Users excluded from frequency capping, then click Apply changes. These users bypass every frequency limit, both global and custom.

What happens if I change Global frequency capping settings while a Customer Journey is running?

The updated settings apply immediately. Pushwoosh checks the capping rules every time it attempts to send a message. Switching the counting mode doesn’t reset counters: Pushwoosh counts the messages already sent over the new period, starting with the next message it checks.

What happens if I disable Global frequency capping?

Future messages will no longer be limited by capping rules. However, messages that were previously blocked due to capping will not be sent retroactively.

How does enabling Global frequency capping affect ongoing campaigns?

Customer Journey messages and messages you create after the change follow the new rules right away. A one-time message that is already scheduled keeps the limits that applied when it was created.

What if I enable Global frequency capping but still use the old capping settings in the Send Push form (legacy)?

The system will continue using the old capping settings for messages sent via the legacy Send Push form.

How does Frequency capping affect API-based messaging?

Marketing API messages are subject to global capping. Set message_type to transactional in /createMessage or email_type to transactional in /createEmailMessage so those sends are not capped. If you omit the type in the API request, frequency capping applies.