The short answer
Google Tag Manager (GTM) is a container that sits on your website and holds your tracking code. Instead of a developer pasting each piece of code into the site, you add one GTM snippet and manage the rest from a dashboard. It controls what runs, when it runs and what information is sent.
It does not measure or report anything. Think of it as the switchboard, not the report. Setting it up and keeping it tidy is part of our tracking and analytics service, so this comes from doing the work.
Tags, triggers and variables
GTM has three building blocks. Once you know them, conversations with whoever manages your tracking become much easier to follow.
| Term | What it is | Example |
|---|---|---|
| Tag | A piece of code that sends data somewhere | Tell GA4 that a quote form was sent |
| Trigger | The rule for when a tag runs | When the thank-you page loads |
| Variable | A detail a tag or trigger can use | Which form it was, or the page address |
Everything lives in a container, which is the set of tags for one website. Changes are made in draft, checked in a preview mode, then published as a numbered version. If something goes wrong, an earlier version can be restored. That history is one of the main reasons to use it. A single trigger can also feed several tags, which is how one booking can be reported to GA4 and to an advertising platform at the same moment.
What it is and is not
- It is a place to manage tracking code without editing the website each time.
- It is a way to send one event, such as a form being sent, to several tools at once.
- It is a record of what was changed, when and by whom.
It is not an analytics tool. You will not find visitor numbers or enquiry counts inside it. Those appear in GA4, in your advertising accounts or in your call tracking service. The difference between the two Google reporting tools is covered in GA4 vs Google Search Console.
It is also not a consent tool, although it works with one, and it will not mend a form that fails to send. For where it sits among the other tools, see our guide to website tracking and analytics.
When you need it and when you do not
Not every business needs GTM. A simple site with one contact form, and GA4 added through the website platform, can be measured well enough without it. You probably do need it if several of these apply:
- You advertise on more than one platform, and each needs to know about enquiries.
- You have several forms, a booking tool and tappable phone numbers to measure.
- Changes to tracking currently wait on a developer.
- More than one agency or person adds code to the site.
- You need tags to respect consent choices in a controlled way.
Imagine a clinic that advertises on Google and on social media, takes bookings through an online diary and has a contact form. GA4 and each advertising platform need to hear about every booking. Without GTM, that means several pieces of code added by hand. With it, one trigger for a confirmed booking feeds every tag.
If they do, the practical steps are in our guide on how to track calls, forms and bookings. If none apply, leave it out. A half-used container is one more thing to maintain.

Who should own the account
Your business should own the GTM account and container, under a company login and not an individual's personal address. Agencies and freelancers should be added as users with the level of access their work needs, and removed when the work ends. Publishing rights deserve particular care, because anyone who can publish can put code on every page of your site.
If an agency created the container inside its own account, ask for it to be moved or for full administrative access. It is a normal request, and a reasonable supplier will not resist it.
Common risks
| Risk | What it looks like | What to do |
|---|---|---|
| Duplicate tags | Enquiries counted twice, because code sits in both the site and GTM | List every tag and remove the copy |
| Nobody knows what is installed | Tags from past campaigns and suppliers still running | Review the container at least yearly |
| Consent not respected | Tags fire before the visitor has chosen | Test with cookies declined |
| Untested changes | A published change breaks form tracking | Preview first, and name each version |
On consent: in general terms, UK rules expect non-essential cookies to wait for the visitor's agreement, and GTM will run whatever it is told to. The container has to be configured to hold tags back until your consent tool says otherwise. Check your own position against current ICO guidance. This is not legal advice.
There is also a security point. Tags are code, and a tag can read what is on the page. Only people you trust should be able to publish.
Questions to ask whoever manages it
- Who owns the account, and who can publish?
- Can you show me every tag, what each one does and which supplier it belongs to?
- Which tags record calls, forms and bookings, and when were they last tested?
- What happens when a visitor declines cookies?
- Is any tracking code also added directly to the site?
- How are changes named and recorded?
A competent manager can answer all of these in a short conversation. Vague answers usually mean nobody has looked for a while.
Common mistakes
- Installing GTM and leaving the old tracking code on the site as well.
- Giving publishing rights to everyone who asks.
- Leaving tags from finished campaigns running.
- Publishing without using preview.
- Using unclear names such as Tag 1 or New trigger.
- Assuming GTM handles consent without being configured to.
Common questions
Is Google Tag Manager the same as Google Analytics?
No. Tag Manager sends data, and GA4 receives and reports it. You can use GA4 without Tag Manager, but Tag Manager with nowhere to send data tells you nothing.
Will it slow our website down?
The container itself adds little. What affects loading is the number and weight of the tags inside it, so a container full of old tags can slow pages. Keeping it tidy matters.
Can we manage it ourselves?
Simple changes, yes, with some training and care. Setting up enquiry events and consent properly takes more experience, and mistakes go live on every page. Many owners keep ownership and let a specialist make the changes.
Do we need a developer at all?
Usually once, to add the GTM snippet to the site, and occasionally when a form or booking tool needs to pass extra information. Most day-to-day changes then happen inside GTM.
What to do next
Find out whether GTM is on your site, who owns the account and what is inside it. If nobody can tell you, that is the first thing to put right, before any new tracking is added.
If you would like someone to look, ask for a free 24-hour audit. A founder records a personal video walkthrough of your website within 24 hours, and it can point out what tracking is visible on it. No call is needed, and a 15-minute call is optional.
Want this applied to your website?
George or Nicholas will record a personal walkthrough of your site within 24 hours.
Not ready for an audit? See Tracking and analytics.
