RevOps

Score your GTM container health across the 8 things a real audit checks.

Use the calculator Or book a diagnosis call
Category
RevOps
Signup
None
Your data
Stays in your browser

How do you score the health of a Google Tag Manager container?

Check eight practices and weight them: tag inventory, no duplicates, specific triggers, Consent Mode and a documented data layer (15 points each), Preview before publishing and version notes (10 each), and monthly reconciliation (5). Yes scores full points, partly half. 85+ is clean, 60 to 84 needs a cleanup, under 60 means data is likely unreliable.

Container health checklist
Weight 15
Weight 15
Weight 15
Weight 15
Weight 15
Weight 10
Weight 10
Weight 5
Container health score
13/100
Data is likely unreliable
Highest-priority fix
Every tag has a documented purpose and owner
Lowest-scoring dimension

Multiple core checks failed, starting with "every tag has a documented purpose and owner." At this state, treat every number your ad platforms and GA4 report with real suspicion until the audit below is run in full.

This is a self-assessment, not the audit itself, read the full checklist below for how to verify each of these eight items in Preview mode and GA4 DebugView.

About this calculator

A GTM container can look fine and still be reporting numbers 20-40% off from reality, duplicate tags, unscoped triggers, and missing consent handling rarely throw errors, they just quietly corrupt the data everyone downstream trusts. This scorecard is a weighted self-assessment across the eight checks that actually predict clean data, based on the technical audit checklist in the Google Tag Manager Audit guide.

How to use it

  1. Answer each of the eight checklist items honestly: Yes/confirmed, Partial/not sure, or No.
  2. "Not sure" is a valid answer, and should be treated as a gap, if you can't confirm it, you can't rely on it.
  3. Read the weighted container health score out of 100, and the single highest-priority fix, the lowest-scoring dimension.
  4. Use the full audit guide below to actually verify each item in Preview mode and GA4 DebugView, this scorecard tells you where to look, not how to fix it.

Methodology

Each of the eight checklist items has a weight (15, 15, 15, 15, 15, 10, 10, 5) reflecting how much it typically affects data reliability, tag inventory, duplicate detection, trigger specificity, and Consent Mode carry the highest weight; reconciliation carries the lowest since it's a symptom-detector rather than a root cause.

Each answer scores 1 point (Yes), 0.5 points (Partial), or 0 points (No), multiplied by that item's weight. The container health score is the sum of weighted points divided by total possible weight, as a percentage.

Scores band into three tiers: 85+ is a clean container, 60-84 needs a targeted cleanup, below 60 means data is likely unreliable across the board. These bands are calibrated conservatively, a container with three or four unchecked items typically compounds into meaningfully distorted reporting even if no single item looks catastrophic alone.

This is a self-assessment based on your own honest answers, it can't verify your container directly. Treat a high score as a reason to spot-check rather than a guarantee, and re-run it after any agency handoff, site rebuild, or CRM migration, the three events most likely to quietly break a previously clean container.

Weighted container health score

Score = Σ (Weight × Answer) ÷ 100 × 100
(Answer: Yes = 1, Partly = 0.5, No = 0)
Weights: inventory 15, duplicates 15, triggers 15, Consent Mode 15, data layer 15, Preview 10, version notes 10, reconciliation 5
Band: 85+ clean, 60 to 84 targeted cleanup, under 60 unreliable
Inventory
Every tag has a written purpose and an owner.
Duplicates
No two tags send the same event to the same tool.
Triggers
Tags fire only on the pages and actions they should, not on all pages by default.
Consent Mode
Consent Mode v2 is set up and its behaviour checked.
Data layer
Events and variables pushed by the site are documented and versioned.

This is a self-assessment; it cannot inspect the container. Be strict with "partly". Reconciliation carries the lowest weight because it detects problems rather than preventing them, but it is the check that tells you whether the other seven are working.

Worked example: the default answers

A company inherits a container from a former agency. There is no tag list, duplicates are likely, some triggers are specific, Consent Mode is not set up, the data layer is undocumented, Preview is used sometimes, versions have no notes and numbers are never reconciled.

  1. Triggers partly = 15 × 0.5 = 7.5.
  2. Preview partly = 10 × 0.5 = 5.
  3. All other items no = 0.
  4. Score = 7.5 + 5 = 12.5 out of 100, in the "data is likely unreliable" band.
  5. Fixing inventory, duplicates and Consent Mode alone adds 45 points, reaching 57.5.

At this score, reports built on the container should not drive budget decisions until it is cleaned up. Start with an inventory, because every other fix depends on knowing what each tag does. The full method is in the Google Tag Manager audit guide, and the GA4 audit covers the reporting side.

What does a clean container look like?

A clean container is one a new person could understand in an hour:

  • Tags named consistently, each with an owner and purpose.
  • Triggers tied to specific events or pages.
  • Consent handled through Google's Consent Mode, with behaviour checked in Preview.
  • Every published version with a short note of what changed and why.
  • A monthly check that GA4, ad platforms and the CRM agree within an expected margin.

Re-run the scorecard after any agency change, site rebuild or CRM migration.

Tag management in India vs the US and Europe

India

India's Digital Personal Data Protection Act, 2023 sets rules on consent for personal data, so consent handling is becoming a compliance question in India as well as a measurement one. Many Indian sites also run several ad pixels (Meta, Google, LinkedIn, affiliates) added by different agencies over time, which makes duplicates and orphaned tags common.

United States

In the US, state privacy laws vary, and sites with European visitors need consent handling that meets EU rules. Consent Mode lets Google tags adjust behaviour to the visitor's choice. Server-side tagging is increasingly used to control what data leaves the site; see Google Tag Manager services.

Common GTM container mistakes

  • Publishing changes without Preview, then debugging live.
  • Leaving old agency tags running because nobody knows what they do.
  • Firing conversion tags on all pages, which inflates conversions.
  • Setting up Consent Mode without checking what tags do when consent is refused.
  • Never comparing GA4, ad platform and CRM numbers.

Sources

  1. Consent mode overview, Google for Developers. Accessed 2026-10-19.

Go deeper

FAQ

What's the single most common cause of a low score?

Unscoped triggers, tags firing on "All Pages" that should be scoped to specific events or conditions, combined with duplicate tags tracking the same event through different mechanisms. Together these two issues account for most of the inflated or double-counted conversion numbers we see in container audits.

Why does Consent Mode carry so much weight?

Consent Mode v2 directly affects whether Google Ads and GA4 can model conversions for users who decline cookies. Getting it wrong, or not implementing it at all, silently suppresses or corrupts conversion data for a meaningful share of EU traffic, and increasingly matters outside the EU as more regions adopt similar consent requirements.

How often should this scorecard be re-run?

At minimum quarterly, and always after any of the three high-risk events: an agency or freelancer handoff, a site rebuild or CMS migration, or a CRM/marketing-automation platform migration. Each of these commonly introduces duplicate tags or breaks data layer variables without anyone noticing immediately.

My score is high but my GA4 and ad platform numbers still don't match. Why?

A high score on this checklist reduces the odds of the eight most common causes, but reconciliation gaps can also stem from attribution model differences between platforms, sampling, or timezone mismatches, issues outside what a container-health checklist alone can catch.

This only covers my tracking setup, what about the rest of my revenue system?

A clean container is one piece of a larger picture, RevOps, paid media efficiency, funnel conversion, unit economics, and GTM strategy all matter independently. The Revenue Systems Health Score runs a 12-question version of that broader audit and tells you which of those five areas to look at first.

How often should I audit my GTM container?

A light review monthly and a full audit at least once a year, plus after any site rebuild, agency change or CRM migration.

What is a data layer?

A data layer is a structured object on the site that passes information, such as order value or form type, to Tag Manager so tags can use it reliably.

Why do GA4 and ad platform conversions differ?

They use different attribution rules, counting windows and consent handling. Some difference is normal; a large or changing gap points to a tracking problem.

Numbers looking off?

If the model says one thing and the pipeline says another, that gap is usually where the revenue is. A 30-minute call finds it.

It starts with a 30-minute call. Pick a time below.

Prefer email?