On this page
Google launched Tag Manager in October 2012, when marketers had to ask a developer for every new tracking code. The idea is simple: you add one snippet of Tag Manager to your site once, and from then on you manage in a web interface which other codes load, when and on which page. Those codes are called tags: the Google Analytics 4 tag, the Google Ads conversion tag, the Meta pixel, a LinkedIn Insight Tag.
What is Google Tag Manager used for?
A container holds three kinds of parts. A tag is the code that does something, such as sending an event to Analytics. A trigger says when: on every page, on a click on a phone number, on a submitted form. A variable supplies the value the tag needs: the URL, an order amount, the UTM code of a campaign. Each change is saved as a version you can test in preview mode and roll back if something breaks.
Your site, the container and the tags behind it
- 01
Your website
The Tag Manager snippet, once, in the head
- 03
Consent
Consent mode reads the choice from your cookie banner
- Google Analytics 4When: Every page, submitted formWaits for consent
- Google Ads conversionWhen: Click on your phone numberWaits for consent
- Meta pixelWhen: Enquiry submittedWaits for consent
- Own cookieless analyticsWhen: Every pageAllowed without
Tag Manager measures nothing itself. It loads the tags, and only after consent if you set it up that way.
Google Tag Manager vs Google Analytics
Most searches on this term mix the two up, so plainly: Google Analytics 4 measures and reports, on visitors, sources and conversions. Tag Manager measures nothing; it is the place from which Analytics and other tools get loaded. You can run Analytics without Tag Manager, with the Google tag placed straight in your site. How to set up Analytics, with or without Tag Manager, is covered step by step in Google Analytics 4 setup.
When Tag Manager helps, and when it does not
| Situation | Tag Manager | Directly in the code |
|---|---|---|
| One tool, Analytics, on a simple site | One layer too many | Simpler and lighter |
| Analytics, Google Ads, Meta and LinkedIn together | One place for all, with versions | Four snippets to maintain |
| A marketer without a developer | Add tags without a release | Every change via the developer |
| A site where speed matters | Every extra tag costs load time | Only what you need |
| Strict privacy rules or sensitive data | Easy to load too much unnoticed | Every code chosen on purpose |
The biggest risk is convenience. Adding a tag takes a few clicks, so codes that send data to third parties sometimes go live without anyone updating the cookie banner. In the EU every tag that sets marketing cookies or shares data for advertising has to wait for consent; do I need a cookie banner explains when. Tag Manager can enforce that through consent mode, but only if you set it up that way; what consent mode changed in June 2026 is in the consent mode change in Google Analytics.
The second risk is speed. Tag Manager itself is light, but each tag it loads is extra JavaScript. A container with twenty tags from campaigns long gone makes a site noticeably slower, which shows in your Core Web Vitals. Clean it up once a quarter.
Setting up Google Tag Manager in five steps
- Create an account and a web container at tagmanager.google.com.
- Put the two snippets on every page: a script in the head and a noscript block right after the opening body tag.
- Set up consent mode in the container, wired to your cookie banner, before adding other tags.
- Add your tags with their triggers: Analytics on every page, a conversion on a submitted form or a click on your phone number.
- Test in preview mode, and only then publish a version.
Server-side Tag Manager
A second kind of container runs on a server of your own rather than in the browser. The browser sends one signal to your server, and that server decides what goes on to Google, Meta or others. It gives more control over what data leaves your site and can make pages lighter, but it costs hosting and does not replace consent. The full picture is under server side tracking.
Short questions on Tag Manager
Is Google Tag Manager free?
Yes, the standard version is. Only the server-side variant costs money, for the server the container runs on.
Does Google Tag Manager set cookies itself?
Tag Manager itself does not. The tags it loads usually do, and those need consent in the EU and the UK.
What is the difference between GTM and the Google tag?
The Google tag (gtag.js) is one code for Google's own products, Analytics and Ads. Tag Manager can load that and any other tag, from one interface.