G Suite is now Google Workspace: everything your business needs to get work done.

Zones

Use zones to control and sandbox access to tagging on your sites.
This article is for advanced users who wish to set up zones for Tag Manager containers.

A zone allows you to link additional Tag Manager containers when your main container loads, so that the linked containers are allowed to fire tags on your website. Linked containers may be associated with any Tag Manager account, including containers owned and managed by 3rd parties.

Example uses:

  • A 3rd party ad agency is given access to a zone that fires tags on specific pages using only the tag types that are relevant to the advertising campaigns they are working on.
  • The recruiting team is given access to publish containers on the careers section of your website.
  • The marketing team is given access to publish containers on most pages, but are limited to only being able to edit (but not publish) more secure content (e.g. shopping cart pages) so that the changes must go through a review and approval process.

You can also use zones to link Tag Manager containers to Google tags (i.e., tags for related Google products, like Analytics and Ads) created using the global site tag (gtag.js) framework. 

You can set parameter values for zone tags, configure zone boundaries that define the pages on which the zone is active, and restrict the types of tags that a zone can fire. 

Combined with approvals, zones can help you create an effective tag management workflow for your organization. You can set completely different users and permissions for the main and linked Tag Manager containers, and for other Google tags that are linked to a zone. Admins of the main container do not need or gain access to the linked containers. 

Conversion linker and zones

The conversion linker tag automatically detects the ad click information in your conversion page URLs, and stores this information in first-party cookies on your domain. It is recommended to implement the conversion linker tag on all pages of a website. When implementing the conversion linker tag in a zone container, make sure that the container is linked on all pages of the website. If the zone container cannot cover all pages of the user's journey on the site, implement the conversion linker tag directly in the parent container for the site.

In some cases, it may be necessary to implement the conversion linker tag in the parent container for the site and in one or more linked zone containers. While this may result in the tag being triggered multiple times for a single click event, it will not impact the accuracy of conversion measurement.

Zone triggers and data layer event timing

If a zone tag uses a data layer event trigger, it is important to confirm that the data layer event takes place after the zone has loaded. If the data layer event occurs before the zone has loaded, the tag will not fire.

For example, if a zone loads at "All Page - Container Load", and a tag in the zone uses the data layer "consent initialization" event as its trigger, the tag will not fire because the "consent initialization" event occurs before "All Page - Container Load". In this scenario you would need to change the trigger for the zone tag to an event that occurs after the zone has loaded.

Create zones

Use this method to create a zone that links to a Tag Manager container. To link to Google tags, use the method described in Link to Google tags.

To create a new zone that links to a Tag Manager container:

  1. In Tag Manager, click Zones and then NEW.
  2. In Zone Configuration, click Add to add one or more containers.
  3. Select a container using one of the following actions:
    1. Click the container select icon and select a container from the current account.
    2. Manually enter a Container ID and optional Nickname
      Note: You can enter the ID of any container. It does not need to be in the same account.
  4. Optional: In Fields to Set, configure persistent parameter values for all pages that fire a given tag. See Fields to set for more.
  5. Optional: In Boundaries, select Some pages to specify which pages linked containers are allowed to fire tags on. See Boundaries for more.
  6. Optional (Tag Manager 360 only): Use the Type Restrictions toggle to specify which types of tags, triggers, or variables linked containers are allowed to fire. See Type restrictions for more.
  7. Give your zone a title and click Save.
  8. Save and publish your workspace for the changes to take effect.
Use this method to link a Google tag (gtag.js) to your main container.

You can link a main container to multiple Google tags (any gtag.js implementation) to ensure that all tags load on the same page. Each tag should reside in its own zone. Use this method, for example, to link a Google Analytics tag or a Google Ads tag to the same website.

To create a new zone for a Google tag: 

  1. In Tag Manager, click Zones and then NEW.
  2. In Zone Configuration, click Add to add a container.
  3. Manually enter any of the following in Container ID:
    1. Google Analytics (gtag.js) tag ID (G-XXXXXXXXX).
    2. Google Ads (gtag.js) Conversion tracking ID (AW-XXXXXXXXX).
    3. Floodlight (gtag.js) Conversion ID (DC-XXXXXXXXX).
    4. ...any gtag.js implementation (Tag-specific ID-XX....) .
  4. Optional: In Fields to Set, configure persistent parameter values for all pages that fire a given tag. See Fields to set for more.
  5. Optional: In Boundaries, select Some pages to specify which pages linked containers are allowed to fire tags on. See Boundaries for more.
  6. Optional (Tag Manager 360 only): Use the Type Restrictions toggle to specify which types of tags, triggers, or variables linked containers are allowed to fire. See Type restrictions for more.
  7. Give your zone a title and click Save.
  8. Save and publish your workspace for the changes to take effect.

Fields to Set

Fields to Set lets you initialize and configure settings for a particular gtag.js tag. Depending on the product linked, fields to set may also initiate certain behavior for that product. 

Settings configured here are equivalent to configuration parameters defined in your gtag.js code. For example, if you set the field name to send_page_view with a value of false for an Analytics tag, this will disable pageview measurement in the same way as the following snippet in your code:

gtag('config', 'TAG_ID', { 'send_page_view': false });

To learn more about how the fields to set can control behavior, read the product-specific documentation:

Boundaries

Boundaries allow you to choose which pages your zone fires on. 

The two main options are All pages (default) and Some pages. For Some pages, you can set the conditions for your zone container to fire. Conditions operate in the same way as triggers.

The underlying page view trigger is set to Consent Initialization by default. To access this setting, select 3 vertical dots icon > Show custom evaluation.

The default page view trigger was updated in March 2022 from Initialization to Consent Initialization. Zones created prior to this change are not affected and retain the Initialization page view trigger. 

Type restrictions (Tag Manager 360 only)

Type restrictions allow you to restrict which tags fire in your zone. This gives you additional control and security over how your zone behaves.

You can set restrictions based on tag types, trigger types, variable types and script types.

Restrictions default to:

  • Google tag types: All allowed
  • Trigger types: All allowed
  • Variable types: All allowed except custom JavaScript
  • Script and iframe tag types: None allowed
  • Pixel types: None allowed
  • Sandboxed script types: None allowed.
    Note: To allow use of custom templates, enable Sandboxed script types.

For non-360 Tag Manager users, no restrictions are applied to the zone.

Edit a zone

To edit a zone:

  1. Click Zones and then click the name of the zone you would like to edit.
  2. Edit Zone Configuration, Zone Boundaries, and Type Restrictions as desired.
  3. Save and publish your workspace for the changes to take effect.
Note: Communication across zones is not supported. Updates to the data layer of your main container may not get reflected in a linked container.

Related resources

Was this helpful?
How can we improve it?
Search
Clear search
Close search
Google apps
Main menu
Search Help Center
true
102259
false
false