Google Tag Manager needs an owner more than it needs more tags

Google tags are becoming Tag Manager containers. The question for a small UK team is who can press Publish.

Google Tag Manager is Google's free tool for adding and changing tracking code on a website without a developer. For a small UK B2B team the real risk is who holds Publish rights, because one click puts a new script on every page. Name an owner first.

In short

  • Google announced on 20 August 2026 that Google tags will be upgraded to full Tag Manager containers, so most GA4 sites will have one whether they chose it or not.
  • On the free version of Tag Manager there's no approval workflow, so anyone with Publish rights changes the live site the moment they click.
  • Google advises at least two administrators and says the account should be managed inside your organisation, not by an external agency.
  • Since the Data (Use and Access) Act, statistical analytics cookies can skip prior consent but advertising cookies can't, which makes uncontrolled tags a UK compliance risk.
  • A half-hour check of users, version history, container size and duplicate GA4 tags needs no analyst.
A minimalist desk setup featuring a laptop, smartphone, and pen under soft window light.
Photo: Kindel Media on Pexels

Google Tag Manager is Google's free tool for adding and changing tracking code on your website without asking a developer. We'd say a small UK B2B team should worry less about setting it up and more about who can press Publish, because one click puts a new script on every page, so name an owner before adding another tag.

What is Google Tag Manager, and what changed in August 2026?

A tag is a small piece of code that sends information about a visit to a tool such as GA4, Google Ads or LinkedIn. Google Tag Manager is a container for those tags, so you add its two snippets of code to every page once and then add, edit and remove tags from the Tag Manager website rather than the site itself.1 In fact it's close to the default way of doing this. W3Techs, which surveys the technology websites run on, finds it on 44.7% of all websites and on 99.6% of the sites whose tag manager it can identify.2

On 20 August 2026 Google announced that Google tags, the single snippet GA4 and Google Ads generate for you, will be upgraded to fully capable Tag Manager containers, which means sites using only the Google tag gain Tag Manager's debugging and version control.3 Google says the upgrade won't change how the tag behaves on the page, and that its recommended container optimisation won't be applied automatically. It also says optimised containers send data straight to Google products instead of loading an extra script first, which should help page speed.3

So the line between "we just use the Google tag" and "we use Tag Manager" is fading, and what's left is the question of who gets to change it.

One Publish click changes every page

Tag Manager handles Google's own tags, many third-party tags and custom tags,1 and because a custom tag can hold almost any script, whoever can publish the container can, in effect, add code to your whole website without going near it.

Each container has four levels of access, which are read, edit, approve and publish.4 People with Approve access can create versions, and a version is recorded every time a container is published.5 Formal approval workflows, where one person requests a change and another signs it off, belong to Tag Manager 360, the paid enterprise edition.56 On the free version that most small firms use, there's no such step, and a person with Publish rights goes live the moment they click.

Google's own help page is blunt about the risks, which is more than most help pages manage. It recommends at least two active administrators so that one person leaving doesn't lock you out, and says the account should be managed by someone in your organisation, "not an external agency".4

Picture a 30-person consultancy whose web agency set up the container under its own login in 2021. Since then a freelancer has added a heatmap tool, a former marketing executive has added an ad pixel for a campaign that ended long ago, and nobody now in the building has admin rights. Nothing is broken, which is exactly why nobody looks.

The Data (Use and Access) Act 2025 changed the consent rules for some cookies. Section 112 amended regulation 6 of PECR, the Privacy and Electronic Communications Regulations, so cookies used for statistical purposes that don't significantly affect users no longer need prior consent.7 Advertising cookies and cross-site tracking still do, and the change only removes the consent requirement, so you still have to tell people what you're doing.7

For a B2B site, that splits your container in two. A GA4 setup you use to understand traffic may now sit outside the consent banner, but an advertising pixel added through Tag Manager on a Friday afternoon doesn't, and if it fires before anyone has agreed, your cookie policy is describing a website that doesn't exist. We've written before about why UK GDPR is about principles rather than consent, and the container is where those principles hold or quietly fail.

Do small B2B sites even need Google Tag Manager?

Well, the strongest case against comes from Google itself. Its comparison page says the Google tag alone is great for marketers who don't have a web development team or who use a content management system, and that if you only need default metrics such as page views, clicks and scrolls, you can set it up once and leave it.1 For a 25-page services site whose only tool is GA4, that's sound advice, and adding Tag Manager would just mean one more login for you to lose.

It stops holding up on two points. After August's change your Google tag becomes a container anyway, with its own users and permissions.3 And the Google tag can only send data to Google services,1 so the day you add LinkedIn's tag, a chat widget or a visitor identification script, that code has to live in the theme files, in a plugin or in Tag Manager. Of those three, Tag Manager is the only one that gives you a permission list and a dated history of every change.

So we'd keep the tracking simple and still use the container, because for a small team its real value is the audit trail, far more than any extra events it can measure.

What should you check in the container this month?

None of this needs an analyst, and it takes about half an hour.

Start in Admin, then User Management at both account and container level. Remove anyone who's left, question every agency or freelancer login, and make sure two people on your own payroll are administrators.4 We'd keep Publish rights to one or two people who know what the cookie banner is meant to block.

Then open the version history. Because each publish is recorded,5 you can see when tags arrived and who published them, and any tag nobody can explain should be paused and then removed. Google's web.dev guidance says to remove duplicate and unused tags, notes that paused tags still add to container size, and puts the container limit at 300 KB with a warning at 70%, while the median site container is around 50 KB.8 If your small B2B site sits well above that median, it usually has old campaigns still in it.

Finally, check that GA4 isn't loaded twice, once in the theme and once in the container. Two tags send two sets of page views, and the inflation spreads to everything that reads GA4. Scout, for example, pulls session depth and pages read per company from GA4, so a doubled tag would make every visiting company look twice as engaged, which is flattering and entirely wrong. If you've recently cleaned referral spam out of GA4, this is the same habit applied one layer down.

Knowing which tags fire is half the picture

Tag Manager tells you what code runs on your pages, but it can't tell you which businesses were reading them. Scout identifies the company behind a visit, gives each match a 1 to 99 confidence score with a one-line reason, and connects GA4 and Search Console to show you the pages each company read and the searches associated with it. Start a 14-day free trial, no card needed.

Frequently asked questions

Is Google Tag Manager free?

Yes. The standard version is free, and Google pitches it at individuals and small to medium-sized companies. Tag Manager 360 is the paid enterprise edition, which adds approval workflows and support from Google and its partners.

Can you remove Google Tag Manager from a website?

Yes, by taking its snippets out of the site's code or the plugin that adds them. Every tag loaded through the container stops with it, so move GA4 and anything else you still need first, then check your reports the next day.

How to provide Google Tag Manager access?

In Admin, open User Management at account or container level, add the person's Google account email and choose their permissions. Container access comes as read, edit, approve or publish, and we'd give Publish only to people who should be able to change the live site.

What is the difference between Google Tag Manager and Google Analytics?

Google Analytics 4 is where visit data is collected and reported. Google Tag Manager is a way of putting tags, including the GA4 tag, onto your website and managing them without editing the site's code. Tag Manager doesn't produce any traffic reports of its own.

It depends on the tag. Since the Data (Use and Access) Act amended PECR, cookies used for statistical purposes that don't significantly affect users can be set without prior consent, as long as you explain them. Advertising and cross-site tracking cookies still need consent, wherever they're loaded from.

Sources

  1. Google Tag Manager Help: Google Tag Manager vs. gtag.js support.google.com
  2. W3Techs: Usage statistics and market share of Google Tag Manager w3techs.com
  3. Google Tag Manager Help: Updates to Google tag and Google Tag Manager (20 August 2026) support.google.com
  4. Google Tag Manager Help: Managing users and permissions support.google.com
  5. Google Tag Manager Help: Publishing, versions, and approvals support.google.com
  6. Google Marketing Platform: Compare Tag Manager and Tag Manager 360 marketingplatform.google.com
  7. Bratby Law: Data (Use and Access) Act 2025, changes now in force bratby.law
  8. web.dev: Best practices for tags and tag managers web.dev