Please note: The pixel is for car hire implementations only. This is not applicable to flights
The Skyscanner Conversion Pixel is a very small (1px by 1px) invisible gif which is called to let us know when a user converts or makes a purchase on your site, allowing ourselves and partners greater visibility on conversion rates etc. We currently support several integration methods so your company can choose the one best suited to your web technologies and services, you only need to select one.
Google Tag Manager (GTM) - We provide documentation on how to set up our conversion pixel using GTM, this is the best option for people who already have GTM implemented on their site. This method will also utilise one or more of the Skyscanner js scripts here
- User Redirects from Skyscanner.
- Partner site stores the
skyscanner_redirectidfrom the URL query string.
- User Purchases a ticket from the partner.
- User redirected to Thank you/Confirmation page
- Partner site retrieves the stored
skyscanner_redirectidand other parameters
- Partners Thank you page pushes parameters to
window._sstrackobject (see code examples)
- Partners Thank you page calls the Skyscanner pixel code (see code examples)
- Pixel query string is built and attached to pixel URL
- Pixel call is made to Skyscanner’s system
- Skyscanner processes the pixel and makes the information available via Flights Connect
- Data available for partner to view within (all being well) a 15-minute window
The code in this file handles the getting and setting of parameters to attach to the pixel request as well as the client side validation for debugging and the calling of the pixel itself.
Click the links below to view the example pages. To get an idea of how they work, right click and select view source to see the code they use…
You will also need to read and store the case sensitive Skyscanner RedirectID which is included in the parameters when we redirect someone to your site i.e.
We recommend storing this in any of the following:
- Cookie (preferred - see Landing Page section below)
- Local/HTML5 Storage (can often be more persistent than cookies)
IMPORTANT: Please avoid storing using
windowor other session based variables that can be lost when the customer closes their window/browser as this can cause the redirect ID to be lost and breaks the 30-day attribution window
- The pixel should only ever be fired once per booking i.e. on the thank you or purchase confirmation page after the booking has been completed
- If a customer converts multiple times these should each fire a separate pixel
- The generally agreed attribution model for Skyscanner partners is 30-days, this means that any purchase made within a 30 day window of being redirected from Skyscanner should have a pixel fired
- The RedirectID provided as part of the query string when we redirect to your site is the single most important piece of information in the pixel parameters
- Only purchases from customers attributable to Skyscanner should trigger a pixel call