Zones In Google Tag Manager 360

In Google Tag Manager 360, we now have Zones that make handling various partners’ containers quite a bit easier.

Google Tag Manager 360 zones

Zones have boundaries, which are basically page rules you can use to limit Zones to only certain pages or groups of pages. In addition to this, Zones let you define type restrictions for tags, triggers, and variables, which gives you even more control over what these linked containers can and cannot run on your site.

What is Zones?

Zones lets you link multiple containers to a single site. However, instead of allowing the linked container to fully fire its tags and triggers, you can restrict access to the site on two fronts:

  • Boundaries let you specify page rules. The defined Zone is only active (i.e. the containers are only linked) on pages which pass these rules. For example, you could restrict a marketing agency’s container to firing only on the landing pages they have created.
  • Type Restrictions allow only certain tags, triggers, and variables to work on the page. This is useful if you want to prevent linked containers from running Custom HTML tags or Custom JavaScript variables, for example.

Boundaries and type restrictions

A linked container will thus be able to fire any of its tags, triggers, and variables that have not been restricted on pages that are included in the Zone Boundary.

You can create a zone, it’s same as creating a tag. Once you start it, you can easily understand.

You can read zone in more detail at Simo’s blog.

Summary

I think Zones are a very smart solution to the problem of access control rights and running multiple containers on the site. Until now, it’s been appealing to just add multiple containers to the page when working with partners who might have a different approach to container governance than you do.

Zones don’t fix governance issues, but they do provide you with more tools to facilitate governance.

For linked containers to which you do have access, you can always put them in Preview mode, which lets you see what’s going on when the Zone is active.

Yes, it’s a bummer this is only for Google Tag Manager 360. On the other hand, this is most certainly an enterprise feature, which means it makes sense to package it under a paid plan, together with SLA and other support, too. And it’s not like this is a must-have feature for most. Zones or no Zones, a single-container setup is still the preferred way of working with Google Tag Manager, at least in my view.

Note: While creating zone’s whichever GTM container ID you will mention, from mentioned GTM container you can send any data to your Google Analytics property. For example: In the below image GTM container “GTM-KSNJJM” can send any data to your Google Analytics property, so we need to use boundary for the restrictions (don’t allow custom javascript tag etc.) There is no need to place “GTM-KSNJJM” container code on the website.

gtm zone

Image Source: Simo’s Blog

Please follow and like us:
569

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *

www.000webhost.com