Cross-domain tracking allows Google Analytics to track a guest’s journey across different sites as a single session. Without a White Label booking engine, your booking engine exists on a separate domain. Therefore, you need to configure cross-domain tracking. This will ensure that your GA4 data does not view the booking engine as a referring domain. To set this up, follow the steps below:
Note: Due to universal analytics being discontinued from 1 July 2023 and only Google Analytics 4 (GA4) being supported for the future by Google, this guide covers how to do it for GA4.
What do you need?
Your website domain e.g www.myhotel.com.
The RoomRaccoon booking engine domain e.g booking.roomraccoon.com
Access to your Google Analytics 4 (GA4) account with
How to configure cross-domain tracking?
To get your GA4) Measurement ID, open Google Analytics and click on the Admin Tab. Under the Property Tab on the right column, click on Data Streams.
2. Click on your site's data stream. If you still need to set one up, then click here.
3. Then navigate down on this Streams page to “Configure tag settings” under Google Tag:
4. Then, under settings, click on “Configure your domains.”
5. Click the Add Condition button.
6. Add the condition “Contains” and your booking.roomraccoon.com domain. Double-check which domain your booking engine is running off and use that:
7. Then click Save and add your GA4 measurement ID to your Google Tag Manager.
8. To add your tag to your Booking Engine, we advise that you do this by using a Google Tag Manager (GTM) account. If you don't have one, click on this link: https://tagmanager.google.com/ and select Create Account.
9. Then add a new tag, select GA4 as the tag type, add your Measurement ID, and make it fire on every page view.
10. Click save & then publish this. Add the GTM tracking code to your site and into your booking engine, which will look like this:
Good to know
- Read this article to learn how to use Google Analytics and Tracking Codes.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article