trivago Conversion Pixel integration (deprecated)

To be able to view the conversion rate of clicks coming from trivago in trivago Intelligence, it's highly recommended to integrate our trivago Conversion API (link to the documentation). In this page you will find all the necessary instructions to integrate our Conversion Pixel, which is currently deprecated.

What needs to be integrated?

Advertisers need to integrate a simple <img> tag into advertiser's booking confirmation page. The image returned is a 1x1 png image with a white background.

<img height="1" width="1" style="border-style:none;" alt="" src=""/>

Where should the pixel be implemented?

To ensure a correct tracking, the <img> tag has to be integrated within the body tag in the HTML code of the booking confirmation page the user is redirected to once the booking has been completed. The Pixel should only be initiated if the user had a click-through via trivago within the last 30 days.

What needs to be integrated into the Pixel URL?

As shown in the example above the src attribute contains the Pixel URL. The protocol can be "http" or "https". Most booking pages use "https". The base URL is "" followed by a list of parameters separated by "&". Each parameter consists of a name and a value separated by "=". The parameters are case-sensitive.

Parameter Description Format Sample Mandatory
pagetype Mandatory tracking parameter (always the same). string track true
ref trivago Advertiser ID, as defined and communicated to the advertiser by trivago (always the same value for each advertiser). integer 12345 true
hotel The advertiser's unique hotel ID. Must be identical to the IDs used in the inventory feed string HOTEL537 true
arrival Arrival date UNIX timestamp 1524566908 true
departure Departure date UNIX timestamp 1524739708 true

If arrival and departure cannot be given in UNIX timestamp format, it can instead be given in the simpler YYYY-MM-DD format. If this format is preferred, then the date_format parameter has to be integrated in exactly this way:

&date_format=Y-m-d (don’t integrate it as &date_format=YYYYMMDD)

string Y-m-d false
volume Total booking price per stay (including all rooms, all nights, all taxes). number 150.70 true
currency Currency in ISO 4217 code. string USD true
domain Contains the trivago POS from which the visitor was linked through to the advertiser's site. Format is always the 2-letter top level domain of that country. string US false
booking_id The advertiser's booking reference.

For tEB, must be same as the reservation_id from the booking_submit response.

string AC500 true
margin Percentage which is received from the booking amount of the hotel as commission for the booking (in this sample case 15.8%). number 15.8 false
source Source parameter identifying transaction as tEB booking (always the same). text tebadv true

if booking coming via tEB

dateless Only for special cases and only if confirmed with trivago. integer 1 false

Sample URLs

Let's assume that the advertiser_id is 1232. For a booking for the property with hotel "MUC1345“ on, from 24th to 25th of April 2018 for 250.50 EUR, the advertiser receives a margin of 14.5% on this hotel.

Booking the advertiser's hotel with hotel "MUC1345“ from 20th to 26th of June 2018 for USD 240.00 and booking_id “book123”. Additionally, the Y-m-d date format is used.