Tracking on your domestic site
Tracking on the localized sites
Glopal builds localized sites based on your domestic site. And since your tracking code is already on your domestic site, it means that it will automatically be on the localized sites as well. This allows you to track the activity from Glopal localized sites directly into your analytics tool such as GA.
In addition, for our own tracking on the localized sites, we use Google Tag Manager (GTM) to inject one, and only one, GTM container into those localized sites. The container contains Glopal’s GA tag enabling the tracking of various web and e-commerce metrics such as the following to name only a few:
- Traffic - Source of the traffic
- User path in the site - Visited pages
- Purchased items
When looking at the site's source code or when using a tag plugin, you can easily verify the presence of our tag in the localized sites. It is the tag ID: GTM-NQ33NR5.
Multi GTM containers
You may be using GTM in order to implement various tagging and add more context and metadata to the information that you send to Google Analytics, Universal Analytics property and/or Google Analytics 4 property.
Including Glopal's one, it means that there are 2 Tag Manager containers on the localized sites. When implementing our container, we paid attention to following Google’s guidelines and avoiding interferences with your container. And here's how it works:
- Glopal’s GTM container is using a separate GTM data layer “glDataLayer”, and we prefix “glopal_ga” to our cookies.
- So, it is only your GTM container, which includes tags, that will send data to your properties.
- Also, our data layer contains additional details on the localized sites, so you could read it and set up specific variables and triggers to enrich your analytics on the localized sites.
In short, there will be no duplicated data or conflicts caused by Glopal’s GTM on localized sites.