> 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/set-up-your-website.md).
# Set up your website
To set up Flip.to, add the following code snippet to the **\** tag of every page of your website and take a peek below at any additional configurations.
```html
```
{% hint style="info" %}
The user experience and tracking on the website can be impacted if the tag is delayed on page load. To ensure it loads asynchronously, we recommend adding it directly to the \ tag over GTM.
{% endhint %}
***
## Configurations
Implementing Discovery
If you're implementing Discovery, you'll also need to add the following snippet. Make sure to include your unique **Discovery ID** in your snippet.
```html
```
{% hint style="warning" %}
You'll need your unique Discovery ID, which you should have received by email. If not, ask our [Customer Success team](/docs/support/customer-success.md).
{% endhint %}
Setting up Consent Management
Flip.to supports consent signals out-of-the box for CookieBot, OneTrust, and Google Tag Manager—see the guide for [Consent management for your website](/docs/integrations/websites/consent-management-for-your-website.md).
Supporting JavaScript navigation
If you use JavaScript to navigate users from your website to your booking engine, there's one extra step—see the guide for [Cross-domain tracking](/docs/integrations/websites/cross-domain-tracking.md).
Configuring single-page applications
For single-page applications, this snippet should only be loaded at application start, not on virtual pageviews.
***
If your website and booking engine are on the same domain, the instructions above apply only to your website pages. A different snippet is required for [your booking engine pages](/docs/integrations/booking-engines/set-up-your-booking-engine.md).
---
# 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/set-up-your-website.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.