container audit
GTM-WZTZJBV
51 tags, 2 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 2 custom HTML tags carrying 1 KB of JavaScript. This runs on every page the container loads on.
- 1 third-party host reachable from its tags.
- Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
Tags51
Custom scripts2
Third parties1
Delivered443 KB
Versions144
What we observed
A real browser loaded newsbit.nl a month 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
not observed loading
Measurement sent to
google-analytics.com — GoogleConsent
Cookiebot answered its own API. 1 host appeared only after consent was granted.
Third parties contacted
11 hosts — rum.corewebvitals.io, cdn.onesignal.com, pagead2.googlesyndication.com, consent.cookiebot.eu, api.taggrs.io, v1.widget.futy.io, api.onesignal.com, consentcdn.cookiebot.eu, and 3 more
dataLayer events seen
gtm.js, gtm.dom, gtm.elementVisibility, gtm.load, gtm.click, cookie_consent_preferences, cookie_consent_statistics, cookie_consent_marketing
Where the data goes
Nothing fired — we loaded the page and no tag library or measurement request ran, which usually means a consent banner held everything back. The container below still describes what would run once it does. observed on newsbit.nl 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.
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
infoOne variable that a great deal depends on (41)
"gtm.triggers" 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 (3)
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
infoLoads JavaScript from another host (1)
1 piece of custom code fetch and run JavaScript from another host.
WhyWhatever that host serves executes with full access to the page — it can read the DOM, cookies and form fields. The code is not in this container, so it can change at any time without any change here.
CheckConfirm you recognise every host below and that someone owns the relationship. A host you cannot name is the one to chase.
Seenseen in 54.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_30012331_79 private injects code from x.cookiebot.com, x.cookiebot.eu__cvt_5RM3Q gallery injects code from connect.facebook.net · 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-WZTZJBV |
|---|---|
| Published version | 144 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:23:22 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-WZTZJBV |
| Body checksum | e65d2b79197bd2b239c7d1baa04b796db93038dc50ef09ef1aba8b9e4c987c0bEvidence 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 a month 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 »