Analytics and Tracking

Container

Also called GTM container, web container

The Tag Manager unit installed on a site, holding every tag, trigger and variable under a single GTM identifier.

Quick facts: Container

Category
Analytics and Tracking
Also called
GTM container, web container
Level
Beginner
Affects
Tag deployment, data accuracy, access control
Where to see it
Google Tag Manager (Admin, Container settings), Tag Assistant, page source
In this article4
  1. How a container works
  2. Why the container matters
  3. Where containers go wrong
  4. How to act on it

How a container works

A container is the box that holds everything you configure in Google Tag Manager: the tags, the triggers, the variables and the settings that join them together. It has its own identifier, in the familiar GTM- form, and that identifier is written into the snippet installed on the site. When a page loads the snippet, the browser asks Google for whatever that container currently publishes, and runs it.

The type is chosen when the container is created and cannot be changed later — a web container for a website, separate ones for iOS and Android apps, and a server container that runs in cloud infrastructure you control rather than in the visitor’s browser. Inside a container, editing happens in a workspace, a set of edits is frozen into a version, and only a published version reaches real visitors.

Why the container matters

It is the unit of deployment and the unit of access at the same time. Everything inside one ships together when you publish, and anyone granted rights on a container holds them over every tag in it. So deciding how many containers to run is an organisational question as much as a technical one. One per website is the sensible default; separate containers make sense when different teams, agencies or markets are genuinely responsible for different sites.

It is also the only honest inventory of third-party code on your site. If a script is not in the container and not in the theme, nobody put it there on purpose — and that is worth knowing before a privacy review or a page-speed complaint.

Where containers go wrong

Two containers firing on the same page is the classic fault, usually because a plugin installs one while a developer has hand-coded another. The result is doubled page views, doubled conversions and reporting nobody believes. It is easy to miss, because nothing breaks visibly.

The opposite happens just as often: the snippet lives on most templates but not all of them. Checkout, the thank-you page, a landing page builder or a blog on a subdomain get forgotten, and the gaps look like sudden traffic drops rather than missing code.

Sharing one container across unrelated websites causes a slower kind of damage. Every trigger then has to be fenced by hostname, and the first person who forgets leaks a client’s tags onto someone else’s pages.

How to act on it

Start by confirming that exactly one container fires per page, using Tag Assistant or by searching the page source for the container ID. Then walk the full set of templates — home, service page, blog post, form confirmation, cart, checkout — rather than assuming the theme covers them all.

After that it is housekeeping. Give the container a clear name that includes the site it belongs to, keep publish rights narrow, and record who owns it, because containers usually outlast the agency that built them. If the site also needs collection that survives ad blockers, that is a job for a server container alongside the web one, not a replacement for it. Inheriting a container with unexplained tags is a good reason to book a Tag Manager review before adding anything new.

Do and do not

Do

  • Confirm exactly one container fires on every page
  • Check the snippet on checkout and confirmation templates
  • Name the container after the site it serves

Do not

  • Run one container across unrelated client websites
  • Let a plugin add a second container alongside yours
  • Hand publish rights to anyone who requests access

Questions people ask about this

How many containers should a business have?

Usually one per website. That keeps publishing simple and permissions meaningful. Use separate containers when different teams or agencies own different sites, when a brand needs its own access, or when one property has far stricter privacy requirements. Splitting a single site across several containers rarely helps and makes duplicate firing much harder to spot.

Can I move tags from one container to another?

Yes. Tag Manager can export a container, or selected tags, as a file and import it into another one. Review the result carefully afterwards: measurement IDs, conversion IDs and hostname conditions all travel with the export, so an imported tag can quietly start sending a new site's data to an old account.

What is a container ID?

It is the identifier that ties the snippet on your pages to the configuration in Tag Manager, shown at the top of the workspace and beginning with GTM. Anyone can read it in your page source, which is normal and not a security risk on its own. Access is controlled by account permissions, not by hiding the ID.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.