Google Analytics 4 (GA4)
Google Analytics 4 (GA4) tracking can be implemented onto your booking engine to analyze visitor and booking journeys. The GA4 code can run alongside your Universal Analytics (UA) tracking if both will be in use for a period of time. Your digital marketing team or agency will be able to assist with the code to track the various elements of the guest journey and the overall transition.
Conversion tracking overview
With Google Analytics 4 conversion tracking, CRS sends a standardized set of data for tracking at the item level everything that is booked in a transaction.
📌Note: We push one conversion per item in the cart (one per booked reservation ID). This ensures proper mapping of the reservation to price data.
Data customization options
You can customize the output of the purchase event data, but the following caveats apply:
Fields marked as restricted cannot ever be removed or changed.
Fields marked as required must be present, but can be changed on an individual basis. If one is overridden, then the next caveat applies as well.
All other fields of each item type will be overridden as a single unit. If one is overridden, then all others are also overridden or removed.
Setup Google Analytics 4 conversion tracking
Follow the steps below to setup Google Analytics 4 on your booking engine.
To implement GA4 tracking or request customizations, open a support case [email protected]
Include your property's specific Google tracking information or any customization requests you would like for our professional services team to implement and we will provide a quotation.
This fee includes verification testing of the new code to ensure the data is recording accurately back to your GA4 account.
When the setup is completed below is the data you would expect to receive.
Events
The following non-standard events are sent by default. These are in addition to the standard pageview and click events:
Landing - Sent on pageview for the Index or Shop page.
Detail - Sent on pageview of any detail page.
Cart - Sent on pageview of the cart page.
Checkout - Sent on pageview of the checkout or combo checkout page.
Confirm - Sent on pageview of the confirm page, only at final confirmation of a reservation.
Lookup - Sent on pageview of the confirm page, if the page was loaded after the initial confirmation.
Cancel - Sent on pageview of the confirm page, only immediately after a reservation was cancelled.
Purchase - Sent on final confirmation of the reservation, with an ecommerce purchase event payload as defined below.
Transaction fields
The following fields of data will be provided:
Core transaction data
Transaction_ID (restricted) - The CRS reservation ID for this booking.
Currency - The currency code for the values in this transaction for example USD.
Shipping - Always "0".
Tax - The total tax for this booking (if appropriate), including taxes on addons.
Value - The total value of the booking, including add-ons. Excludes tax.
Affiliation - The HotelID used internal to the CRS. Guaranteed to never change.
Coupon - The promo code used for this booking (if any). Will be empty string if no promo code was used
Custom dimensions and metrics
Below outlines the custom dimensions and metrics:
dimension1 - The HotelID used internal to the CRS. Guaranteed to never change.
dimension2 - The hotel name at time of booking.
dimension3 - The name of the rate at time of booking.
dimension4 - The date of checkin. This date is in the format year-month-day (with prepended 0 if needed).
dimension5 - A pipe-separated list of addon names included with this booking. This does NOT list package inclusions - this is only guest-added items.
metric1 - Number of nights for the booking.
metric2 - The number of Adults in the booking.
metric3 - The total number of Children in the booking.
Items array
An array of items in this reservation. Will always contain one item for the stay itself, and any optional addons will be sent as individual items in this array as well.
Room stay item fields
For the room stay item, the following fields are sent:
Identification fields
item_id (restricted) - A string in the form of "HotelID_RoomCode_RateCode_CheckinDate_Nights_Occupancy"
item_name - A string in the form of "HotelID: RoomName @ RateName"
item_list_name - Always "RoomStay"
Pricing and quantity
price - The price of a single night.
quantity - The number of nights.
Classification fields
item_brand - The room code. Guaranteed not to change.
item_category - The HotelID used internal to the CRS. Guaranteed not to change.
item_variant - The rate code. Guaranteed not to change.
Custom dimensions and metrics
dimension1 - The hotel name at time of booking.
dimension2 - The room name at the time of booking.
dimension3 - The rate name at the time of booking.
dimension4 - The date of checkin. This date is in the format year-month-day (with prepended 0 if needed).
metric1 - Number of nights for the booking.
metric2 - The number of Adults in the booking.
metric3 - The total number of Children in the booking.
Addon item fields
For the Addon items, the following fields are sent:
Identification fields
item_id (restricted) - A string in the form of "HotelID_AddonID"
item_name - A string in the form of "HotelID: AddonName"
item_list_name - Always "Addons"
Pricing and quantity
price - The price of a single addon or item.
quantity - The number of addons or items.
Classification fields
item_brand - Always "Addon"
item_category - The HotelID used internal to the CRS. Guaranteed not to change.
item_variant - The addon Name.
Custom dimensions and metrics
dimension1 - The hotel name at time of booking.
dimension2 - Always "Addon".
dimension3 - The addon name at the time of booking.
dimension4 - The date of addon service. This date is in the format year-month-day (with prepended 0 if needed).
metric1 - Number of nights for the booking.
metric2 - The number of Adults in the booking.
metric3 - The total number of Children in the booking.
🤓Tip: Work with your digital marketing team or agency to understand which tracking elements are most important for your specific analysis needs before requesting customizations.