Google Tag Manager Container
A Google Tag Manager container is a single script, identified as `GTM-XXXXXXX`, that a site loads once. It holds the tags, triggers and variables you configure in the GTM interface, and it decides which tags fire and when.
Why it matters
A GTM container is the control centre for all your tags. Instead of hardcoding dozens of tracking snippets into your site's HTML, you load one container script. The container reads the dataLayer from your page, evaluates its triggers, and fires only the tags you've configured in the GTM interface. This keeps your HTML clean, lets marketers manage tags without code deployments, and makes it easy to pause or change tags live.
Without a container, every change to your tags means an engineering deploy. With GTM, you update tags in an interface and they take effect immediately.
How it works
When you paste the GTM snippet into your site's <head>, it loads a script from Google: https://www.googletagmanager.com/gtm.js?id=GTM-XXXXXXX. That script is your container, identified by the unique GTM-XXXXXXX code. The container downloads the latest published version of your workspace configuration and runs it.
The container reads the dataLayer from your page. Events on the dataLayer (like event: 'purchase') trigger matching rules in your workspace. When a rule's conditions are met (if the event matches and the trigger fires), the container executes the tags attached to that trigger.
A container is a published snapshot of your workspace. Every time you publish in the GTM interface, you create a new container version. Live traffic hits the latest published version.
Server-side containers work the same way but run on your own server instead of in the browser. They receive data from a first-party endpoint on your domain and forward requests to vendors, giving you more control and privacy.
What does not matter
The container ID itself is not sensitive. It's visible in your network traffic and page source. What matters is who has access to edit the workspace, not who knows the container ID.
You can have multiple containers on one site, but it's uncommon. A single container usually handles all your tags.
Code example
A standard web container snippet looks like this:
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-ABCD1234');</script>
<!-- End Google Tag Manager -->
The GTM-ABCD1234 is your container ID. The script loads gtm.js?id=GTM-ABCD1234, which pulls down your published container configuration.
The network request looks like:
GET /gtm.js?id=GTM-ABCD1234 HTTP/1.1
Host: www.googletagmanager.com
How Scalpel shows it
Scalpel Tags detects the GTM container ID from the initial gtm.js?id= network request and also reads it from window.google_tag_manager, which the container script sets on load. The panel shows the container ID in the summary and links any tags running under that container.