Google Triggers Reference
Notice of usage: Google Tag Manager (GTM) and Google Analytics 4 (GA4) are third party services and we provide this integration as is. We support a set of custom events and Data Layer variables for use with GTM and GA4, however we have no control over what happens to them and how they are used. The basic setup examples we provide have been tested and verified to work with the Mews Booking Engine, however if you need a more complex setup then we cannot provide the support to do so and we recommend to ask a specialist to set it up and test it for you.
This reference provides details of custom events and Data Layer variables generated within the Booking Engine, which can be used to trigger analytics tags to fire, i.e. to send data to Google Analytics. You will need to reference these events and variables when setting up tag triggers in Google Tag Manager.
Contents
Data Layer variables
All event data is passed to Google Tag Manager through a Data Layer.
What is a Data Layer?A Data Layer is a Javascript object in a website or app that collects analytics data in a standardized way. It acts as a layer between the site and the tag management system. The layer stores values, such as page name and URL, that are populated automatically when a visitor uses the site. The data is transferred into tag management variables and can be used to activate triggers in your tag configurations. Google Help — The data layer
To use data from the Data Layer in your tags, in the GTM configuration set up a Variable with a suitable name as a Data Layer Variable (DLV), like this:
The Custom events reference below describes which Data Layer Variables are relevant to which custom events.
Prices: Note all prices currently presented via the Data Layer are gross prices, i.e. including taxes and fees.
Custom events
GA4 pageview events
GA4 eCommerce events
Data Layer Variables in events
Each event is fired with a standard set of data:
If a user selects a hotel or property in the Booking Engine, information about it is also added to the event. In Singlehotel mode, the property is always selected.
Pageload events with the 'ga4_' prefix also have the following attributes available in the Data Layer:
Some events expose additional DLVs. These are described separately for each event.
Tracking consents
GA4 pageview events
ga4_ApplicationLoaded
Event which fires when the application is loaded for the user
ga4_VoucherAdded
A voucher has been added into the booking
ga4_PropertiesLoaded
The properties selection step was loaded for the user
ga4_CalendarLoaded
The calendar step has been loaded for the user
ga4_CategoriesLoaded
Categories / room selection has been shown to the user
Each of the items in arrays follows the google Item specification for ecommerce, for example:
ga4_RatesLoaded
Rates selection has been shown to the user
ga4_ProductsLoaded
Products selection has been shown to the user
ga4_PromotedServicesLoaded
Promoted Services has been shown to the user
ga4_SummaryLoaded
Summary step has been shown to the user
ga4_DetailsLoaded
The final screen with form to fill in has been shown to the user
ga4_BookingCreated
Mews created a booking within the PMS. Additional information is available in the
purchase
event.
ga4_ConfirmationLoaded
The confirmation screen has been shown to the user. This step is shown after returning from the payment gateway as the final step of the process.
GA4 eCommerce events
Please follow the Google guide for tracking eCommerce in GA4. You need to set up events with all mandatory parameters so they are tracked correctly. We are pushing all available variables into the eCommerce tracking for more advanced setups as well.
select_promotion
Voucher has been added to the booking
view_item_list
List of available rooms shown to user for eCommerce purposes
add_to_cart
User added room and products to cart
Example:
remove_from_cart
User removed an item from the cart. See
add_to_cart
for event parameters.
begin_checkout
User started the process of check-out. See
add_to_cart
for event parameters.
add_payment_info
User added payment information.
purchase
Purchase made. This is the most important eCommerce event. We expose many variables in the event which can be used for advanced tracking. See the example for full description.
The most important variables are:
Example:
Visual Diagram of GA4 Events in the Booking Engine
The following diagram provides a visual representation of GA4 related events and their respective trigger points within the booking engine.
Last updated