Please note: The pixel is for car hire implementations only. This is not applicable to flights.
Skyscanner JS Installations
Not available for GTM installations
To check if your landing pages are working correctly, go to your browser’s options and clear all cookies from your domain, navigate to one of your landing pages with a
skyscanner_redirectid parameter added to your query string and then examine your site’s cookies to check if it has been stored correctly under the name
To view the output of the validation client side use F12 in most browsers to display the console window and see how your implementation is performing
To enable client side debugging add the following line of code in the Loading your parameters section of the pixel documentation and call your test page:
To fire a pixel while in debugging mode add the following line of code, this will send the pixel with additional parameter js.test=trueattached to let us know it is a test (alternatively you can also add a test=true parameter if sending using your own call for the pixel)
In your browser’s console, you should now see something like the below when trying to send a pixel:
"Debug is on" "Skyscanner Conversion Pixel: 0 VALIDATION ERRORS FOUND" "Full URL: " "https://t.skyscnr.com/userorchestration/tracking.gif?redirectid=SkyscannerRedirectTest&totalprice.amount=59.00&totalprice.currency=GBP&bookingref=BOOK12345&totalprice.cc.amount=5.00&totalprice.cc.type=DEBIT&conversion.version=3&Type=conversion&js.dts=20150709%2013%3A20%3A40&js.domain=yourdomain.com&js.href=http%3A%2F%2Fyourdomain.com%3A3000%2F&js.refdom=undefined&js.ver=1.0.0"
If there is something wrong with your pixel or parameters it should be flagged with useful information in the console as below:
"Skyscanner Conversion Pixel: 2 VALIDATION ERRORS FOUND" "WARNING: Supplied redirectid (SkyscannerRediectTest) must be 22 characters long, currently 21 characters" "WARNING: totalprice.amount (59,00) contains commas, please ensure these are removed. If you are using as a decimal separator please replace with a decimal point"
When using setFire = true you will also see
"Pixel sent"as an output on the console as well as seeing the additional
&js.test=trueparameter on the pixel denoting this is a test for our systems
Not available for Skyscanner js installations
Test your landing page…
To test your new code, click on the dropdown next to Publish in the top right of the GTM screen and select the Preview and Debug option and you will now see the following on your screen…
Now, in the same browser, navigate to a page on your site which has the container you have added this tag to installed and add &skyscanner_redirectid=_skyscanner_testing_id and you should see a bar along the bottom containing GTM information, on the left of this panel click on Page View and if everything is working correctly you should now see your landing page tag firing under the Tags Fired On This Page heading, if not click the tag to find out why it didn’t fire, fix the problem, refresh the page on the GTM screen and then refresh your tag page to see If you have fixed it.
To confirm that you have managed to correctly set your cookie, please examine your cookies using your browser or other tools to see if a cookie for your domain titled skyscanner_redirectid has been set.
In order to test your new pixel, navigate to the Google Tag Manager screen and click the dropdown button next to Publish in the top right of the screen then select Preview and Debug
In the same browser, open a new tab and navigate to your testing page (this must match the criteria set in your trigger) and you should see a bar along the bottom indicating you are in test mode. Click the event down the side corresponding to your new tag (Page Loadin this guide) and you should see your tag listed
If you have checked the button to not fire tags unless published you will see your new tag in the Tags Not Fired On This Page, otherwise it will be in Tags Fired On This Page Section
Click the Variables tab to view all of the variables and their values and ensure that they are all populated correctly.
The final step if it not already enabled is to publish your tag with the Publish button, top right of the GTM screen, and Skyscanner should start receiving your pixels!
Available for both Skyscanner js and GTM installations
Once you are live with your pixel and sending Skyscanner information, you can use Flights/Car Connect to get a breakdown of your pixels hitting the Skyscanner system. Log in using the details provided by your commercial contact and using the left hand menu select Technical -> Conversion Pixel Health
This will display an hourly breakdown in both graph and table format for the past 24 hours detailing if there were any failures
To view a particular pixel failure, click the label under Failure Details to expand the failure types for any given hour and then click on any of the newly visible red labels to expand the parameters provided for the failed pixel to get an understanding of why something has failed
If the above does not help in anyway please contact - RevenueAndReporting@skyscanner.net or your Skyscanner commercial contact to request assistance
|RedirectID Value Missing||No redirect values are being passed - check that the parameter is being grabbed correctly from your landing page and that it is being read correctly when passed to the Skyscanner pixel|
|Some redirect values are making it through - Check that you are capturing the redirectID on Every landing page on your site|
|Some redirect values are making it through - Problems can often arise due to domain hopping or redirects when storing data to cookies and reading that data from a different domain i.e. www.flightsearch.com -> www.securebookings.com or www.flightsearch.es -> www.flightsearch.com, this is especially prevalent where users have 3rd party cookies turned off or when they have something like ad-blocker installed. Generally, the solution is to pass through values when switching between domains|
|Some redirect values are making it through - Check that you are storing the ID in a persistent way and not passing it through your site as a session variable, url parameter or other easily lost method.|
|Supplying ID correctly but it is failed when matching back to Skyscanners systems - Double check you have sent us the Skyscanner redirect id passed on deeplink to your site. If this is the correct value then please check that you are not converting the value to upper or lower case when storing or reading as this is case sensitive|
|Fails on totalprice.cc.amount||Value same as totalprice.amount - This field is supposed to show charges applied due to customers using particular payment methods i.e. a £5 surcharge for using a VISA card. Ensure it is smaller than the totalprice.amount|
|We do not have this information available - If you are unable to access the correct value or simply do not have it please set the field to -1 to differentiate between a zero value and a not supplied value|
|Fails on totalprice.cc.type||Field missing or undefined - Where a pixel is on version 3 (conversion.version=3) and a totalprice.cc.amount is supplied, we request the type of the charge i.e. VISA, DEBIT, MASTERCARD etc. If this information is unavailable or totalprice.cc.amount is unavailable as above please enter a -1|
|Numeric values are failing||Our currency uses commas as a decimal point - Please ensure that all monetary values using commas as decimal points have these replaced with a decimal point.|
|Our currency uses commas as thousand separators - Please strip out any commas that are being used as thousand separators to avoid this failing your pixel.|
|Pixel all being marked as duplicates||Booking ref is not unique - We use your booking reference against our redirect ID to de-duplicate any pixel information sent to us, if you have a lot of pixels being marked as duplicates please check that you booking ref is not generic (i.e. CAR or FLIGHT)|
|Pixel sent but does not appear on Skyscanner systems||Incorrect end point set - Please check the address used to set the endpoint in your script it should read
|Your RedirectID is incorrect or not recognised on Skyscanner systems - We link your data to our user and all their details based on the redirectID you provide. We try as far as possible to assign pixels missing ID information using referrer URLs and other crumbs of information recovered from a bad pixel call, however, without a valid redirectID we cannot guarantee that your conversion will be logged correctly|
|Our conversion volumes are much smaller than we expected||Not all landing pages not storing Skyscanner redirect id - However you choose to store the redirect id ensure it is implemented on all of your landing pages|
|Not all Thank you/Confirmation pages have been integrated - If you have multiple Thank you or confirmation pages, please ensure that each page implements the pixel code and can access the stored redirect id|
|Redirect ID info is incorrect - If your redirect id is not correct or does not match the Skyscanner system records it may have been lost for a number of reasons and may be available but not associated with your site. Please review the RedirectID Value Missing or Pixel sent but does not appear on Skyscanner Systems troubleshooting tips above for reasons this may happen|