One container, many keys

Google Tag Manager Audit: Clear Out Dead Tags and Decide Who Gets to Publish

Somewhere in your Google account is a container that can put code on every page of your website, and a list of people who are allowed to change it. Most owners have never seen that list. The ones who look are rarely relieved.

November 19, 2026 · 10 min read

acmehomegoods.com · tag container register
Every tag, with a name beside it
Dead tags switched off, owners written down
draft register
Analytics page viewmarketing manager · keep
Chat widget, cdn.acme-chatwidget.exampleno owner since 2021 · cut
Ad pixel for a closed ad accountformer agency · cut
Custom HTML calling tags.acme-unknown.examplenobody knows · off for review
Heatmap trial scripttrial over · cut
Booking button click eventoperations lead · keep
People with Publish rights9 cut to 2
Illustrative: sample tag register for a fictional home goods store's container

The short answer

A Google Tag Manager audit lists every tag in the container, what it does, who asked for it and whether it still fires, then removes the dead ones and cuts Publish rights to the few people who need them. Every surviving tag gets a written owner. The result is a faster page and a shorter list of people who can add code to your site.

On this page
  1. Nine people can publish, and two of them left in 2022
  2. What the Optimizely incident says about your container
  3. Five permission levels and who should hold each
  4. Inside the junk drawer: tags that should go
  5. A named owner beside every tag
  6. Faster pages and fewer strangers after the cleanup
  7. When the cleanup is a job for us, and when it is not

Nine people can publish, and two of them left in 2022

A tag manager is a single script on every page that loads other scripts: analytics, ad pixels, a chat widget, a heatmap, a survey. Which ones load, and where, is set in a web dashboard rather than in the website's code. That is the whole appeal. A marketer can add a tracking pixel on Thursday afternoon without waiting for a developer. It is also the whole risk, because anyone with the right permission can add code to every page the same way.

The typical container tells a story in layers. A tag for an ad account closed three years ago. A chat widget from 2021 still loading on every page, answering nobody. Two analytics tags counting each visit twice, which explains a lot about last year's report. A custom HTML tag, pasted by someone whose name nobody recognizes, calling a domain nobody can identify. And on the user list, nine people with full Publish rights, including two agencies and an intern who now works for a competitor.

None of this is unusual, and none of it is the owner's fault. Tags are easy to add and nobody is ever assigned to remove them. The container keeps working, so nobody opens it, until a speed report or a security scare makes somebody ask what is in there. Lately, that scare has a name.

What the Optimizely incident says about your container

A tag manager and a testing tool share one design choice: a script from a vendor, on every page, whose contents change whenever somebody edits a dashboard. On November 16, 2026, that design choice was turned against the customers of one testing vendor. Optimizely's status page, in a notice posted November 17, 2026 at 01:02 UTC, said an unauthorized party "exploited a vulnerability in Experimentation" and used it to add malicious JavaScript to some customer projects. Our write-up of the Optimizely hack covers what that code did.

Nobody has said anything is wrong with Google Tag Manager, and we are not saying it either. The lesson is about the accounts around it. Among the steps Report URI, a company that sells script monitoring, recommended to affected customers in its report published November 16 and updated November 17, 2026: review and rotate users, API tokens and integrations. That is good advice for any dashboard that can put code on your pages, and a tag manager is exactly that kind of dashboard.

A container with nine publishers is nine passwords, nine inboxes that can be phished and nine people who can make a mistake on a Friday. Cutting the list is one of the cheapest security improvements a site can make. It costs nothing but an awkward email to a former agency.

Five permission levels and who should hold each

Google's help page Managing users and permissions, which we read on November 18, 2026, lists five permission levels for a container. The middle column quotes Google. The right column is our recommendation, labeled as practice rather than a Google rule.

Google Tag Manager container permission levels, as Google's help page described them on November 18, 2026, with our suggested holders
LevelWhat Google says it allowsWho we suggest holds it
No accessNo access to the containerEveryone who has left, and every agency whose contract ended
ReadView the container without making changesAnyone who needs to see what is set up, such as an analyst or a new hire
Edit"create workspaces and make edits but not create versions or publish"Agencies and staff who build tags for someone else to review
Approve"create versions, workspaces, and make edits but not publish"A senior marketer who checks work before it goes live
Publish"full rights to create versions, workspaces, make edits, and publish"Two named people at most, both on your payroll, each with two-step sign-in

Two publishers, not one, so a vacation does not freeze marketing. Not nine, because each extra name is another way in. An agency doing good work can build in a workspace with Edit and hand the result to your publisher. If that sounds slow, compare it with the speed of explaining to a payment processor why a stranger's script ran on your checkout.

Inside the junk drawer: tags that should go

Dead tags are not just clutter. Each one is code from a company you may no longer pay, running on pages your customers trust. The usual suspects:

  • The abandoned chat widget, still loading its script and its fonts on every page, connected to an inbox nobody checks.
  • Pixels for ad accounts that closed, quietly sending page views to a platform you stopped paying.
  • Duplicate analytics tags firing on the same page view, so every report double counts and nobody trusts the numbers.
  • Expired trials: a heatmap, a survey or a session recorder installed for one month, still running years later.
  • Custom HTML tags nobody can explain, the riskiest kind, because they can run any code at all.
  • Tags firing on every page when they only need the thank-you page, including the payment pages, where they matter most.
Flat sticker of a junk drawer bursting with blank sticky tags and a tangled cord, thick brown outlines, cream paper, mustard and teal, low hills at sunset
Most tag containers are a junk drawer: everything in it worked once, and nobody remembers why it is still there.

If the container loads on pages where customers type card numbers, its tags are part of what runs on your payment page. Requirement 6.4.3 of the card industry standard, PCI DSS v4.0.1, in effect since 2025, asks for an inventory of payment page scripts with a written reason for each, according to conference material from the PCI Security Standards Council. Our page on payment page scripts explains what that means. Confirm your own scope with your acquirer or assessor.

A named owner beside every tag

The cleanup is not the deliverable. The register is. Every tag that survives gets a line in a short document: what it is, what it does, who asked for it, who owns it now, which pages it fires on, what it can see and when it was last reviewed. A tag with no owner after two weeks of asking is switched off, and if nobody notices, it goes.

  1. 1

    Snapshot the container

    We save a copy of the current setup and work in a separate workspace, so the live version stays on record and untouched until you approve the change.

  2. 2

    Watch what actually fires

    We load your pages in real browsers, desktop and iPhone, and record which tags fire, where, and what each one contacts. The dashboard says what is configured; the browser shows what runs.

  3. 3

    Find an owner for each tag

    We ask your team and your agencies, by name, who needs each tag and why. Answers go in the register.

  4. 4

    Switch off, then remove

    Tags without an owner are switched off first, not deleted, so anything we misjudged can come back quickly.

  5. 5

    Cut the user list

    We recommend who keeps which permission level, and you or your publisher make the changes. Former staff and finished agencies lose access the same day.

  6. 6

    Write the rule for next time

    One paragraph on how a new tag gets added: who asks, who builds it, who publishes and where it is recorded.

Faster pages and fewer strangers after the cleanup

Every tag is code the visitor's phone must download and run. Fewer tags means less work for the browser and less waiting for the visitor, especially on a mid-range phone on a weak signal. We do not promise a particular score, because the gain depends on what was in the container, but removing tags that do nothing is the rare speed fix with no downside. For the rest of the speed picture, see site speed and Core Web Vitals.

Security improves in three ways. Fewer tags means fewer vendors whose bad day becomes yours. Fewer publishers means fewer accounts that can add code. And a short, known list makes a strict browser policy possible. Some tag setups ask for a policy setting called 'unsafe-eval', which lets a page run code built from text; MDN Web Docs, in its guide last modified March 22, 2026, says "developers should avoid unsafe-eval". Our Content Security Policy setup works out what your remaining tags really need.

A tag with no owner is not a tag. It is a tenant who stopped paying rent.

A container also changes by design, which rules out the usual trick of fingerprinting a script so the browser refuses an altered copy. That is why we pair the cleanup with script monitoring on sites that take payments or logins: something should notice when a tag starts calling a new address.

When the cleanup is a job for us, and when it is not

If your container has five tags, one owner and you can name what each does, you do not need us. Keep the user list short and look at it twice a year. If it has dozens, several agencies have touched it, or it loads on a checkout, a third-party script audit with the cleanup folded in is the efficient route. Moving experiments out of the browser entirely is covered on our server-side testing page.

Do it yourself if

  • Fewer than ten tags, all recognizable
  • One or two people can publish, both current staff
  • No custom HTML tags
  • The container stays off payment and login pages

Bring us in if

  • Several agencies have worked in the container
  • Custom HTML tags nobody can explain
  • The container fires on checkout or account pages
  • You need a written record for a processor, insurer or board

The work is from $575, depending on complexity, with a written estimate before anything changes. We respond the same business day during the hours on our contact page. Tracking itself, rebuilt cleanly, is part of our conversion tracking setup, and what to do with clean numbers is conversion rate optimization. If nobody on staff should own this list long term, a fractional CTO can, and our hosting and maintenance plans keep watch after launch. The rest of our website security services are a click away.

DataCram is a web studio in San Antonio, Texas, building for the web since 1999, working with businesses across the US by phone, video and a shared project page. Call (210) 346-0848, or start with the free website health check.

Questions owners ask about website security

We suggest two named people on your own payroll, each using two-step sign-in. One is a single point of failure during a vacation; nine is nine ways in. Agencies can build tags with Edit access and hand them to your publisher. That is our practice, not a Google rule.

That is why we switch tags off before deleting them. A switched-off tag stops firing but stays in the container, so it can come back quickly. We only remove it after the owner question has gone unanswered and nothing has broken.

Each tag is code the visitor's browser downloads and runs, so more tags means more work, most noticeably on phones. How much depends on the tags. We do not promise a score change, but removing tags that do nothing is a speed fix with no downside.

The tool is not the issue. The risk is who can publish and what they publish. Anyone with Publish rights can put code on every page, so a long user list, an old agency login or an unexplained custom HTML tag is where the exposure lives. A short list and a written owner for each tag fix most of it.

Yes. We work in a separate workspace, watch what fires in real browsers before changing anything, and switch tags off before deleting any. Your publisher approves the final version. If tracking needs rebuilding afterward, that is a separate, quoted piece of work.

It helps. They know why most tags exist, and their answers go straight into the register. If they no longer work with you, we can still audit from what the browser shows, and their access should end the same day.

Keep reading

Free · No obligation

Find out who can change your pages

Tell us roughly how many tags you run and who has worked in the container. Someone at DataCram replies the same business day with what a cleanup covers and what an estimate would include.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote