container audit
GTM-HZ8Q5
131 tags, 4 custom scripts, 7 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 4 custom HTML tags carrying 2 KB of JavaScript. This runs on every page the container loads on.
- 7 third-party hosts reachable from its tags — more than 70% of the 46,522 containers we have measured.
Tags131
Custom scripts4
Third parties7
Delivered625 KB
Versions150
What we observed
A real browser loaded sdccu.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. 2 measurement hits left the page before it was granted, carrying a client id (whether that is permitted depends on jurisdiction, and this was not a European visit). no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision. 5 advertising hosts were contacted before anything was granted.
Third parties contacted
23 hosts — use.typekit.net, cdn.cookielaw.org, www.google.com, www.googletagmanager.com, www.google-analytics.com, dev.visualwebsiteoptimizer.com, geolocation.onetrust.com, static.ads-twitter.com, and 15 more
dataLayer events seen
gtm.js, OneTrustLoaded, OptanonLoaded, gtm.dom, gtm.load
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on sdccu.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.
reviewUniversal Analytics tags still shipped (34)
34 Universal Analytics tags are still in the container.
WhyUniversal Analytics stopped processing data in July 2023. These tags still download and execute on every matching page, and send to an endpoint that discards them.
CheckNothing is being collected from these. Confirm the equivalent GA4 tag exists, then delete them.
Seenseen in 23.2% of 46,522 containers measured
reviewWrites cookies directly (1)
1 piece of custom code set cookies in code.
WhyCookies set this way bypass GTM's consent settings, because the consent checks live in the tag templates rather than in raw JavaScript.
CheckIf any of these cookies are used for analytics or advertising, confirm they are still gated on a consent decision.
Seenseen in 21.2% of 46,522 containers measured
infoConsent configuration detected (2)
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 ×42googleads.g.doubleclick.net ×7www.googleadservices.com ×6products.gobankingrates.com ×2clickserv.sitescout.com ×1fls.doubleclick.net ×1pixel-sync.sitescout.com ×1
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_KD25J gallery injects code from ads.nextdoor.com, ads.nextdoor-test.com · runs page-level globals__cvt_174734_201 private injects code from snap.licdn.com__cvt_174734_270 private injects code from static.ads-twitter.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-HZ8Q5 |
|---|---|
| Published version | 150 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-13 08:25:20 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-HZ8Q5 |
| Body checksum | 6d5dff97f35d42ecb7efea44952260bd8fcaac944defd723c7690a4e719668b0Evidence 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 »