Google Tag Manager

GTM Audit: A Google Tag Manager Checklist for an Inherited Container

Audit a Google Tag Manager container you just inherited: back it up, map every tag, find duplicates and orphans, check consent and hard-coded IDs, and stop tags firing on test and preview hosts.

Cover: Audit the container you inherited. a GTM container opened like a toolbox, with tags sorted into keep, fix and remove piles and a hostname filter blocking a staging site.

You take over an account and the container has 80 tags, three people’s naming styles and a Custom HTML tag called "test2". The audit is how you find out what is actually reaching the ad platforms before you change a budget based on it.

A story from our own site

When I built the Whathead site, our production GA4 property started showing visits from 127.0.0.1. Local development, the prerender step, Lighthouse runs and every preview deploy were loading Google Tag Manager and reporting as if they were real visitors. The fix was to load GTM only on whathead.com hostnames.

In a client container you usually can’t change how the site loads GTM, so do the same thing inside the container. Two patterns work:

  • A hostname lookup. A Lookup Table variable on {{Page Hostname}} that returns the real pixel or measurement ID on production hostnames and nothing elsewhere. Tags read the ID from it, so staging sends nothing.
  • A blocking trigger. A trigger that matches when Page Hostname is not a production host, added to tags as an exception. Google’s help calls these trigger exceptions, also known as blocking triggers.

GA4 can filter the rest; see filtering test and internal traffic in GA4.

How to run the audit

How to

Audit an inherited Google Tag Manager container

The order that keeps you from breaking anything while you look.

  1. 01

    Back up

    Export the live version as a JSON file and note its version number. That is your rollback point.

  2. 02

    Check what loads on the page

    With Tag Assistant on the real site, list every GTM container and every pixel loaded outside GTM. Two containers, or a vendor’s container shared across several sites, change the whole picture.

  3. 03

    Inventory the tags

    One row per tag: platform, type, ID it sends to, trigger, consent setting, last edited. Group by platform.

  4. 04

    Walk the conversion path in Preview

    Note which tags fire on each step, how many times, and with what values.

  5. 05

    Mark each finding

    Keep, fix or remove, with an owner. Nothing gets removed without knowing who added it.

  6. 06

    Fix in a new workspace

    Small, related changes per workspace, tested in Preview and published with a note.

The GTM audit checklist

Inventory and duplicates

What is on the page

  • Only the containers you expect load on the site; any other container has a known owner.
  • No pixel is loaded both in GTM and hard-coded in the site.
  • Each platform has one base pixel per site, unless two are intentional and documented.
  • Only one Google tag sends page views to each GA4 property.
  • Platform-side codeless or automatic events (for example in Meta Events Manager) reviewed.
Firing

What fires and when

  • No tags without a firing trigger, and no paused tags left without a reason.
  • No triggers or variables referenced by tags that no longer exist.
  • Conversion tags fire on success events, not clicks or bare thank-you page views.
  • No Custom Event trigger matches every event with a regex such as .*.
  • Single-page apps: page views counted once per navigation.
Hosts and data

Where it fires and what it sends

  • Nothing sends to production IDs from staging, preview, local or test hosts.
  • No personal data in URLs: an email or phone in a query string reaches every pixel’s page URL.
  • Values are numbers and currency codes match the real currency.
  • Check how GTM itself loads: a container delayed until the first click or a timeout misses visitors who leave fast.
Consent

Who waits for the banner

  • Consent overview enabled; no tag left in Consent Not Configured by accident.
  • The banner template fires on Consent Initialization - All Pages.
  • Non-Google pixels require additional consent where your policy says so.
IDs, naming and folders

Can the next person read it

  • Pixel, measurement and conversion IDs live in Constant or Lookup Table variables, not typed into tags.
  • One naming pattern, such as Platform - Event - Type, and one folder per platform.
  • Unused variables, triggers and templates removed.
Access and publishing

Who can change it

  • Users reviewed: former staff and old agencies removed; Publish limited to the people accountable.
  • Workspaces: no stale ones blocking the free limit of three.
  • Version history has names and descriptions from now on.

Consent fixes are covered in consent mode v2 in GTM, and the publishing routine in GTM versions and workspaces. For naming, borrow the logic of ad naming conventions.

Where this goes wrong

  • Deleting what looks unused. A tag with an odd name may feed a report someone relies on. Pause first, publish, and delete a few weeks later.
  • Auditing only GTM. Hard-coded pixels and codeless platform events don’t show up in the container but do show up in your numbers.
  • Shared containers. A vendor container hard-coded into several sites can fire one brand’s pixel on another’s site. Check every container’s scope.
  • One giant cleanup publish. If numbers move, you can’t tell which change did it. Publish in small, named versions.
  • Trusting trigger names. "CE - purchase" might not match purchase at all. Open the trigger.

Do it faster with Whathead

Whathead’s Google Tag Manager MCP includes a read-only container audit that reports duplicate names, tags with no firing trigger, references to missing triggers or variables, paused tags and workspace merge conflicts. For the judgment calls (duplicate pixels, hard-coded IDs, consent gaps, host filters), Claude reads the full tag list and explains it. Whathead is our product.

  • “Audit GTM-XXXXXXX read-only. Then list every tag by platform with the ID it sends to, its trigger and its consent setting. Flag duplicate pixels, hard-coded IDs and tags with no hostname protection.”
  • “Which tags fire on All Pages, and are any two of them loading the same pixel?”

Nothing changes from those prompts. To guarantee it, connect the read-only endpoint, https://www.whathead.com/mcp/read, which refuses GTM writes. When you do fix things, the changes go into a workspace; there is no dry run for GTM writes, so Preview and the publish decision stay with you.

GTM audit: common questions

How often should I audit a GTM container?

When you inherit it, before a major launch, and at least once or twice a year. Small checks after every publish catch most drift.

What does a GTM audit usually find?

Duplicate pixels, tags that never fire, conversion tags on click triggers, hard-coded IDs, missing consent settings and tags firing on staging hosts.

Can I audit Google Tag Manager myself?

Yes, with Read access and Tag Assistant. Fixes need Edit access, and publishing needs Publish rights.

Does a GTM audit include consent?

It should. Turn on the consent overview and check every non-Google pixel’s Additional Consent Checks setting.

How do I find duplicate tags in GTM?

List tags by the ID they send to, then compare with Tag Assistant on the live site to catch pixels loaded outside GTM.

Sources

Written by Ahmed Shahin, founder of Whathead. Last reviewed 19 November 2026.