Rate limiting
Cap how many experiences one user can see in a given time, and exclude the experiences that must show regardless.
Rate limiting caps how many experiences the same user can see in a given time, across your whole project. A user who falls into several audiences then gets your experiences spaced out instead of back to back.
The project cap
Set the cap in Settings > Rate Display Limit. The Rate limit card reads Display [N] Experience(s) every [N] [unit]: the maximum number of experiences, of any type (tours, surveys, NPS, banners...), one user can see within the time span. The unit is picked from a dropdown: Hours or Days.


How the window works
With a cap of one experience every 4 hours, a user who has just seen an experience sees no other one for 4 hours. Then the count resets. An experience held back during the window becomes eligible again: it is not lost, it waits.

Exclude an experience
An experience that must show whatever the cap, such as a security notice or a terms update, can ignore rate limiting. Two ways, same result.
In the When section of the experience, uncheck Rate limiting under Select experience priority. Checked, the experience respects the cap; unchecked, it ignores it.

A warning asks you to confirm before rate limiting is turned off.

In Settings > Rate Display Limit, in the Excluded experiences card, click + Exclude experience and pick the experience. A draft can be excluded too, before you publish it. The card lists every excluded experience.
How it shows in the Troubleshoot tool
An experience held back by the cap is listed as Waiting, with rate limiting among the conditions. See Why my experience does not show, cause 2.
Related
Last updated