1. Ensure that the Webvision page texts “Google script” and “Google Tag Manager” contain the necessary GTM code.

2. Extra datalayer values are passed via “Metadata” page text. This page text is the equivalent of “MExtraction” text asset in ADvance.

3. Ensure that the ADvance site branding contains the necessary GTM code.

4. ADvance text asset “MExtraction” should be populated with datalayer values. This text asset is equivalent to the “Metadata” page text in Webvision.

5. ADvance text asset “MExtractionCheckout” should be populated if you wish to track check-out steps in GA’s e-commerce reporting. For more information, please check the related documentation on e-commerce.

6. GA takes up to 24 hours to propagate new changes such as dimensions, views, etc..

7. GA custom dimension indices are important – those numerical values are used in GTM rather than the actual GA custom dimension names.

8. E-commerce tracking is triggered by page views and not by event-based triggers.

9. Note that all dynamic datalayer variables are case-sensitive, e.g.





Testing & Debugging

The most efficient way is to utilise GTM’s in-built preview function.

debugging 1

After you select Preview, please open the site in a new tab on the same browser. You should be seeing the GTM preview/debug console automatically.

debugging 2

debugging 3

Also, consider trying out ”Google Tag Assistant” add-on (for Chrome) to check the tags on your site: 

For Firefox users, there is a simlar add-on called “GTM Test Drive”:

Exporting / Importing GTM Configurations

It may be easier to export and import GTM configurations when there are multiple sites or you wish to overwrite any changes.

In fact, it is a good practice to export the GTM container prior to making any significant changes, so that it can be imported back with the original default settings if need be.

To do so, go to Admin panel in GTM:

export 1

1. Export – generates a JSON file for download:

export 2

2. Import – loads a selected JSON file from local machine:

import 1