# Set up your website (legacy) Adding Flip.to to your website requires the following code snippet on every page of your website. {% hint style="warning" %} **Before you begin:** you'll need your unique IDs, which you should have received by email. If not, ask our [Customer Success team](/docs/support/customer-success.md). {% endhint %} {% embed url="" %} {% hint style="warning" %} If your website and booking engine are on the same domain, the instructions below 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). {% endhint %} *** ## Website code snippet The following snippet should be added to the **\** tag of every page of the website. Make sure to include your unique **Website ID** in your snippet. ```html ``` {% hint style="info" %} The user experience and tracking on the website can be impacted if the tags are delayed on page load. So it loads asynchronously, we recommend using the \ tags over GTM. {% endhint %} {% hint style="info" %} For single-page applications, this snippet should only be loaded at application start, not on virtual pageviews. {% endhint %} 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" %} 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). {% endhint %} --- # Agent Instructions: 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: ``` GET https://docs.flip.to/docs/integrations/websites/set-up-your-website-legacy.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.