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.

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 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.

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.

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.