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 are using Google Analytics 4 (GA4), you can either:

• Configure the GA4 code to RMS in the instructions that follow.

  OR

• Add your GA4 code to RMS in the instructions that follow. 

For more information on Google Tags, visit the Google Tag Manager Help Centre.

Guide

In the side menu of RMS, go to Setup > Online Bookings > Online Options.

1. Select a Property.
2. Navigate to the 'Market Tracking' tab.
3. Enter the Google Tag Manager Code.
4. Enter your Google Analytics Code (Optional). 

5. Select Save/Exit.
   

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).

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:

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