Overview
Tracking user behaviour is crucial for marketing purposes as well as optimisation purposes. TripBuilder supports the integration of Google Analytics 4 (GA4), Google Tag Manager (GTM), or other analytics scripts.
We highly recommend using Tag Manager associated with a GA4 property to get the most out of your data.
Please note: Google Analytics 4 replaced Google Universal Analytics by 1 July 2023. From this date, standard Universal Analytics properties stopped processing new hits. If you still rely on Universal Analytics, we recommend you switch as soon as possible. If you would like more information, you can visit the official Google Analytics page. |
Script Inserts
Whether you'd like to use GA4 directly or configure the GTM scripts and then load your GA4 via the GTM is up to you. All that's needed for the configuration in TripBuilder is the scripts provided by Google.
- Go to Settings.
- Click on Distribution Channels.
- Click on your TripBuilder ID.
- Click on the tab 3rd-Party Integrations.
- You have four fields where you can insert the tracking tools scripts. Usually, the tracking tools tell you where to insert the scripts:
- Header Begin
- Header End
- Body Begin
- Body End
- Copy and paste the scripts from your tracking tool where they indicate. For example, GTM asks to be inserted in the Header Begin and the Body Begin:
Click on Save. Confirm on your tracking tool if data is being received 24 hours later.
Important: If you want to collect data from the dataLayer script on your Google Tag Manager container, please add the header script of GTM on the Header End field in the TripBuilder Settings instead of Header Begin, as recommended by Google. |
Google Tag Manager Specifics
If you're using Google Tag Manager and Google Analytics 4 to track your application usage, we have created two support articles to help you optimise the data you collect.
Creating a Booking Funnel | How to Create a Basic Funnel Tracking using Google Analytics 4 and Tag Manager |
Using the dataLayer | How to use the dataLayer provided by TripBuilder in Google Analytics |
Booking Conversion Event
For GTM, TripBuilder has a built-in dataLayer.push on the booking confirmation page (last page of the checkout). The event needs to be explicitly enabled within TripBuilder and, by default, contains the following information:
- Booking ID
- Template ID
- Module IDs
- Template name
- Number of PAX
- Package sales price
Example:
dataLayer = [
{
"event": "conversion",
"conversion": {
"transaction_id": "04sjd54xte8m",
"template_id": "t1234567",
"template_name": "Grand Tour of Europe",
"module_ids": [
"m0000456",
"m0000123",
],
"pax": 2,
"total_price": {
"amount": 3000,
"currency": "EUR"
}
}
}
];
You can use this information when setting up your Events to GA4 using GTM. For example, when sending a purchase event, you can create custom parameters using the information of the dataLayer.
To enable this, go to:
- Go to Settings.
- Click on Distribution Channels.
- Click on your TripBuilder ID.
- Click on the tab 3rd-Party Integrations.
- Scroll down to Providers of Non-Bookable Content and enable the GTM Booking Conversion setting.
FAQ
Q: What parts of the application can be tracked?
A: The configured scripts are loaded on all pages related to consumers, travel agencies, and Cockpit.
Q: Is UA supported?
A: You're free to load UA via the script inserts. However, please remember that UA ends on 1 July 2023.
Q: Can we use MixPanel, Adobe Analytics, Hotjar, or another analytics service?
A: Yes, that's up to you. Thanks to the generic script inserts, you define what's loaded on all the pages.
Q: Can we insert a conversion pixel on a specific page?
A: This is not possible to do directly with Nezasa's configuration. However, tools like GTM provide such features as firing an event that can be an HTML code on a specific page.
Q: How are UTM parameters stored?
A: We read the following UTM parameters as part of our analytics filter, which is triggered on each incoming request and stored in our database:
- utm_source
- utm_medium
- utm_campaign
- utm_term
- utm_content
Since data is stored in our database, it is not publicly accessible.
Please note: The calls are grouped by the user's session id (this is maintained through a cookie across requests). Depending on how the calls are made, it may not always be the case that the calls are linked to the same itinerary. |
Comments
0 comments
Article is closed for comments.