> For the complete documentation index, see [llms.txt](https://docs.pulseinsights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulseinsights.com/implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/bot-blocking.md). # Bot blocking Pulse Insights attempts to recognize and block bot traffic so that bots don't see impressions, which can skew the reporting/accuracy of survey response rates. Our analysis shows that most client bot traffic is from crawlers such as search engines and security vendors. There are two primary mechanisms for bot recognition: * IP address requests over a threshold within a time window * Maximum cumulative impressions for a single Device UDID The exact values change from time to time to allow for heavy real usage by development and QA teams, while still blocking likely bots. Once traffic is identified as a bot, Pulse Insights will not return surveys unless explicitly unjailed by by Pulse Insights. Or, once max cumulative impressions for a single UDID is reached, any additional impressions or responses won't be recorded. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.pulseinsights.com/implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/bot-blocking.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.