FAQ about Mobile Channel Frequency Capping

Prev Next

What does Frequency Capping mean?

Frequency Capping allows you to control how many app push notifications a user can receive within a specific period. You can configure it daily at the channel level. For example, if you set it to 1 per day, the user will only receive one app push notification from your app per day, even if multiple campaigns are scheduled.

Is the global frequency capping limit applied per user or device?

It is applied per user.

Does global frequency capping apply to pushes sent via Bulk Push API?

Yes, Bulk Push API follows the Global Frequency Capping (GFC) settings. Sending pushes via Bulk Push API increases the user’s GFC count.

Does global frequency capping apply to pushes sent via Targeted Push API?

No, the Targeted Push API does not follow Global Frequency Capping settings. Pushes sent through this API do not increase the user’s GFC count.

If I bypass global frequency capping in a campaign, does it still increase the user’s push count?

Yes. Even if Global Frequency Capping is bypassed in a campaign, the push still counts toward the user’s global cap limit for the day.

Are push campaigns triggered from Architect subject to global frequency capping?

Yes, push campaigns sent via Architect are included in Global Frequency Capping and count toward the user’s limit.

Are app templates triggered within Architect subject to global frequency capping?

Yes, the App Templates triggered from Architect are counted toward Global Frequency Capping.