> For the complete documentation index, see [llms.txt](https://docs.flip.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flip.to/docs/integrations/websites/allowing-flip-to-scout.md).
# Allowing Flip.to Scout
{% columns %}
{% column %}
Meet **Scout**, Flip.to's friendly watchdog. Scout automatically loads your website and confirms your Flip.to integration (the Discovery component, tracking script, and booking links) is installed and working. If something breaks, Scout lets our team know so we can help you fix it quickly.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% hint style="success" %}
**Scout is read-only and safe.** It loads your pages the way a normal browser would. It never logs in, submits forms, makes bookings, or changes anything on your site.
{% endhint %}
{% hint style="warning" %}
**Seeing this page because your bot protection is blocking Scout?**
When a website firewall or bot-protection service (Cloudflare, Akamai, DataDome, Imperva, and similar) serves Scout a "challenge" or block page instead of your real site, Scout can't verify your integration. That produces false *"integration missing"* results on our side, and it means you won't get a real alert if your integration actually breaks. **Allowing Scout through fixes this.**
{% endhint %}
## How to identify Scout
Every request Scout makes includes **`FliptoScout`** in its User-Agent string:
```
Mozilla/5.0 (...) Chrome/... Safari/537.36 FliptoScout/1.0 (+https://www.flip.to/scout)
```
Match on the **`FliptoScout`** token, not the whole string, because the Chrome version changes over time.
{% hint style="info" %}
**For your security team:** a User-Agent on its own can be spoofed. Where your provider can verify the source of a request, pair the `FliptoScout` match with that check. The Cloudflare tab below shows how.
**Do not allow by IP address.** Scout runs on shared cloud infrastructure and its IP addresses are not stable.
{% endhint %}
## Allow Scout through your bot protection
Pick your provider below. In every case, the goal is the same: let requests whose **User-Agent contains `FliptoScout`** reach your site.
{% tabs %}
{% tab title="Cloudflare" %}
In Cloudflare, Scout's browser sessions appear as **Cloudflare Browser Run** (category **AI Assistant**). How you allow Scout depends on which Cloudflare bot product you use:
* **Bot Fight Mode (free plans):** Bot Fight Mode does **not** honor WAF skip/allow rules, so a User-Agent rule will not work. Either turn Bot Fight Mode off for your site, or upgrade to a plan with Super Bot Fight Mode / Bot Management.
* **Super Bot Fight Mode (Pro/Business) and Bot Management (Enterprise):** add a **custom rule**:
1. Go to **Security → Security rules → Create rule → Custom rules**.
2. Set the field to **User Agent**, operator **contains**, value **`FliptoScout`**.
3. Set the action to **Skip**, and select both **All remaining custom rules** and **All Super Bot Fight Mode rules**.
4. Place the rule **first** in your custom rules, then deploy.
* **Bot Management (Enterprise), stronger match:** add **Bot Detection ID** equals **`119853733`** to the same rule's expression (combined with the User-Agent condition). That ID is Cloudflare's own identifier for Cloudflare Browser Run sessions and can't be spoofed, so the rule only matches genuine Browser Run traffic that carries Scout's token.
* **AI crawler / AI agent blocking.** If you block AI crawlers or agents (in **AI Crawl Control** or your bot settings), allow **Cloudflare Browser Run** there. The custom rule above also lets Scout past an AI Crawl Control block, because that block is itself a custom rule that runs after yours.
{% hint style="info" %}
Cloudflare's own guidance: [Allowlisting Browser Run](https://developers.cloudflare.com/browser-run/faq/#can-i-allowlist-browser-run-on-my-own-website) and [Skip rule options](https://developers.cloudflare.com/waf/custom-rules/skip/options/).
{% endhint %}
{% endtab %}
{% tab title="Akamai" %}
In your bot management / **Bot Manager** policy, add an **allow (exception) rule** that matches the **User-Agent** containing **`FliptoScout`**, so requests from Scout bypass bot mitigation.
{% endtab %}
{% tab title="DataDome" %}
In the **DataDome dashboard**, add a **custom rule / allowlist** entry matching the **User-Agent** containing **`FliptoScout`**, and set it to **Allow**.
{% endtab %}
{% tab title="Imperva" %}
In your **Imperva (Incapsula)** site security settings, add a **Bot Access Control / allowlist** exception for the **User-Agent** containing **`FliptoScout`**.
{% endtab %}
{% tab title="Other / origin firewall" %}
Any WAF or origin firewall that lets you write rules on the request User-Agent can allow Scout the same way: **permit requests whose User-Agent contains `FliptoScout`**.
{% endtab %}
{% endtabs %}
## After you've allowed Scout
{% columns %}
{% column %}
That's it. There's nothing else you need to do. Scout re-runs automatically on its regular schedule, so once your rule is in place, its next visit should reach your live site and the integration check will clear on its own.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% hint style="info" %}
Need a hand, or want us to confirm Scout is getting through? Reach out to your Flip.to contact and we'll verify it together. 🐾
{% endhint %}
---
# 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.flip.to/docs/integrations/websites/allowing-flip-to-scout.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.
