How to Structure Containers in Google Tag Manager

How to Structure Containers in Google Tag Manager

When implementing Google Tag Manager, one of your first tasks is to decide on an appropriate structure of containers. Should you use a single container across multiple websites, or should each website have its own container?

The best approach for you will depend on your situation and the needs of your organization. In this article, we outline the benefits of each approach to help you make an informed decision.

1. One Website, One Container

If you have a single website on a single domain, a single GTM container will most likely be the best approach:

  • A single GTM container snippet can be deployed across all pages of your site.
  • All tagging can be managed from a central location, enabling consistent tracking and data quality across your site.
  • User permissions can be managed in one place, helping you maintain data security.

2. Multiple Websites, One Container

If you have multiple websites, using a common container will be a better approach if:

  • The websites have a shared CMS (content management system), template, and platform.
  • The websites share similar tagging needs.
  • One central team that manages the tagging for all websites.

Structure of Multiple Sites, One Container GTM

 

3. Multiple Websites, Multiple Containers

If you have multiple websites, using a separate container for each site will be a better approach if:

  • The websites have a different CMS, template or platform.
  • Each website has a distinct business objective or tagging need.
  • There are independent teams with varying access requirements that manage the tagging.

Multiple Sites, Multiple Containers Structure GTM

 

Do you need extra help deploying your website tagging through Google Tag Manager? Let us know!

By |2018-03-12T14:22:04+00:00January 29th, 2018|0 Comments

Leave A Comment