How to Audit a GTM Container You Inherited (And What to Look For)

You just took over a GTM container. Maybe you joined a new company. Maybe the last agency left. Maybe the person who set it up quit two years ago and nobody’s touched it since.

You open it and see 47 tags, 23 triggers, 18 variables, and no documentation. Some tags are paused. Some have names like “Copy of GA - Event - Click - v2 FINAL.” Nobody can tell you what half of them do.

Here’s how to audit it systematically.

Step 1: Take inventory

Before changing anything, document what exists.

Tags: Export the full tag list. For each tag, note:

• Name
• Type (GA4 Event, Google Ads Conversion, Custom HTML, etc.)
• Status (active, paused)
• Firing trigger(s)
• Last edited date and who edited it

The quick win: Sort by “last edited.” Tags that haven’t been touched in over a year are candidates for review or removal.

Step 2: Identify the dead weight

Open the container in GTM and look for:

• Paused tags — why were they paused? If nobody knows, they’re candidates for deletion.
• Tags with no trigger — orphaned tags that never fire. Remove them.
• Duplicate tags — “GA4 - Page View” and “GA - Pageview - All Pages” doing the same thing. Common after agency transitions.
• Custom HTML tags with inline scripts — these are the highest-risk tags. They can contain anything: analytics, chat widgets, heatmap tools, or code that stopped working months ago.

Step 3: Check what actually fires

Open GTM Preview mode and navigate through your key pages:

1. Homepage — what fires on load?
2. Product/service page — are product view events present?
3. Contact/form page — does form submission trigger a tag?
4. Checkout (if applicable) — is the full e-commerce flow tracked?
5. Order confirmation — does the purchase event fire with a transaction ID?

For each page, compare what fires to what should fire. This is where you find the gaps.

Step 4: Validate the data layer

In Preview mode, look at the dataLayer panel for each page. Check:

• Are events named consistently? Mix of camelCase and snake_case is a red flag.
• Do product events have complete data? item_name, item_id, price should all be populated — not undefined.
• Are there unexpected pushes? Third-party scripts often push to the dataLayer without anyone realizing it.

Step 5: Check consent mode

If the site has a cookie consent banner:

1. Is GTM Consent Mode implemented? (Look for consent events in the dataLayer)
2. Do tags check consent before firing? (Open each tag → Advanced → Consent Settings)
3. Does declining consent actually stop tags from firing?

If the answers are no, no, and no — the consent banner is decorative and the site has compliance risk.

Step 6: Check who has access

Go to Admin → User Management. Look at who has Publish access. Common findings:

• Former employees still have access
• Former agency accounts still have Publish rights
• “Everyone” has Publish access because nobody set up permissions

Lock it down. Publish access should be 1–2 people with a review process.

Step 7: Prioritize fixes

After the audit, sort your findings by business impact:

1. Critical — things actively costing money (duplicate conversion tags, broken purchase tracking)
2. High — compliance risks (consent mode, PII in tags)
3. Medium — data quality issues (inconsistent naming, missing events)
4. Low — container hygiene (dead tags, messy naming, missing documentation)

Fix critical issues immediately. Schedule high and medium for the next sprint. Low can wait but shouldn’t be forgotten.

The documentation deliverable

After the audit, create a simple document listing:

• Every active tag, what it does, and why it exists
• Every trigger and what pages/events it covers
• Known issues found and their priority
• Recommendations for fixes with effort estimates

This document is the thing the previous owner never created. It’s the most valuable output of the audit because it prevents the next person from going through the same discovery process.

---

This is the exact process we follow in a GTM audit. If you don’t have time to do it yourself, we’ll do it for you and hand you the documentation.

← All posts