Google Tag Manager supports loading multiple containers on the same page. It is useful if you have several companies or organizations running on the same site, but for one reason or another (eg governance) you want to restrict access to your main container. In these cases, having the other party create their own container and add it to the site is the best of the bad options.
Well now we have it in Google Tag Manager 360 Regions Which makes managing multiple partner containers a little easier.
areas have the border, which are basically page rules that you can use to limit regions to only specific pages or groups of pages. Additionally, regions let you define type constraints for tags, operators, and variables (similar to
gtm.whitelist), giving you more control over what can and cannot run on your site these linked containers.
Simmer . Newsletter
Subscribe to the Simmer newsletter to get the latest news and content from Simo Ahava right in your inbox!
Why do we use regions?
Zones allow you to link multiple containers to a single location. However, instead of allowing the associated container to fully fire its tags and triggers, you can restrict access to the site on two fronts:
the border Lets you define page rules. The specified region is only active (ie containers are linked only) on pages that pass these rules. For example, you can restrict a shooting marketing agency container to only the landing pages you’ve created.
Thus, the linked container will be able to fire any of its tags, operators, and variables Not Restricted to pages that are included in region limits.
Create a new region
To create a new region, tap Regions Enter navigation, then red the new button.
Naturally, you can have more than one region defined in your container, and your regions can have more than one container associated with each region.
Attach a container to an area
In the region settings, you can associate a new container with the region by clicking Area Configuration to enter edit mode. Then click File There are no associated containers a box (if there are no linked containers yet), or the blue plus button to open the container link overlay.
In the overlay that opens, you can either click Add the container Code, which opens the list of containers you can access in the current account, or you can just write any container identifier into a file Container ID field. Remember to give the container an alias to help you identify it when looking at the region settings.
You can even click Add the container To open the list of containers you can access, and instead of selecting an existing container, you can click the blue plus button in the corner to create a brand new container within that workflow!
Once you have selected the container, click Add to add it to the current area.
Precautions are in place to prevent infinite loops (such as adding the current container as a linked container) and overly complex links (such as linking a container that links a container that links a container).
word in judgment
If you choose a container that you can access, you’ll see some extra container details In a container delimiter overlay.
This overview allows you to check files latest And published versions look. The latter is especially important, since this is the container that will be linked to the site itself. You can also check which users can access the linked container. These are all, in my opinion, features that are necessary to enhance the transparency of the workflow.
The fact that you can inspect and modify the users of the linked container means that you can set up everything for the region within the workflow, without having to move between different GTM management views.
In general, you may find it strange that you can only add Which The container ID you want in the region. In other words, you can drag any container into existence and have it fire tags, triggers, and variables on your site!
Well, when you think about it, this is how GTM works. Nothing prevents you from adding a container snippet from any existing container to your site, and nothing prevents you from linking a container to your region either.
This could potentially lead to governance issues, but type and boundary constraints are in place to mitigate somewhat the friction that arises from this open setup.
However, nothing beats communication. Even with regions, I would still suggest you work on improving communication structures within your organization and with your partners. You will also need to create a contingency plan for when something goes wrong with an associated container.
Add some borders
Boundaries are the rules of the page. Page rules are the conditions that the page must meet to pass the rule.
This means that these conditions must be present when the Google Tag Manager container is loaded. In other words, you can’t create a state like “Once the user clicks the X button, activate this area”. Though, see the next chapter for an exception.
In the picture above, all pages Is a good area boundary, and Page path contains / campaign / Good area boundaries. These conditions can be checked when the page is loaded.
event equals gtm.click He is Not Good area boundaries, because when page rules are evaluated, Event won’t be worth gtm.click.
However, there is an exception to how boundary conditions are evaluated. If you have One page application, or need to reevaluate boundary conditions when certain events (such as a custom event trigger to indicate page transition), you can click on the small point menu and select View custom rating. When you click on it, you’ll see a new view, which you can use to add triggers and which, when fired, will make the area reevaluate the boundary conditions.
As you can see, by default the operator used to evaluate boundary conditions is all pages. In other words, the conditions listed in the bounds settings must be present when the Google Tag Manager container is loaded for the first time.
However, by adding other operators to this list, the boundary conditions when firing will be re-evaluated. So if you have a one-page app, for example, the following process could happen:
When the container is loaded for the first time, the page path is
/, so the region is inactive.
When the user then clicks on a link to the campaign page, the single-page app changes the URL to
/campaign/without loading the page.
Now, since the URL changes without the page loading, GTM won’t reevaluate the region bounds by default, since it only does so when all pages are running on the initial load of the container.
By adding a trigger to this custom evaluation list, you can force GTM to reevaluate the boundary conditions, and possibly activate the area if the conditions pass.
For example, here I am using the log change operator to force the GTM program to reevaluate the state of the bounds on a browser log event, which is very common in single page transitions.
If the log event changes the page URL to
/campaign/, the area will become active.
type of restrictions
By default, linked containers run at full capacity. When a container is linked in an active region, the container is completely free to act as if it were added directly to the page.
With type of restrictions, you can specify the region to only allow certain types of tags, triggers, and variables to operate in the region. To enable type restrictions, turn on the toggle switch.
These are the default type constraints that exist if you switch the type constraint to:
All kinds of Google tags be Maybe. Google tag types are tags for Google products such as Google Analytics, Adometry, DoubleClick, and AdWords.
All kinds of trigger be Maybe.
All kinds of other tags be handicapped.
Likewise, if you disable operator and variable types, note that containers can contain very complex strings of variable operators and evaluation. By disabling one type, you are likely to disable all functionality in the linked container.
Once again, I stress the importance Telecommunications. It would be very fine to restrict only certain types of tags, operators, and variables that are fired into the region, but you need to make sure you know the situation in the linked containers before arbitrarily blocking their core functions.
To add or remove genre restrictions, first click on Select main type. This opens an overlay where you can toggle individual tag, trigger, and variable types on or off. You can also click File let everyone / restrict all A button to perform the respective selection action.
Preview mode has some additional functionality as well. When you preview the container in which you selected the region, the preview mode will show you whether the region is currently active or not. that Energetic Region means that any associated container will be able to fire its tags, operators, and variables (as long as the type constraints allow them to do so).
You can click on the region in preview mode to see details about it, such as the linked containers they contain and the type constraints in place.
areas that are Not Active will display as Inactive in preview mode.
If there is a custom rating rule that changes the activity status of an area, it will change from inactive to active in preview mode.
If you have a linked container in preview mode as well, and you have access to the preview in your browser, you’ll see a dropdown menu in the preview mode pane. This allows you to switch to preview mode for the linked container, if you wish.
Note that if you don’t have access to the linked container, you won’t have any visibility into what’s going on inside preview mode or not.
I think zones is a very elegant solution to the problem of access control rights and running multiple containers on a site. Until now, it has been tempting to add multiple containers to a page when working with partners who may have a different approach to container governance than you.
Regions don’t fix governance issues, but they do give you more tools to make governance easier.
The main problem with Zones is that you lack visibility into the linked container. This is understandable, because it will open a completely different can of worms if you have a view of the containers that you can arbitrarily add to your site.
For linked containers that you Act You have access, you can always put it in preview mode, which allows you to see what happens when the area is active.
Yes, it is a problem, this is only for Google Tag Manager 360. On the other hand, this is definitely a file Project – Adventure An advantage, which means that it makes sense to bundle it under a paid plan, along with a service level agreement and other types of support as well. It is not such an indispensable feature for most people. Regions or no regions, setting up a single container is still the preferred way to work with Google Tag Manager, at least in my opinion.