container audit
GTM-MC3WMB9
80 tags, 10 custom scripts, 3 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 10 custom HTML tags carrying 7 KB of JavaScript. This runs on every page the container loads on.
- 3 third-party hosts reachable from its tags.
duplicate-ga4-configis uncommon — under 5% of the containers we have measured have it. That is context rather than a verdict: a server container is rarer still and is a sign of a mature setup. What it means is in the finding itself.
Tags80
Custom scripts10
Third parties3
Delivered537 KB
Versions57
What we observed
A real browser loaded shadestation.co.uk 2 months ago and recorded every request it made. This is what happened, as distinct from what the container is configured to do. It is one page load — anything that fires only deeper in the site did not fire here.
Container loaded from
googletagmanager.com — GoogleMeasurement sent to
www.shadestation.co.uk — not Google, at /metrics/ag/g/cMeasurement is first-party; the container still loads from Google. These are separate decisions, and this is the more common of the two.
Forwarded to
GA4 ×5 — read from the measurement id, not the hostname
Consent
a consent platform is present, but our browser could not complete the accept step — so the before-and-after comparison did not run here. Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — static.cloudflareinsights.com, static.zdassets.com, www.googleadservices.com, app.aliapopups.com, ekr.zdassets.com, widget.trustpilot.com, static.criteo.net, static.klaviyo.com, and 17 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load
Where the data goes
Confirmed — a browser watched this site send measurement data to www.shadestation.co.uk, not to Google. observed on shadestation.co.uk More info »
Findings
Ordered by consequence. review has a concrete cost when it bites; info is real but depends on your setup. Seen is how common it is across the containers we have measured — reported separately on purpose, because common and harmless are different claims.
reviewSame GA4 property configured more than once (1)
G-9Z7QGHFP49 is configured by 2 separate tags.
WhyEach config tag initialises the property independently, so a single page view can be counted once per tag. Sessions, users and conversion rates all inherit the error.
CheckIf more than one of these fires on the same page you are double-counting. Compare against a known-good day, or check for a step change in traffic when the second tag was added.
Seenseen in 4.8% of 46,522 containers measured
reviewNo consent signal in the container (1)
Nothing in this container sets, reads, or gates on a consent state.
WhyThe container itself neither sets a Consent Mode default, holds any tag back for consent, nor references a known consent platform. Either enforcement lives entirely outside GTM — where it cannot be audited from here — or tags fire regardless of what a visitor chose.
CheckIf a consent platform blocks scripts before GTM loads, this is fine — confirm that is actually the case. If not, tags are firing on a choice nobody recorded.
Seenseen in 52.1% of 46,522 containers measured
infoVendor IDs written into custom code (1)
1 vendor ID is pasted directly into custom HTML rather than held in a variable or template.
WhyChanging a property, pixel or account then means editing every tag that mentions it, and any one that gets missed keeps sending to the old destination indefinitely.
CheckFine if the ID never changes. If you have ever migrated a property, check that none of these still point at the old one.
Seenseen in 31.4% of 46,522 containers measured
Third parties it can reach
Each host is a party that can execute code or receive data in a visitor's browser. Follow one to see who else loads it. More info »
What the custom templates can do
Custom templates are third-party code shipped inside the container. Injecting scripts and running page globals is ordinary for them — most tag templates need it to work — so this is an inventory, not a warning. It lists the capability each template declares so you can match it against templates you meant to install.
__cvt_PBGZL gallery injects code from www.redditstatic.com · runs page-level globalsDetected on
Sites observed loading this container. A container used across many hosts is a shared template; one on a single host is a bespoke build. Follow a site to see every container it loads.
What this audit describes
Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.
| Container | GTM-MC3WMB9 |
|---|---|
| Published version | 57 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:45:14 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-MC3WMB9 |
| Body checksum | a0b78a5ca2b5f91b34c258fd60ff0300c1eaa6ea39e84db4741b1761c59c113dEvidence of the exact bytes we read, not an identity: Google varies the response per request, so re-fetching an unchanged container yields a different checksum. Compare the published version instead. |
Re-audit
This reading is from 2 months ago. A container can be republished at any time, and nothing here updates on its own — a fresh read is the only way to know whether it still says this. Running it again replaces this page in place, so the link keeps working.
Put this container under version control. Tagora exports it to a repository you own, so every change arrives as a pull request. How it works »