Limit how often a user can receive messages

Leanplum lets you set delivery caps on the number of Emails, Push notifications, Webhooks, and App Inbox messages per day (a 24 hour period) and/or per week (a 168 hour time period) that can be sent to any given user. Additionally, you can set limits on individual messages if they have a triggered delivery. 

These caps and limits ensure that if a user matches the target criteria for several messages (or matches the criteria for a triggered message multiple times), they do not receive more messages than you'd like.

Note: In-App messages do not have Caps, however, they have more powerful options for limits (more below).

Delivery Caps

Delivery caps limit the total number of messages a user can receive in a given day or week, where a day is the past 24 hours and a week is the past 168 hours (7 days). Right before each message is sent to a user, Leanplum determines if the message will exceed the daily or weekly caps. If so, the message will not be sent. 

Setting the Caps

To implement caps on the number of daily and/or weekly messages per user, navigate to the App Settings page by clicking on the App Selection menu at the top of the screen, and select Manage Apps.

Once in the App Settings page, do the following:

  1. Find the app you wish to set message caps for and click on the Keys & Settings link (Note: This requires your account to have Admin or Member privileges for that team)
  2. Click on the Messaging tab
  3. Enter the daily and/or weekly caps you would like to use (for push, webhooks, emails, or app inbox)
  4. Click Done

Exempting a message from caps

When composing a message, you can select the option Caps Exempt.

This will ensure the message is sent to all users, even those who have received the maximum number of messages (set by the cap).

Note: Caps Exempt messages still count towards the daily and weekly messaging caps. This means that a Caps Exempt message may actually cause a user to reach their cap and prevent the next non-exempt message from being delivered.



Individual email, push, webhook, and app inbox messages can be limited if the delivery type is "triggered." You can add a limit to restrict the total number of times a single user can receive the message. This is an all-time limit, not weekly or daily. See more in Limiting message sends with targets.

Quiet Hours

The Quiet Hours feature limits the hours during which a user can receive a message (any message other than in-app messages). To set Quiet Hours, do the following:

  1. Navigate to the message for which you want to set Quiet Hours
  2. Check the Quiet Hours checkbox in the Delivery section
  3. Set your start time and end time

Your users will not receive this message during the hours you have deemed Quiet Hours (in their timezone). If a message was scheduled for delivery during those hours, the message will be sent as soon as Quiet Hours are over (i.e., if your Quiet Hours end at 6 am and a message was scheduled for 5:45 am, it will be sent at 6:01 am).

  • Note: Locally triggered messages do not work with our Quiet Hours feature. This is because the send is controlled by the local trigger, and not Leanplum's servers.

In-App Message Limits

You can set limits on triggered In-App messages. However, you have a bit more options than other messages. There are three different types of limits you can set, and you can utilize all three types of limits in conjunction with one another:

  • When trigger occurs exactly n time(s)
  • When trigger occurs every n time(s)
  • Up to n time(s) per time period, where time period can be:
    • Ever
    • Per session
    • Per second
    • Per minute
    • Per hour
    • Per day
    • Per week
    • Per month

The limits menu appears after selecting a Display When event for your in-app message. See more in Limiting message sends with targets.






Was this article helpful?
Have more questions? Submit a request