How do I set up conversion tracking in Google Ads from hotel website to booking engine?
How do I set up conversion tracking in Google Ads for cross-domain tracking from a hotel website to a Sabre Synxis booking engine? I couldn’t find booking confirm page URL to set the thank you page conversion tracking in google ads and google analytics.
The short answer is:
Your issue is incredibly common with third-party booking engines like Sabre Synxis because they often use a single-page application (SPA) or prevent direct script injection on their server-side confirmation page, meaning there’s no unique “thank you page URL” to track.
The solution involves two steps: first, setting up cross-domain tracking in Google Tag Manager (GTM) for your main website and the Synxis domain to preserve the user session.
Second, because you can’t rely on the URL, you must use a server-side tracking solution that relies on Sabre’s APIs or booking confirmation data to send the conversion event directly to the Google Ads API, bypassing the Synxis front-end entirely.
The cheapest and most effective way to manage this is by using a Google Tag Manager (GTM) Server Container hosted by a service like Stape or Google Cloud Platform to receive booking data and forward it to Google Ads.
The long answer is:
The reason you can’t find a reliable “thank you page URL” is a combination of the Synxis platform’s technical setup and cross-domain tracking limitations.
The booking engine is a separate domain, and your website’s tracking scripts stop working effectively once the user lands there.
To fix the first issue, you must deploy the Google Ads Conversion Linker tag in your GTM Web Container and enable cross-domain tracking for both your hotel domain and the Synxis domain.
This ensures that the gclid (Google Click ID) tracking parameter is passed from your website to the Synxis URL, which is vital for attribution.
However, this only solves the link problem, not the missing event problem.
Since you can’t place a Google Ads Conversion Tag directly on the booking confirmation page (a page typically controlled by Synxis that doesn’t expose a clean URL path change), you need to get the booking data from a source you do control – your Sabre Synxis booking data.
You will need to leverage Sabre Hospitality APIs (or work with your Sabre contact to access booking event webhooks) to retrieve the confirmed booking details like the order ID, value, and currency immediately after the user completes the transaction.
This data should be sent to your own server, and this is where the GTM Server Container comes in as an excellent and cost-effective intermediary.
You configure your server to send the booking data (the Purchase or Standard Event equivalent) to your GTM Server Container’s endpoint.
From there, you use a Google Ads Conversion Tracking tag within the Server Container.
This tag then sends the final, complete, and accurate conversion information server-to-server via the Google Ads API directly to Google Ads.
The use of a simple, hosted GTM Server Container, like those provided by Stape or a minimal GCP instance, makes this traditionally complex API integration cheap and scalable because you don’t need to build and maintain a complex in-house server-side tracking infrastructure.
This server-side approach is the most robust and future-proof method, guaranteeing conversion accuracy regardless of browser, ad blocker, or third-party booking engine restrictions, and is the modern standard for sophisticated tracking.
About The Author
