container audit
GTM-KVF8X8QH
59 tags, 4 custom scripts, 6 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 4 custom HTML tags carrying 1 KB of JavaScript. This runs on every page the container loads on.
- 6 third-party hosts reachable from its tags.
Tags59
Custom scripts4
Third parties6
Delivered518 KB
Versions27
What we observed
A real browser loaded phoenixchildrens.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
phoenixchildrens.org — the site's own host, at /modules/contrib/google_tag/js/gtm.js rather than the default path, and googletagmanager.comMeasurement sent to
google-analytics.com — GoogleThe container is self-hosted; the measurement still goes to Google. The first-party path that a tagging server provides is not being used for the data itself.
Consent
OneTrust answered its own API. Measurement fired beforehand but carried no identifier —
analytics_storage was denied, which is Consent Mode working as designed rather than a gap. no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision. Google recorded gcs=G100 (all denied).Third parties contacted
25 hosts — static.cdn-website.com, irp.cdn-website.com, d32hwlnfiv2gyn.cloudfront.net, rtc.multiscreensite.com, phoenixchildrens.org, fonts.googleapis.com, cdn.cookielaw.org, script.crazyegg.com, and 17 more
dataLayer events seen
OneTrustLoaded, OptanonLoaded, gtm.js, gtm.dom, gtm.load, gtm.click
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on phoenixchildrens.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.
infoOne variable that a great deal depends on (41)
"gtm.element" is read by 41 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
infoConsent configuration detected (1)
The container declares one or more consent signals.
WhyConsent handling is present in the container. This describes what the artifact declares; what actually happened on the page is measured separately, above.
CheckConfirm these settings match the consent policy you intend to enforce, and compare them with the before-and-after observation.
Seenseen in 44.6% 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 »
www.google-analytics.com ×51insight.adsrvr.org ×2www.googleadservices.com ×2fls.doubleclick.net ×1js.adsrvr.org ×1tag.simpli.fi ×1
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-KVF8X8QH |
|---|---|
| Published version | 27 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:41:14 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-KVF8X8QH |
| Body checksum | 3e2b3c70a63280d3ad6456163c7c76fe9840cf6e33babd3bc0c6efd784d63d02Evidence 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 »