Tracking requirements

In order to ensure accurate measurement of the tEB campaign, tracking needs to be implemented in three ways. All tracking integration information will be explained within the following section, along with some other additional information.

1. Tracking of tEB clicks

To enable advertisers to track the clicks leading to tEB and subsequent post-view conversions occurring outside of the tEB environment, advertiser can optionally provide their tracking pixel to be integrated on the tEB landing page.

To enable advertisers to track the clicks leading to tEB and subsequent post-view conversions occurring outside of the tEB environment, advertiser can optionally provide their tracking pixel to be integrated on the tEB landing page. Refer "Tracking parameters supported from trivago side" section for possible parameters.

2. tEB-specific tracking parameters within the exit link

Users have the option to exit the tEB path and continue the booking process directly on your website. For this purpose, a deep link to your hotel page will be placed on the tEB landing page.

It is important that you also attribute those users to tEB in your tracking, and not regular trivago traffic, to ensure conversions are measured accurately. Particularly while we run tEB at 50% against the traditional price search.

To enable advertisers to identify and track conversions of users that have chosen to continue without Express Booking, advertisers can provide specific tracking parameters to be added to the original deep link. This parameter also enables advertisers to distinguish between the deep links to avoid tracking an exit click as a click coming from the trivago platform.

3. tEB conversion API integration

For booking conversion tracking and view this data on trivago intelligence advertsier can implement server to server call supported by trivago. Refer this section for more details.

3. tEB conversion pixel integration

For booking conversion tracking and view this data on trivago intelligence advertsier can implement pixel supported by trivago. Refer this section for more details.

Tracking parameters supported from trivago side

Below is the list possible parameters supported in tracking data and tracking pixel sent from trivago side

Parameter Description Landingpage Submit Confirmation
hotel_id advertiser hotel id
start_date date of arrival in format: Y-m-d
end_date date of departure in format: Y-m-d
region 2-letter region code : e.g. GB
locale locale code : e.g. en_GB
currency currency code
adv_link advertiser link (if available at express side)
timestamp time of landingpage impression or booking
date_time time of landingpage impression or booking (ATOM formatted)
gbv gross booking volume price : user clicked on price search (if available at express side)
room_occupancies room occupancies as json-encoded value (e.g. [{"adults": 2},{"adults": 2,"children":[11,8]}])
device_type device type, possible fields: small / medium / large
user_ip_anonymised for example 127.0.0.xxx
user_ip_hashed for example 4f03eee243f3f97d14771fec94c17718
user_agent currency code
user_country country user selected during reservation
trv_reference click id, sent from trivago to express.
clicked_price price clicked by user, sent from trivago to express.
clicked_price_currency currency of clicked price by user, sent from trivago to express.
bucket_id (deprecated) bucket id (if available at express side) (deprecated)