> 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 means you won't get a real alert if your integration actually breaks. **Allowing Scout through fixes this.**
{% endhint %}
## How to identify Scout
{% columns %}
{% column %}
Scout identifies itself in two ways — match on either, and ideally pair them (see the security note below).
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% stepper %}
{% step %}
#### A User-Agent token
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 — the Chrome version changes over time, so don't match the whole string.
{% endstep %}
{% step %}
#### A signed request identity
Scout runs on Cloudflare's browser platform, which automatically attaches a cryptographically **signed** [Web Bot Auth](https://developers.cloudflare.com/bots/concepts/bot/verified-bots/web-bot-auth/) identity to every request (`Signature` / `Signature-Agent` headers). Unlike a User-Agent, this signature **cannot be spoofed** — so it's the most secure way to recognize Scout.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
**For your security team:** pair the `FliptoScout` User-Agent match with a source check (Scout's signed Web Bot Auth identity, or your provider's verified-bot category) rather than matching the User-Agent alone — a User-Agent on its own can be spoofed.
**Do not allow by IP address.** Scout runs on Cloudflare's shared browser platform and its egress IPs 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" %}
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 **WAF custom rule**:
1. Go to **Security → WAF → Custom rules → Create rule**.
2. Set the field to **User Agent**, operator **contains**, value **`FliptoScout`**.
3. Set the action to **Skip → All remaining custom rules** (and **Skip → Super Bot Fight Mode**).
{% hint style="info" %}
Because Scout sends a signed Web Bot Auth identity, you can also allow it as **verified bot traffic** for the strongest protection.
{% 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 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://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 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.