container audit
GTM-KMPGBHW
71 tags, 1 custom scripts, 3 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 1 custom HTML tag carrying 4 KB of JavaScript. This runs on every page the container loads on.
- 3 third-party hosts reachable from its tags.
Tags71
Custom scripts1
Third parties3
Delivered576 KB
Versions56
What we observed
A real browser loaded janushenderson.com 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
google-analytics.com — GoogleConsent
OneTrust answered its own API. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 0 fired afterwards. That is the outcome consent is meant to produce. Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — cdn.cookielaw.org, janushenderson.bynder.com, geolocation.onetrust.com, siteimproveanalytics.com, www.google.com, challenges.cloudflare.com, cdn.userway.org, www.googletagmanager.com, and 17 more
dataLayer events seen
OneTrustLoaded, OptanonLoaded, gtm.js, gtm.dom, read-times-calculated, gtm.load, gtm.scrollDepth
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on janushenderson.com 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.
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
infoOne variable that a great deal depends on (43)
"gtm.triggers" is read by 43 tags and triggers — more than anything else in this container.
WhyGTM shows you where a variable is defined, never how much depends on it. Editing this one touches a large share of the container at once, and whatever breaks will surface somewhere that looks unrelated to the change.
CheckBefore changing it, check what reads it. If it feeds both measurement and consent or routing logic, split those uses apart first.
Seenseen in 10.1% 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 »
Detected 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-KMPGBHW |
|---|---|
| Published version | 56 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:39:18 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-KMPGBHW |
| Body checksum | 45f6a5a32c837333f5e86a8c73e26103dff67c96d2493362e1aafe64a9072553Evidence 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 »