# iHotelier

Adding Flip.to to your iHotelier booking engine is done in just two steps.

{% hint style="warning" %}
**Before you begin:**

* If you ask your Amadeus point person to grant Engine Container access to **<integrations@flip.to>**, our [Customer Success team](/docs/support/customer-success.md) will take care of configuring iHotelier for you.
* If you'd like to take care of the configuration below, you'll just need your **Flip.to companyCode**, which you should have received by email. If not, ask our [Customer Success team](/docs/support/customer-success.md).
  {% endhint %}

***

## Step 1: Add the Flip.to booking engine tag

* Click into **Tags** → **New** to create a new tag
* Set the **Tag Name** to **Flip.to booking engine**
* Set the **Tag Configuration** as **Custom HTML**
* Copy and paste the snippet below into HTML field
* Replace **`XX`** with your **Flip.to companyCode** (be sure to keep the single quotes)
* Set the **Tag Firing Option** to **Once per page**
* Set the **Firing Triggers** to **Page View Event** (fires on the engine's "content-view" event, after iHotelier configuration is available)

```javascript
<!-- Flip.to - Booking Engine Integration -->
<script>
!function(b,e,i){
(b[e]=b[e]||[]).push({flipto:i, event: 'flipto.configuration.load'})
}(window,'fliptoDataLayer',
{
    bookingEngine: 'iHotelier',
    companyCode: 'XX',
    code: '{{ihHotelID}}'
});
</script>
<script async src='https://integration.flip.to/K2X4KDP'></script>
<!-- Flip.to - End Booking Engine Integration -->
```

* After that's configured, it should look something like:

<figure><img src="/files/7t2ARULohZHPznlFYwp4" alt=""><figcaption><p>Example every-page tag setup</p></figcaption></figure>

<figure><img src="/files/9cIjG6dbNEgDX6z47zOc" alt=""><figcaption><p>Example triggering criteria to run on every page of the booking engine</p></figcaption></figure>

<figure><img src="/files/emin3dAYMAFZGDrqMXlz" alt=""><figcaption><p>Example trigger configuration for running on every page after booking engine configuration</p></figcaption></figure>

***

## Step 2: Add the Flip.to confirmation tag

* Click into **Tags** -> **New** to create a new tag
* Set the **Tag Name** to **Flip.to confirmation**
* Set the **Tag Configuration** as **Custom HTML**
* Copy and paste the snippet below into HTML field
* Replace **XX** with your **Flip.to** **companyCode** (be sure to keep the single quotes)
* Set the **Tag Firing Option** to **Once per page**
* Set the **Firing Triggers** to **Confirmation Page View Event** (fires on the engine's "content-view" event, only on the /confirmation page, after iHotelier configuration is available)

```javascript
<!-- Flip.to - Confirmation Page -->
<script>
!function(n,e,w){
w.eventData={category:'Booking_Engine',action:'Load',value:w.amount};
(n[e]=n[e]||[]).push({flipto:w,event:'flipto.confirmation.load'});
}(window,'fliptoDataLayer',
{
    bookingEngine: 'iHotelier',
    companyCode: 'XX',
    code: '{{ihHotelID}}'
});
</script>
<!-- Flip.to - End Confirmation Page -->
```

* After that's configured, it should look something like:

<figure><img src="/files/VnoE7duivjCFyXaSvR7Z" alt=""><figcaption><p>Example confirmation page tag setup</p></figcaption></figure>

<figure><img src="/files/vijnVrO8vwUGvHzOdSfq" alt=""><figcaption><p>Example triggering criteria to run on the confirmation page</p></figcaption></figure>

<figure><img src="/files/ZrtOzhl8iOmZrrfBxCf3" alt=""><figcaption><p>Example trigger configuration for running on the confirmation page after booking engine configuration</p></figcaption></figure>


---

# 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/booking-engines/vendors/ihotelier.md?ask=<question>
```

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.