Google Tag Manager (GTM) is a free Google tool for adding, changing and controlling the tracking code on a website from one web interface, without editing the site’s templates each time. You install one snippet once; after that, analytics, advertising and other tags are managed inside GTM and go live when you publish them.
How Google Tag Manager works
Everything sits inside a container, usually one per website. Three building blocks do the work:
- Tags are the pieces of code that send data somewhere: GA4 event tags, the Google Ads conversion tag, the Meta Pixel, LinkedIn’s Insight Tag and so on.
- Triggers decide when each tag fires: on every page, on a tap of the phone number, on a successful form submission, or on a custom event your developer sends.
- Variables hold the values tags and triggers need, such as the page address, the text of the clicked button, or an order value read from the data layer.
You make changes in a workspace and check them in preview mode, where Tag Assistant lists each event on the page and shows which tags fired and which did not. Publishing saves a numbered version, so you can see who changed what and roll back if something breaks.
There are two kinds of container. A web container runs in the visitor’s browser. A server container runs on a cloud server you control, receives data from the site, and forwards it to Google, Meta and others, which gives you more say over what each platform receives.
Why it matters
Without GTM, every new tracking request becomes a job for whoever maintains the website, and tags accumulate in theme files, plugins and page builders where nobody can see them all at once. With it, a UK business has its whole tracking set-up in one place that a marketer can read, test and audit.
That matters most for consent. UK sites need the visitor’s agreement before advertising tags run, and in most set-ups before analytics tags too. GTM is usually where that rule is enforced. Your consent management platform passes the visitor’s choice into GTM, and each tag is set to fire only once its category has been accepted. Tags placed outside GTM escape that control, which is a common reason a banner looks right while tracking still runs before anyone clicks Accept.
It also matters for speed and accuracy. A tidy container holding a dozen purposeful tags is lighter on page performance, and kinder to your data, than one carrying years of abandoned scripts from former agencies and free trials.
Common mistakes
- Running GA4 or the Meta Pixel through GTM while the same tag is also hard-coded in the site, so events are counted twice.
- Leaving publish access with everyone who ever worked on the site, including agencies that left years ago.
- Pasting third-party scripts into Custom HTML tags without checking what they do or giving them consent rules.
- Counting a lead on a click of the submit button rather than on a confirmed submission, so failed and empty forms count as enquiries.
- Publishing without testing in preview mode, or without a version name that says what changed.
- Placing the container snippet low in the page, so tags miss visitors who leave quickly.
How to act on it
If you already have GTM, start with an audit. Under Admin, User Management, remove anyone who no longer needs access and keep publish rights to one or two named people. Then go through every tag and answer three questions: what does it send, to whom, and which consent category controls it. Pause anything nobody can explain, and delete it once you are sure it is not needed.
Look through the site’s source for tracking code outside GTM, such as a GA4 tag added by a plugin, and remove duplicates. Test your key actions in preview mode with the banner accepted and again with it rejected. Name tags, triggers and variables in one consistent pattern so the next person can follow them.
If you do not have GTM yet, install it before adding any other tracking, so everything starts in one place. Setting up and maintaining a clean, consent-aware container is part of the measurement work in my performance marketing service.