One 1,270-byte tag with no tag manager, no build step and no consent mode to configure, which is one fewer thing for a container to manage and one fewer thing to lose to blocking.
From $9 per month · None, so no consent banner · Full review →
Tag management
Google Tag Manager, explained
What GTM is, what it definitely is not, and why so many people believe it is an analytics tool.
Google Tag Manager is the most misunderstood product in this market, and the misunderstanding is specific enough to name: a large number of people believe GTM collects data. It does not. It is a container that loads other people's code on your pages, and a user interface for deciding when that code fires.
On its own, GTM measures nothing, reports nothing and has no dashboard of your traffic. If you open GTM expecting to see visitor numbers, you are in the wrong product, and the tool you actually want is the one GTM was deploying for you.
What GTM actually doesWhat GTM is notGTM versus GA4, since everybody asksThe real costs, which are not the licence
What GTM actually does
Three concepts and you have the whole product.
A container is a small script you put on every page. It is the only thing your developers install, and it is the last thing they need to touch.
Tags are the pieces of code the container loads: an analytics snippet, an advertising pixel, a chat widget, a heatmap script. Each one is a third party's code that would otherwise be pasted into your HTML by hand.
Triggers and variables decide when each tag fires and what data it receives. Fire the purchase pixel on the order confirmation page. Pass the order value from the data layer. Do not fire anything until consent has been granted.
The value proposition follows directly: a marketer can add, change or remove a tracking script without a developer, a deployment or a release cycle. On a team where adding a pixel means a two-week wait for the next sprint, that is worth a great deal.
What GTM is not
It is not analytics. GTM has no reports. It deploys Google Analytics, or Meta's pixel, or anything else, and those products hold the data. Asking GTM how much traffic you had is like asking a plug socket how much electricity you used.
It is not a consent solution. Consent Mode gives GTM a way to respond to consent signals, but something else has to collect the consent and store the record. GTM honours the decision; it does not make it or evidence it.
It is not free of performance cost. The container script is small, but what it loads is not, and GTM's job is precisely to make loading more third-party code easy. Containers accumulate. Tags added for a campaign three years ago are still firing on every page view on a great many sites, because nobody has a review habit and nothing prompts one.
It is not privacy-neutral. GTM itself sets no cookies. Nearly everything it is used to deploy does, and from your visitor's point of view the distinction is academic: the consent obligation attaches to what fires, not to what fired it.
GTM versus GA4, since everybody asks
These are two separate Google products that are almost always used together, which is where the confusion starts.
Google Analytics 4 is the measurement product. It collects events, stores them, and gives you reports. It is where your traffic numbers live.
Google Tag Manager is the deployment product. It is how the GA4 tag gets onto your pages, and how you configure what that tag sends without editing your site.
You can run GA4 without GTM by pasting the GA4 snippet directly, and plenty of sites do. You cannot run GTM without something for it to deploy, because there would be nothing to deploy. If you have one analytics tool and no advertising pixels, adding GTM buys you a second system to maintain in exchange for flexibility you are not using.
The real costs, which are not the licence
GTM is free, and that is the least interesting fact about its cost.
Container bloat. Every tag added is a tag nobody removes. The single most common finding in a tag audit is several scripts firing on every page for campaigns that ended years ago. Diagnose it by opening GTM's preview mode on your busiest page and reading the list of what fires.
Consent Mode configuration. Since March 2024, Google has required Consent Mode v2 for EEA and UK traffic to keep advertising and remarketing features working. Configuring it correctly, and keeping it correct as tags change, is real ongoing work that falls between the marketing team who owns GTM and the legal team who owns the consent policy.
A second surface to get wrong. Tag management moves deployment out of your release process, which is the point, and also removes it from code review, testing and rollback. A tag published at four on a Friday is live immediately with none of the safeguards your application code has.
Blocking. GTM is widely blocked by ad blockers and tracking protection, which means the tags inside it do not fire for those visitors at all. If your analytics sits inside your GTM container, you are losing exactly the visitors most likely to block it, and the loss compounds with whatever consent already cost you.
The options, at a glance
| Tool | From | Free tier | Cookies | Score |
|---|---|---|---|---|
| Absolutely Analytics | $9 per month | No free tier. A 30-day trial of the exact tier you picked | None, so no consent banner | 8.9 |
| Plausible Analytics | £9 per month | No, but the community edition is free to self-host | None, so no consent banner | 8.0 |
| Google Analytics 4 | Free with paid GA360 quoted | Yes, the standard product is free | Yes, so consent is required in the EU and UK | 4.4 |
| Matomo | Free self-hosted; cloud from €22 | Yes, the entire on-premise product | Optional, and it runs cookieless if configured | 7.0 |
| Piwik PRO | Free core tier, then quoted | Yes, a Core tier with a monthly action limit | Optional, and it runs cookieless if you configure it to | 6.4 |
| Cloudflare Web Analytics | Free for everyone | The whole product is free | None | 6.9 |
The rest of the field
A single lightweight script, deployable through GTM or pasted directly, with a documented proxy for first-party serving that meaningfully reduces blocking.
From £9 per month · None, so no consent banner · Full review →
The tag GTM most often exists to deploy. Configuration through GTM is the standard route, and Consent Mode v2 is required for EEA and UK advertising features.
From Free with paid GA360 quoted · Yes, so consent is required in the EU and UK · Full review →
Ships its own tag manager, free and open source, so analytics and tag management come from one vendor with no Google dependency.
From Free self-hosted; cloud from €22 · Optional, and it runs cookieless if configured · Full review →
Bundles tag management with consent management and analytics, which is the combination regulated buyers usually assemble from three vendors.
From Free core tier, then quoted · Optional, and it runs cookieless if you configure it to · Full review →
The extreme case: on Cloudflare-proxied sites there is no tag to manage at all, because measurement happens at the edge.
From Free for everyone · None · Full review →
Common questions
Is Google Tag Manager the same as Google Analytics?
No. Google Analytics 4 is the measurement product: it collects events and gives you reports. Google Tag Manager is the deployment product: it puts tags like GA4 onto your pages and controls when they fire. GTM holds no data of its own and has no traffic reports.
Do I need Google Tag Manager to use Google Analytics?
No. You can paste the GA4 snippet directly into your site and many people do. GTM becomes worthwhile when you have several tags to manage, or when marketing needs to change tracking without waiting for a developer release.
Is Google Tag Manager free?
The product is free, and GTM 360 exists within Google Marketing Platform for enterprises. The real costs are elsewhere: container bloat from tags nobody removes, ongoing Consent Mode v2 configuration for EEA and UK traffic, and the fact that GTM is heavily blocked, so tags inside it do not fire for a meaningful share of visitors.
Does Google Tag Manager set cookies?
GTM itself does not. Almost everything deployed through it does, and the consent obligation attaches to what fires rather than to what fired it, so a container full of cookie-setting tags needs a banner exactly as if they had been pasted in by hand.
Related guides
Do you need Google Tag Manager?Google Tag Manager alternativesServer-side tagging, explainedThe lightest analytics script
Everything above is my own opinion, formed from published vendor documentation and pricing read on 11 September 2026. There are no affiliate links on this site and no vendor has paid to appear. Corrections welcome.