> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/publish/trigger-at-the-right-time-when/rate-limiting-prevent-overwhelming-users.md).

# Rate Limiting - Prevent overwhelming users

You may have users that fall into multiple target audiences and they could be shown too many Jimo's experiences in quick succession. You can restrict this with our **Rate Limiting** functionality.

***

### Quick access

* [Create a Rate Limit to avoid overwhelming users](#id-1-create-a-poke-limit-to-avoid-overwhelming-users)
* [Rate limit exclusions](#id-1-poke-limit-exclusion)

***

## Create a Rate Limit to avoid overwhelming users <a href="#id-1-create-a-poke-limit-to-avoid-overwhelming-users" id="id-1-create-a-poke-limit-to-avoid-overwhelming-users"></a>

To set a limit *(1 Experience every 4 hours per default)*, go to Settings > Rate Display Limit.

<figure><img src="/files/MgOZ16jpObgsor4uFHFl" alt=""><figcaption><p>Rate limiting</p></figcaption></figure>

You can set the maximum number of experiences (Tours, NPS, surveys, etc.) any user should see across a given timespan (minute, hour, day, or week).\
In the example on the screenshot above, a user can’t see more than one experience every 4 hours. After the 4 hours, their experience view count will be reset, and they can see it again.\
\
If any experiences were blocked from displaying during the 4 hours, the user will be eligible to see them again.

***

## Rate limit exclusion <a href="#id-1-poke-limit-exclusion" id="id-1-poke-limit-exclusion"></a>

If you are launching an important experience that your users must see, regardless of whether they've hit the global frequency limit, you can bypass the frequency limit for that particular experience. In the audience settings of your experience, you will be able to uncheck "**Rate limiting**” to ignore the experience limit. When checked, the frequency limit will be ignored.

<figure><img src="/files/J0zr5pNh2ucpomvSRJrR" alt=""><figcaption><p>Rate limiting button</p></figcaption></figure>

<figure><img src="/files/sQ82UTzLcltVboccA2bd" alt=""><figcaption><p>Disable rate limiting alert</p></figcaption></figure>

<figure><img src="/files/Px6mZd7AsbIdncJ5bgdY" alt=""><figcaption><p>Disabled rate limit</p></figcaption></figure>

{% hint style="info" %}
**Remember**: You can also do it manually from the Rate limitation page in the settings by adding an experience or a draft with the "**+ Exclude experience**" button.
{% endhint %}

<figure><img src="/files/OrqFaZ5x2EYBbzKVPdYu" alt=""><figcaption><p>Exclude experience</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.usejimo.com/docs/publish/trigger-at-the-right-time-when/rate-limiting-prevent-overwhelming-users.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
