Welcome to docs.triptease.io

Overview

This page has all the information required to get you up and running with Triptease products as quickly and easily as possible.

What do we need from you?

To integrate with Triptease we need a single script to be placed across the full funnel of your website. It does not matter if the page is a brand.com page, or hotel vanity page, or hotel booking engine page - the same script works everywhere.

Your script tag

<script defer async crossorigin="anonymous" type="text/javascript"
src="https://onboard.triptease.io/bootstrap.js?integrationId=REPLACE_ME">
</script>

Our recommended way of getting this script onto your page is via a tag manager (e.g. GTM).

Yes, the script can work with cookie banners.

We recommend that you communicate the user’s consent preferences to the Triptease script. Please see consent mode guide for details.

Yes, the script is GDPR compliant provided you do one of the following:

Add the Triptease script all the time (prior to displaying the cookie banner, and regardless of consent chosen on the cookie banner) and communicate the user’s consent preferences to the Triptease script (details here).
OR
Add the Triptease script only when the user has given consent to Marketing/Advertising or all cookies.

We advise against choosing option 2. Please refer to this for detailed information on why the option is not recommended.

When should the script be added?

The script should be added as early as possible. It is designed to load asynchronously, which means it will not block the rendering of your page.

If the script has been set up to receive user’s cookie choices (option 1 above), you don’t need to wait for the user to explicitly make a cookie choice before adding the script.

If you’ve chosen to add the script after the cookie banner (option 2 above), ensure that once the user grants consent, the script is added immediately without requiring a page reload.

Where should the script be placed?

The script should be placed towards the end of the <body> tag.

If your booking engine is in an iframe, the script should be placed in two places:

On the parent page, towards the end of the <body> tag
On the booking engine iframe, towards the end of the <body> tag

How should your content security policy be changed?

If you have a Content Security Policy (CSP) in place, you will need to add triptease.io *.triptease.io to the script-src directive of Content-Security-Policy header.

This defines Triptease domain and subdomains as a trusted source for scripts and ensures that the Triptease script will not be blocked by the browser.

What does the script do?

The script performs the following tasks:

Detects the current location in the funnel (group page, hotel page, search page or confirmation page)
Loads the correct script for that location (i.e. on the booking engine it loads the script capable of reading search and confirmation pages)
Identifies your group/brand and the specific hotel
Loads the correct products for that page
Reads page specific data (see below) and provides it to the loaded products

What data do we read?

We read the following information (if available)

Search query
- Checkin
- Checkout
- Number of adults
- Number of children
Search results
- Room and rate names
- Price
Booking confirmation pages
- Booking reference
- Total price
- Room only price
- Room and rate names
Guest’s information
- IP address (always masked)
- Approximate Geo location (country/region)
- Browser and device information (from User Agent)
Hotel information
- Street
- Postal Code
- City
- Country
- Geolocation

What data do we never read?

We never read any sensitive information such as:

Guest details
- First / last name,
- Address
- Email (except when you have opted-in for Cart Abandonment feature)
- Telephone etc
Payment details
- Card number
- Expiry etc

For more information head over to our help section on How Triptease collects and uses data.

What is the performance impact on my page?

We have specifically engineered our scripts with following principles mind:

Always load after all of your content has finished rendering
Ensure everything is asynchronous and never blocks the main thread.
Only run the specific products required for your integration
Cache as much as possible
Always use HTTP2/3
Use GZIP and Brotli compression
Automatically detect changes without expensive polling

You can use Google Lighthouse or Page Speed Insights to measure our impact. You should see a minimal change in score with or without our script.

What happens if my booking engine is not supported?

If your booking engine is not supported, please reach out to us, and we may be able to integrate with your booking engine. Alternatively, you can provide us the data we need using industry standard Structured Data.