Google Tag Manager market tracking for the RMS Booking Engine.
Overview
Market Tracking for the RMS Booking Engine enables linking Google Tag Manager to track events throughout the online booking process.
Google Tag Manager allows an infinite and advanced array of events for tracking.
With the assistance of a Digital Analytics specialist, any number of events across the property's digital presence, including the RMS Booking Engine, can be tracked and reported on in Google Tag Manager.
If you also use Google Analytics 4 (GA4), set it up in one place only: either as a tag inside your Google Tag Manager container, or as a GA4 code entered in RMS. See Using a Google Tag Manager code and a Google Analytics code together below.
For more information on Google Tags, visit the Google Tag Manager Help Centre.
Important! If you are using Google Tag Manager with Google Analytics 4 (GA4) and have created custom events for any of the four GA4 events that RMS sends by default from the Booking Engine, you must remove the rmscloud.com domain condition from your GA4 tag configuration. Leaving the rmscloud.com domain as a condition on your GA4 tag when these custom events are also configured can cause duplicate event data to be recorded in GA4.
Please Note! RMS is highly configurable. Some Terminology, User Access & Permissions, Images, Labels, and Functions used in these articles may differ from your setup. CLICK HERE to find out more.
Guide
In the side menu of RMS, go to Setup > Online Bookings > Online Options.
- Select a Property.
- Navigate to the 'Market Tracking' tab.
- Enter the Google Tag Manager Code.
- Enter your Google Analytics Code (Optional).
Important! If you have configured Google Analytics 4 within your Google Tag Manager, Do Not add your Google Analytics Code here. Doing so will result in you receiving duplicate entries.
- Select Save/Exit.
Tip! An Enterprise database can pool analytics for multiple properties by using the same Google Tag Manager code in RMS.
Using a Google Tag Manager code and a Google Analytics code together
The Market Tracking tab can hold both a Google Tag Manager code and a Google Analytics code at the same time. Whether you should enter both depends on what is inside your Google Tag Manager container.
- Your container includes GA4 tags (for example, GA4 Configuration or GA4 Event tags): enter only the Google Tag Manager Code and leave the Google Analytics Code empty. If both are entered, GA4 receives each Booking Engine event twice and your reports show duplicate data.
- Your container has no GA4 tags (for example, it only holds a Meta (Facebook) Pixel, Google Ads, or custom HTML tags): you can enter both codes. The Google Analytics code sends the standard Booking Engine events to GA4, and the container serves your other tags. Nothing is recorded twice.
Important! RMS cannot see which tags are in your Google Tag Manager container. Check the tags in your container before entering a Google Analytics code, and check again whenever you add a GA4 tag to the container later.
Find your Client ID and Agent ID
The URLs in the next section include two placeholders that are unique to your property: the RMS Client ID (sometimes shown as Generated Code) and the Agent ID. You can read both values directly from your live Booking Engine URL.
Open your RMS Booking Engine in a browser. The path after ibe.rmscloud.com/ shows both values, separated by a slash:
ibe.rmscloud.com/{RMS Client ID or Generated Code}/{agentID}
A masked example looks like this:
ibe.rmscloud.com/XXXXXXXXXXXXXXXX/N
- Generated Code - the alphanumeric code that appears immediately after ibe.rmscloud.com/.
- Agent ID - the number after the next slash (for example, 1).
Tip! The Agent ID is the same number used for your RMS Book Now connection in the Channel Manager. If your RMS Book Now button is already configured, you can reuse the same Agent ID.
Important URL Updates
The Google Tag Manager (GTM) integration for the new Booking Engine is now complete.
This means that when your Booking Engine is migrated, the URLs in Google Tag Manager will need to be updated.
See the URLs below:
Important! The {RMS Client ID or Generated Code} and {agentID} remain the same between the Retiring URL and the Updated URL.
If you have a number at the start of your URL, e.g. bookings_12_.rmscloud, the number must be copied over to the Updated URL also, e.g. ibe_12_.rmscloud.
Landing Page
Retiring URL:
bookings.rmscloud.com/Search/Index/{RMS Client ID or Generated Code}/{agentID}/
Update to:
This URL is now the same as the Rates Page URL below
- ibe.rmscloud.com/{RMS Client ID or Generated Code}/{agentID}
Rates Page
Retiring URL:
bookings.rmscloud.com/Rates/Index/{RMS Client ID or Generated Code}/{agentID}
Update to:
ibe.rmscloud.com/{RMS Client ID or Generated Code}/{agentID}
Extras Page
Retiring URL:
bookings.rmscloud.com/Extras/Index/{RMS Client ID or Generated Code}/{agentID}
Update to:
ibe.rmscloud.com/{RMS Client ID or Generated Code}/{agentID}/Extras/
Checkout Page
Retiring URL:
bookings.rmscloud.com/Guest/Index/{RMS Client ID or Generated Code}/{agentID}
Update to:
ibe.rmscloud.com/{RMS Client ID or Generated Code}/{agentID}/Guest/
Confirmation Page
Retiring URL:
bookings.rmscloud.com/Guest/Confirmation/{RMS Client ID or Generated Code}/{agentID}
Update to:
ibe.rmscloud.com/{RMS Client ID or Generated Code}/{agentID}/bookingConfirmation
Comments
0 comments
Please sign in to leave a comment.