You can set mobile app frequency limits for each mobile app to control the maximum number of messages a user receives per month, week, day, hour or minute. This is to avoid overengagement, and as a result, the possibility that the user might uninstall the app.

Frequency limits are enforced with a rolling window and are checked at any giving point in time. Start and end dates are not involved. At the time of sending, the frequency limits are checked against the number of messages that are already sent within the past month, past week, past 24 hours, past hour, or past minute period. The message is not sent if the limit is reached on any of the limit levels set.

Use case example

If an app frequency limit is set to, maximum messages per month = 100 and maximum messages sent per week = 10 for the store iOS app, then at any point in time the system checks if the mobile app for maximums reached in the past month and past week. For example:

On 07/04/2020, if a new message for a 4th of July Sale should be sent to the store mobile app, the system checks for the maximums reached in the past month and week:

• If 100 (monthly max) and 10 (weekly max) are reached - the user will not receive the message.
• If 100 (monthly max) and 10 (weekly max) are not reached - the user will receive the message.
• If 100 (monthly max) are not reached but 10 (weekly max) are reached - the user will not receive the message.

Set frequency limits

1. In the Campaign menu, go to Development > Apps > New app.
2. Select Frequency limits.
3. Under Settings, choose how often you want the app to send for mobile app messages by setting a frequency limit.

   Available frequency limits settings are:

   • No frequency limits - Users can send unlimited messages.
     • 'No frequency limits' is the Default setting for any mobile app.
   • Custom limit(s) - Set the maximum number of messages that are sent per month, week, day, hour or minute.

     Rules when using custom limit(s)

     • Users can enter more than one custom limit, such as a limit for month and another for week. However, if there is more than one custom limit, the limit values must be in descending order from month to minute, e.g. the week limit cannot be greater than the month limit.
     • If the minute limit (see last row) is set, you must enter a value for both the maximum number of messages and the number of minutes. If you enter a value for only one of the two fields, you see an error message when you save your changes.
     • All customer limits that are preset values should be positive numbers greater than zero.
   • Preset limits: Set Low (default), Medium, or High options to define suggested preset limits for messages that are sent per month, week, day, hour, or minute. The default for preset limits is set to low.
4. Select Save.

Important notes about app frequency limits

• As of February 27th, 2018, we added App frequency limit support to PUSH TO CONTACT API, with a separate API: channels/push/sends/useAppFrequency
• Use this Swagger URL when sending messages via the Push to Contact API and when mobile app frequency limit(s) do NOT need to be honored or checked: https://api-campaign-[Data Center]-[Pod#].goacoustic.com/restdoc/#!/channels/push_to_contacts_post_
• Use this Swagger URL when sending messages via the Push to Contact API and when mobile app frequency limit(s) need to be honored and supported: https://api-campaign-[Data Center]-[Pod#].goacoustic.com/restdoc/#!/channels/push/sends/useAppFrequency
• When you set frequency limits for a mobile app key, inline error messages display on the Frequency limits tab. If you do not comply with an app key frequency limit rule, an inline error message displays. The corresponding field with the error is highlighted with a red box.
• Push to contact source/segment APIs accept mobile app frequency limits.