GTM Ultimate Stack
Read a GTM standards audit scorecard
What pass, fail and n/a mean, how severity orders the containers, what a finding tells you, and why the standards that fail most often matter more than any single finding.
The headline
The scorecard opens with one line: Conformance — 6 containers · 58/66 checks passed. A check is one standard against one container, so six containers and eleven standards make sixty-six checks.
Containers, worst first
Each container has a row with a coloured dot and its pass, fail and n/a counts. Containers with failures sort to the top. The dot shows the worst severity among its failures: red for an error, amber for a warning or info finding, green when everything passed.
A scorecard listing containers worst first, two with error findings, one with warnings and two that pass every standard.
Pass, fail and n/a
- pass: everything the standard applies to in that container conforms. A standard that forbids something passes when there is none of it.
- fail: at least one item doesn't conform. Each one is a finding.
- n/a: the container has nothing for the standard to check, such as the ads consent standard in a container with no ads tags. It isn't a pass, so don't read a column of n/a as good news.
A checklist of pass, fail and n/a, and the error, warning and info severities with their dot colours.
What a finding tells you
Open a container and every failing standard lists its findings: the item's name and the reason. Reasons are specific: consent not declared: analytics_storage (declares: ad_storage), measurementId is the literal "G-…", not a {{variable}}, name contains "copy of", found 2, expected exactly 1. Container-level standards report against the container itself, such as 4 open workspaces (GTM allows 3).
Passing standards are folded away, and you can open them to see what passed.
A findings table for one container listing three items, the standard each fails, the reason and the severity.
The standards that fail most often
Next to the containers, the scorecard lists the standards with the lowest pass rate across the run. One container failing a standard is a fix. Most containers failing it is a habit: a template everyone copies, a step missing from the build checklist. Fix the habit and the findings stop coming back.
A list of four standards with their pass rate across eight containers, the weakest first.
“No orphaned tags” is not Inventory's Orphaned
The built-in No orphaned tags standard flags a tag with no firing trigger attached. Inventory & Cleanup's Orphaned usage verdict means nothing references an item at all, and covers triggers and variables too. They answer different questions; Read the usage verdicts covers the other one.
Two panels contrasting the audit's no-firing-trigger check with Inventory & Cleanup's orphaned usage verdict.
Questions about the scorecard
Why does a standard show n/a everywhere?
None of the containers have anything it applies to. Check its Applies to settings, or switch it off.
Can I share the scorecard?
On Premium, export the results or email them. Every row carries the account, container, standard, category, severity, status and findings.
Why is a finding about something that isn't live?
The audit reads the Default Workspace, which can hold unpublished edits.
ODDVX for Windows
One standard, every container.
Start free on one GTM account with every built-in standard. Premium adds several accounts in one run, any number of custom standards, exports and scheduled audits.