> 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/booking-engines/set-up-your-booking-engine.md). # Set up your booking engine To set up Flip.to, add the following code snippet to the **\** tag of every page of your booking engine—**including the confirmation page**—and take a peek below at any additional configurations. ```html ``` {% hint style="info" %} We have step-by-step guides for **SynXis**, **Cloudbeds**, **iHotelier** and others—see the [vendor guides](/docs/integrations/booking-engines/vendors.md) for exactly where the snippet goes in yours. {% endhint %} *** ## Configurations Once the snippet is in place, Flip.to reads what it needs from the booking engine directly: * **Which property the page is for.** Depending on the engine, that's read from the URL, from values the engine exposes on the page, or from its data layer. * **The language**, from the page's own markup. * **The reservation**, from the confirmation page—confirmation number, guest details, dates, room and rate, currency and amount. Flip.to has built-in detection for dozens of booking engines. **If yours isn't one of them, the snippet still works**—you supply the same values through the data layer instead, as described under Overrides. See below for specific configurations that may apply to your booking engine.

Tracking add-ons and other products

If you sell experiences, events or ancillary items at time of booking, those are the one thing we can't read from the page—see [E-commerce tracking](/docs/integrations/booking-engines/e-commerce-tracking.md).

Setting up Consent Management

See the guide for [Consent management for your booking engine](/docs/integrations/booking-engines/consent-management-for-your-booking-engine.md).

Configuring single-page applications

For single-page applications, this snippet should only be loaded at application start, not on virtual pageviews.

Overrides

**Most implementations need none of this**—if Flip.to has built-in detection for your engine, it works from the snippet alone. Use the overrides below when it can't detect what it needs: an engine we don't have built-in detection for, a custom booking-engine domain, or a page whose language markup is wrong or missing. If you're not sure, ask [Customer Success](/docs/support/customer-success.md) first. #### Setting the property or language directly Put `data-flipto-code` on any element to set the property code: ```html ``` For language, the attribute goes **on the `` element specifically**—it is not read anywhere else: ```html ``` #### Setting values via the data layer Where a data attribute isn't practical, the same values can be pushed before the snippet loads. This takes precedence over everything Flip.to detects on its own, and goes **before** the Flip.to snippet rather than instead of it. ```javascript ```

Field	Description
bookingEngine	The Flip.to string identifying your booking engine vendor. Ask Customer Success for the value to use.
companyCode	Your internal Flip.to company code.
code	The property code used by the booking engine.
language	Optional. The ISO 639-1 language code the engine is displaying—`'en'`, `'fr'` and so on. A culture name such as `'en-US'` also works. Only needed when the page's own language markup is missing or wrong; otherwise Flip.to reads it from the page.

#### Sending the reservation directly If your engine can't be read from the confirmation page—or you want to send values you know are correct rather than have them detected—push the reservation on the confirmation page. Anything you send here takes precedence over what Flip.to would otherwise read. ```javascript ```

Field	Description
bookingEngine	The Flip.to string to define the booking engine used. Please contact Customer Success if you need the name to use for your booking engine vendor.
confirmation	Guest’s confirmation number.
loyalty	Guest's loyalty program number, if any.
first	Guest’s first name.
last	Guest’s last name.
email	Guest’s email address.
phone	Guest’s phone number.
startDate	Guest’s check-in date. This should be formatted as `'yyyy-MM-dd'` (i.e. 2027-05-15). If you prefer a different date format use the dateFormat field.
endDate	Guest’s check-out date. See start date for specifics.
guests	The total number of guests.
adults	The total number of adult guests.
children	The total number of children guests.
type	The guest’s room type, if available. Otherwise leave it blank. This should include the booking engine internal code, and not the room type description.
rateCode	The guest’s rate code, if available; otherwise blank
groupCode	The guest’s group code (or block code), if available. Otherwise leave it blank.
promoCode	The guest’s promo code, if available. Otherwise leave it blank.
language	The language ANSI code the guest has used to make the reservation. For English use 'en', French 'fr', etc. Refer to the complete list of language codes. Use the ISO 639-1 Code for the language parameter. Optionally, a culture name can be used as well. For example, this can be set to `'en-US'` or `'en_US'`.
currency	The 3 character currency code the guest has used to make the purchase. A complete list of currency codes can be found here. For instance 'USD' for US dollars.
amount	The total pre-tax amount used for the room purchase based on the defined currency. Amount should be supplied as a valid number including a decimal point if appropriate.
flightAmount	Optional The total pre-tax amount of the flight portion of the purchase. This can be omitted or set to null if booking engine does not support purchasing flights. Amount should be supplied as a valid number including a decimal point if appropriate.
addonAmount	Optional The total amount used for any add-on products and/or services. Amount should be supplied as a valid number including a decimal point if appropriate.
dateFormat	Specify a different date format for the startDate and endDate parameters. All date fields should be set using the default format: `'yyyy-M-d'`. However, you can define your preferred format instead with this field. For example, if you want to use 12/31/2027 the dateFormat should be set to: `'M/d/yyyy'`.
products	To track additional e-commerce products purchased at time of booking, such as events, experiences, ancillary items or other, see our E-commerce tracking.

#### Optional dynamic configuration ```javascript ```

Field	Description
_ga-ft	Page persistent access to the value of the _ga-ft url parameter. Used as a fallback in case the _ga-ft url parameter is removed by the booking engine.
enableAdobeCrossDomain	Flag denoting whether Flip.to should attempt to add adobe analytics cross-domain parameters to outbound links. Used to enable cross-domain tracking for Adobe analytics.

Troubleshooting: a website tag firing on engine pages

We recommend adding the snippet directly to the page rather than through Google Tag Manager. If you do deliver your **website** tag via GTM, make sure its trigger fires on your website pages but **excludes** the booking engine, or the two will both fire on engine pages. The triggers should look like this:

*** Adding Flip.to to your website? See [Set up your website](/docs/integrations/websites/set-up-your-website.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/booking-engines/set-up-your-booking-engine.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.