Web Analytics · Google Tag Manager

GTM Audit & Container Cleanup

Nothing leaves the container on a hunch; every removal carries the evidence that made it safe.

When several agencies and in-house teams have worked in the same container, forgotten tags pile up quickly. We trace what still serves a purpose, what can be removed safely, and what continues to fire where it does not belong. You end up with a GTM container with a complete inventory, confirmed duplicates resolved, and a documented reason for every item that remains.

Plan a GTM cleanupAll Google Tag Manager Consulting tasks
A Zeo specialist sweeping obsolete tags out of an open GTM container

Some of the 500+ brands we've worked with

See all references
  • LC Waikiki
  • Lexus
  • Findeks
  • Mustela
  • Country Floors
  • Groupama
  • Elele
  • Amazon
  • BMW
  • Shell
  • Hyundai
  • PepsiCo
  • Red Bull
  • Decathlon
  • MediaMarkt
  • Bayer
  • Sanofi
  • EY
  • KPMG
  • GE
  • 3M
  • Domino’s
  • Trendyol
  • Hepsiburada

How we run it

Four passes through the container before anything gets deleted

We examine the layers of tags, triggers, variables, and access that build up when a container changes hands without clear ownership. Four careful passes take the container from an uncertain inventory to a documented, understandable setup.

How we hold ourselves to it

  • Every tag, trigger, and variable gets counted — We list what exists, when it last fired, and whether anyone still recognizes it.
  • Find duplicates and conflicts — We check for the same pixel or event firing from two different tags, or triggers that silently override each other.
  • Who still has access, and should they? — We check user permissions against who's actually still working on the account and tighten what's too open.
  • Safe to remove isn't the same as forgotten — We separate tags that are clearly dead from ones that fire rarely but still matter, so nothing useful gets deleted by mistake.

  1. Pull the full inventory

    We export every tag, trigger, and variable in the container and note firing frequency where GTM exposes it. A specialist confirms firing frequency GTM doesn't show.

    Container inventory

    Illustrated figure stepping across a page of listed links

  2. Test in Preview mode

    We walk key pages with GTM Preview open to see exactly what fires, in what order, and whether anything doubles up. A person walks the pages Preview can't script.

    Preview test log

    Illustrated figure watching a monitor full of tracked rows

  3. Confirm with your team

    We go through anything ambiguous with whoever's been maintaining the container, so nothing gets removed that someone still relies on. Whoever maintains the container signs off on each item.

    Disposition list

    Two illustrated figures talking across a row of microphones

  4. Clean up and document

    We remove or pause what's confirmed dead, fix confirmed duplicates, and write down what's left and why. A second person signs off before we call it done.

    Cleanup log

    Illustrated figure pruning excess pages from a document tree

Nothing gets deleted just because nobody remembers adding it

Automation diffs the exported tag list against the previous export, flags tags that fire twice in one pass, and drafts the disposition list. Removal is never automatic: a specialist walks the pages Preview cannot script, the container owner signs off item by item, and a second person reviews before anything is called done.

What you get

Proof of what changed, not just a promise it's clean

The final container is organized and documented so a new owner can understand it without relying on institutional memory.

  • A cleanup ledger showing before-and-after tag inventory sheets side by side

    Working document

    Full container inventory

    Every tag, trigger, and variable, with its purpose and status noted.

  • A cleanup ledger showing before-and-after tag inventory sheets side by side

    Change log

    Before-and-after cleanup log

    What we removed, paused, or fixed, and why, so the change is traceable later.

  • A cleanup ledger showing before-and-after tag inventory sheets side by side

    Access report

    Access review

    Who has access to the container and whether that access still makes sense.

We call it done when: every item is either kept with a documented reason or removed with a sign-off, and the before-and-after log lets someone reverse any single change.

Fit and readiness

A container three agencies touched is nobody's responsibility now

A container passed through three sets of hands rarely has one clear owner left. Sound familiar?

A good fit when

  • Multiple agencies, freelancers, or in-house teams have touched your container and nobody has the full picture.
  • You suspect duplicate tags are double-firing, but nobody has confirmed it or measured the impact.
  • A new agency or team member is about to join, but container access no longer reflects who still owns the tags and triggers.
  • Container access is available and past maintainers can be named, but nobody has matched those users to current responsibilities.

Better handled as other work when

  • You need a new container with a fresh folder, naming, and environment structure. That belongs in GTM Web Container Architecture.
  • The tags and triggers causing the problem live in a server-side container. That belongs in Server-Side GTM & Cloud Setup.

If one of these is closer to your situation, start here instead: All Google Tag Manager Consulting tasks

We call it done when: the full inventory is out and someone has confirmed the firing frequency GTM's own screens do not show.

People who build your measurement system

Zeo designs measurement systems that connect a business decision to governed collection and reporting you can check. The people shown here work on the part of that system this page covers.

Tools we use

Tools behind this work

  • Google Tag Manager

    the container itself, read through its own publish history to date every tag found

  • Google Tag Assistant

    the Preview-mode pass that shows what actually still fires, before anything gets deleted

  • Omnibug

    an independent log of every outbound tag request, so a tag GTM's own preview panel undercounts doesn't get missed

Next step

Find out what's actually running in your container

Give us access and we'll separate what is safe to remove from confirmed duplicates and anything that still needs a person's decision.
Plan a GTM cleanup

Before we start

Questions teams ask before booking

Will you delete tags without asking us first?

No. We confirm every uncertain tag with your team before making a change. Leaving one unused tag in place is safer than removing something a team still depends on.

What if the audit finds the container needs a full rebuild?

We'll say so directly. Cleanup has limits when the container never had a sound structure for naming, folders, or environments. In that case, GTM Web Container Architecture is the better next step.

How long has a tag been sitting there before you consider it dead?

Age alone does not make a tag obsolete. We check its firing frequency and confirm its purpose with your team, since an annual campaign tag may look inactive for eleven months and still be necessary.

What container access does the cleanup need?

We need user-level access to the GTM container and contact with the people who have maintained it, including agencies, freelancers, or previous in-house owners.