What a Google Tag Manager container is, and how to read one without logging in

A Google Tag Manager container is a box that holds all of a website's measurement tags, the small pieces of code that record page views, form submissions, phone clicks and ad conversions. One snippet on the site loads the whole box, so instead of pasting a new bit of code into the website every time you want to measure something, you add a tag inside the container and Google Tag Manager (GTM) delivers it. Google's own documentation puts it as a collection of tags, triggers, variables and related configurations installed on a given website or app.

That one-snippet design is why GTM took over. Marketers stopped needing a developer for every tracking change, and developers stopped fielding requests to paste mystery scripts into the site. The trade-off is that the container becomes the single place where measurement either works or quietly fails.

What is actually inside a container?

Three kinds of things. Tags are the code that fires, such as a Google Ads conversion tag or a Google Analytics 4 (GA4) event. Triggers decide when a tag fires, for example on a thank-you page view or a button click. Variables feed values into both, like the page URL or a transaction amount. Most tracking disasters live in the triggers. In one account I took over in 2026, a conversion tag was set to fire on page load rather than on a completed enquiry, which meant 75% of clicks were counted as conversions. The tag was fine. The trigger was the problem. I wrote up that pattern in Google Ads says you are getting conversions, but there are no leads.

Where do I find the container ID?

Every container has an ID that starts with GTM- followed by a short string of characters, and it is the thing that tells the browser which set of tags to load. There are two places to find it, and which one you use depends on whether the account is yours.

If you have access, sign in at tagmanager.google.com and the container ID sits at the top right of the workspace, next to the Preview and Submit buttons. Clicking it opens the install snippets.

If you do not have access, open the website, view the page source, and search the text for GTM-. The ID is sitting in the snippet in plain sight, because it has to be for the container to load at all. This is the step that makes everything in the next section possible.

How many containers do I need?

The usual confusion is between an account and a container, and it costs people hours. The account is the topmost level of organisation, and Google's guidance is one account per company or organisation, not one per site. Inside that account you create one container for each website or app.

So a business with a main site, a separate booking subdomain and an Android app has one account and three containers, not three accounts. The container name should be the top-most URL of the site, such as www.example.com. You do not need a container per page, and setting one up that way is the kind of mistake that takes a year to notice and a weekend to unpick.

What are the container types?

Google offers five, and you pick the type when you create the container. Web is the one almost everybody wants, covering a website or web app, and there are separate iOS and Android types for mobile apps on those platforms. The remaining two are narrower: AMP, for sites built on Accelerated Mobile Pages, and Server, for server-side Tag Manager, where the tags run on your own infrastructure rather than in the visitor's browser.

The type cannot be changed afterwards, so a container created as the wrong type has to be rebuilt. It is worth the ten seconds of attention at setup.

How do I create a container?

Go to tagmanager.google.com and sign in with a Google account. Click the Accounts tab at the top left, then Create Account at the top right. Give the account your company name and set the country. In the Container Setup section below it, enter the site URL as the container name, choose the container type, and click Create.

Google then hands you two snippets, one for the head of the page and one for the body, and both need to be on every page you want to measure. If your company already has an account and you are adding a second site, return to the Accounts tab and create a container inside the existing account rather than starting a new account.

How do I read a container without logging in?

This surprises people: every GTM container is publicly readable. The snippet on a site loads the container from a URL of the form googletagmanager.com/gtm.js?id=GTM-XXXX, and you can open that same URL in your browser. First, view the page source of the site and search for GTM- to find the container ID. Then load the gtm.js URL with that ID and search the text for AW-, which is the prefix on Google Ads conversion IDs. If AW- appears, ads conversion tracking is at least configured. If it never appears, the site is spending on Google Ads with no conversion tag in the container. The same page-source check works for gtag installs. I use this alongside the Ads Transparency Center when sizing up any account before touching it.

It is worth being clear about what this does and does not tell you. You can see that a tag exists and roughly what it points at. You cannot see the conversion values, the account it reports into, or whether the trigger behind it is sane. It is a first read, not an audit, and it is usually enough to know whether a conversation is worth having.

1. 01

   Trigger

   A trigger decides when to fire

2. 02

   Variable

   A variable supplies the detail

3. 03

   Tag

   A tag sends the event

4. 04

   Recorded

   The platform records a conversion

Every container is publicly readable at googletagmanager.com/gtm.js?id=GTM-XXXX, so you can check whether a site measures anything at all without an account and without asking permission.

Why do containers matter in takeovers and relaunches?

Because the container is where the truth lives. Reports can look plausible while the tags behind them fire on the wrong trigger, and a website relaunch can silently drop the GTM snippet altogether, which is one of the ways leads vanish after a relaunch. Untagged days also bleed your remarketing audiences, which I explain in what remarketing is, and why untagged days never come back.

The container also keeps you honest. Across my takeovers I logged 70 suspected tracking problems from the outside, from dashboards and symptoms. Once I opened the GTM containers and checked, 30 of them proved false.

That is nearly half of the alarms dissolving on contact with evidence. So before you accuse an agency of broken tracking, or pay someone to rebuild it, read the container. It takes ten minutes, costs nothing, and needs no login. If what you find is genuinely broken, that is a bounded fix, and it belongs in the same evidence file as the three receipts you should be getting anyway.