Google Tag Manager is a free Google tool that gathers all the tracking scripts of a website or app into a single container and decides under what conditions each one should fire, without touching the page code again.
The container is installed once. From then on, adding Google Analytics 4, the Meta pixel or Google Ads conversion tracking becomes a change you publish from the interface in a few minutes. In the UK and Europe there is a second step that few guides put up front: those tags do not fire freely, and the consent set-up decides which ones run and which ones stay idle.
Container, tags, triggers and variables
The container is the set of tags, triggers, variables and configurations installed on a given website or app. Google's documentation describes it as something that "can replace all other manually-coded tags on a site or app, including tags from Google Ads, Google Analytics, Floodlight, and 3rd party tags".
Three objects do the work inside the container.
- The tag is the code to run: a GA4 event, a Google Ads conversion, the Hotjar or Microsoft Clarity script.
- The trigger says when to run it: on page load, on a button click, on a form submission, when scrolling passes a threshold.
- The variable is the value the tag and trigger read: the page URL, an order value, the measurement ID.
Every publish creates a version. If a tag breaks the checkout, you roll back to the previous version and the site is fine again in under a minute, which does not happen with scripts pasted into the theme.
Tag Manager or the Google tag: what changes
Today the choice is not between Tag Manager and hand-written code. It is between Tag Manager and the Google tag (gtag.js), the single tag that Google Ads and GA4 generate on their own when you create the property.
| Google tag (gtag.js) | Google Tag Manager | |
|---|---|---|
| What it can send | Data to Google products only | Google, third-party and custom tags |
| How it is updated | By writing code in the pages | From the web interface, without touching the code |
| Version control | Depends on how you manage your code | Native workspaces and versions |
| Server-side tagging | Possible, but the server container is still managed in Tag Manager | Supported |
| Best suited to | Developers who only manage Google tags | Marketers and agencies with Google and third-party tags |
| Cost | Free | Free |
The test is practical. If everything you need to measure lives inside Google Analytics and Google Ads, and nobody will ever ask you to add an external script, the Google tag is enough. As soon as a non-Google ad pixel, a heatmap or a CRM comes into play, the Tag Manager container stops being an option and becomes the place to keep everything together.
In the UK, consent comes before the tag
In the UK, cookies and similar technologies are governed by PECR, and the ICO's guidance on storage and access technologies sets out how to apply it. Anything that is not strictly necessary needs prior consent, with a few exceptions. Since 5 February 2026, under the Data (Use and Access) Act 2025, one of those exceptions covers analytics collected solely for statistical purposes to improve the website, provided users get a simple, free way to object. The exception does not stretch far: according to the ICO it stops applying when the analytics provider uses the data for its own purposes, and advertising tags still need consent. The same guidance rules out silence or simply carrying on browsing as a way of giving consent, requires refusing to be as easy as accepting, and sets a rule that plenty of banners ignore: after a refusal, the ICO recommends waiting around six months before asking again.
On Google's side the mechanism is called consent mode. The developer documentation notes that it was updated in November 2023 with two extra parameters, and that anyone using it before must move to version 2. These are the four parameters that matter.
| Parameter | What it allows | What happens if it is denied |
|---|---|---|
| analytics_storage | Measurement cookies, for example visit duration | Analytics does not read or write its own cookies and receives cookieless pings, used for modelling |
| ad_storage | Storage of advertising cookies | No new advertising cookies are written; IP addresses are truncated on collection |
| ad_user_data | Sending user data to Google for advertising purposes | Enhanced conversions and user-provided data are not sent |
| ad_personalization | Personalised advertising | Remarketing in Google Ads, Display & Video 360 and Search Ads 360 receives no data |
A container installed without connecting it to the banner produces figures that look right and are not, and remarketing campaigns that optimise on incomplete signals. It is where measurement most often breaks on a UK or European site, before any discussion of events and e-commerce.
How much it slows the site down
The container file loads asynchronously and does not block page rendering. The weight comes from what you put inside it: every tag is code the browser has to download and run, and a container with twenty active scripts costs as much as twenty scripts pasted into the theme.
The difference is visibility. In Tag Manager the twenty scripts are a list you can read and switch off; in the theme they stay for years without anyone noticing. If you are working on load times, the container is the first place to open, not the last.
Client-side and server-side
The classic set-up is client-side: a single container in the browser that, for every event, sends an HTTP request to each destination. With ten destinations, that is ten very similar requests leaving the user's device.
Server-side tagging uses two containers: a web container in the page and a server container in a cloud environment. The browser sends a single request to the server container, which generates the specific calls for each vendor. Google lists three benefits: less load on the client, the ability to filter and modify incoming requests before they go out, and validated, normalised data.
There is a cost, and it is not the licence. The server container runs on infrastructure you pay for, and it has to be monitored and sized: Google warns that sending large volumes of conversions in short periods can overload the system and suggests batching. For a site with a few thousand sessions a month it makes no sense; for an e-commerce business that depends on well-measured conversions, it often does.
How widely it is used, in numbers
The tag manager market is not a contest. The W3Techs survey of 14 September 2026 across the websites it tracks gives these figures.
| Tag manager | Share of websites surveyed | Share of the tag manager market |
|---|---|---|
| No tag manager | 54.7% | n/a |
| Google Tag Manager | 45.1% | 99.6% |
| Adobe DTM | 0.2% | 0.5% |
| Matomo Tag Manager | 0.1% | 0.2% |
| Tealium | 0.1% | 0.2% |
More than half of all sites use none, so they install their code by hand or through plugins. Among those that do use one, Google against the rest is not a comparison. This has a practical consequence when you choose the tools in your stack: almost every vendor documents its Tag Manager integration and almost none documents the others.
When Tag Manager is not the answer
- It produces no reports. Tag Manager deploys code; it analyses nothing. Conversions, segments and bounce rate are read in Analytics.
- It does not remove the need for technical skill. Installing a standard tag takes five minutes. The data layer, e-commerce events and custom HTML tags require you to understand what you are writing, and anyone promising otherwise is selling you a course.
- It is an open door into the site. Anyone with publish permission can run arbitrary JavaScript on every page, including payment pages. Permissions should be treated as credentials, not as a courtesy login.
- Not every CMS supports it. If the platform does not let you add the container, Google itself points to the Google tag as the alternative.
In the containers we open during an audit we almost always find the same three things: tags from vendors who no longer work with the company, pixels from campaigns that ended years ago, and users with publish permission whose role nobody in the company remembers. A yearly review of the tag list and permissions takes ten minutes and is worth more than most of the technical optimisation done on top: it removes code from the site that nobody is looking at any more. If conversion tracking is what drives your campaigns, it is the same review that should come before any change to your Google Ads budgets.
Google Tag Manager FAQs
Yes. Both the Google tag and Google Tag Manager are free. There is a paid version, Tag Manager 360, within Google Marketing Platform, aimed at large organisations. Server-side tagging has no licence cost but does have a cloud infrastructure cost, because the server container runs on servers you pay for.
Tag Manager manages and deploys code; it produces no reports. Google Analytics collects the data and displays it. Tag Manager is how you install Analytics on the site, but the analysis happens inside Analytics.
Yes, if you reinstall Analytics through the container. Leaving both installations active means counting the same page views twice. The right sequence is: move the tag into Tag Manager, check in preview mode that the data arrives, then remove the code from the theme.
The container loads asynchronously and does not block page rendering. The weight comes from the tags it holds: twenty scripts inside Tag Manager cost the browser as much as twenty scripts pasted into the theme. The difference is that inside the container you can see them all and switch them off.
To install a standard tag, for example GA4 or a Google Ads conversion, no. To work with the data layer, e-commerce events and custom HTML tags you need to understand what you are writing, otherwise you collect the wrong data without noticing.
