How do I audit and repair a GTM container?

Begin with a written inventory before you touch a single tag, because you cannot fix what you have not catalogued. Open the container and list every tag, every trigger, and every variable, noting what each tag is (GA4 config, GA4 event, Google Ads conversion, Floodlight, a third-party pixel, a custom HTML snippet) and what fires it. In a neglected container this is where the rot becomes visible: two GA4 configuration tags, a Google Ads conversion tag pointed at a thank-you page that was renamed last year, three custom HTML tags from vendors you no longer use, and a tangle of triggers nobody can explain.

GTM gives you a few shortcuts for this. The Folders view and the built-in search help, but the fastest way to see relationships is to export the container as a JSON file (Admin → Export Container) and read it, or open each tag and check its firing triggers and the variables it references. Pay special attention to Custom HTML tags — they are the highest-risk items in any container because they can load arbitrary scripts, and old marketing pixels accumulate there.

As you inventory, tag each item with a verdict: keep, fix, or remove. Anything you cannot identify or justify is a candidate for removal — but do not delete yet. The goal of this pass is a complete map: what is in the container, what each piece is supposed to do, and which items are already obviously broken or redundant. That map drives every decision in the passes that follow, and it is the artifact you will hand to anyone who needs to understand the setup later.

An inventory tells you what should happen; Preview mode tells you what does. Enter Preview (the button in the top-right of the container) and connect it to your live site through Tag Assistant. Then behave like a real user: load the homepage, navigate to key pages, submit a form, click a phone number, add a product to cart, complete a test purchase. For each action, the debug panel shows precisely which tags fired, which did not, the trigger that caused each fire, and the order — this is the single most valuable view in a GTM audit.

Look for four failure patterns. First, duplicate fires: the same GA4 event or Ads conversion firing twice on one action almost always means a duplicate tag or a trigger that is too broad. Second, missing fires: a conversion tag that never appears when you complete the conversion means a broken trigger — usually a URL, form ID, or dataLayer event that changed. Third, wrong-page fires: a purchase conversion firing on every page rather than only the confirmation page, which inflates and corrupts your conversion data. Fourth, order and consent problems: tags firing before consent is granted, or analytics firing before its configuration tag.

Cross-check against the dataLayer. Open the browser console, type dataLayer, and confirm the events and variables your triggers depend on are actually being pushed with the values you expect. Many "broken trigger" problems are really a dataLayer that the developers changed during a redesign. Test on mobile too, because layouts, form IDs, and script timing differ. By the end of this pass you should have a confirmed, evidence-based list of what is genuinely broken — not what you suspect.

Preview proves a tag fired in your browser; reconciliation proves the data landed correctly in the platforms that matter. Open GA4 DebugView while Preview mode is active and confirm your events arrive with the right names and parameters — GA4 is strict about event and parameter naming, and a tag that fires perfectly can still send a misnamed event that GA4 quietly ignores. Then check Google Ads under Goals → Conversions: is each conversion action recording recently, or flagged "Inactive" or "No recent conversions"? A tag that fires in Preview but shows inactive in Ads usually points to a wrong conversion ID or label.

This pass is where double-counting surfaces, and it is one of the most damaging defects you can carry. If a developer hard-coded a gtag.js or GA4 snippet directly into the site and GTM also deploys the same GA4 tag, every pageview and conversion counts twice. The numbers look healthy — even flattering — but they are corrupting Smart Bidding, inflating your reported conversion rate, and misallocating budget toward whatever appears to convert. Watch the network tab for duplicate requests to the same endpoint, and search the page source for hard-coded gtag, analytics.js, or conversion snippets that should live only in GTM.

Also reconcile what GTM cannot see. Phone calls dialed from a printed number rather than a tracked call asset, offline sales, and in-store visits never appear in any tag — so a container can be flawless and still under-report real results. The point of this pass is to make the platforms agree with reality: one source of truth per measurement, named consistently, recording where and only where it should.

Make every change inside the audit-and-version safety net GTM already provides, so a mistake is reversible in seconds rather than a fresh emergency. Work in a Workspace (or create a dedicated one for the repair) so your edits are staged, not live. Fix in priority order: remove duplicate tags and consolidate to a single GA4 configuration; repair broken triggers by updating them to match the current dataLayer, form IDs, or URLs; narrow over-broad triggers so conversion tags fire only on the correct event; and delete the orphaned tags, triggers, and variables you flagged in the inventory — but only after confirming nothing else references them.

Address consent properly rather than as an afterthought. If you serve the EEA, Consent Mode v2 is required for Google advertising features: set a consent default that withholds storage until the user chooses, and gate advertising and analytics tags behind the appropriate consent state using GTM's built-in consent settings. Tags firing before consent are both a measurement problem and a compliance one.

Before publishing, re-run Preview against the same real-user journeys from the second pass and confirm each fix behaves — no duplicates, every conversion firing once on the right page, consent respected. Then publish, and write a real version name and description ("Removed duplicate GA4 config, fixed purchase trigger, added consent defaults") so the version history is a usable changelog. Because every publish is a numbered, one-click-revertible version, you can ship the repair confidently: if anything regresses, roll back instantly and diagnose without pressure. Set a reminder to re-audit after any future site redesign, since that is when containers break.