container audit
GTM-W7N7Z6
34 tags, 7 custom scripts, 5 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 7 custom HTML tags carrying 4 KB of JavaScript. This runs on every page the container loads on.
- 5 third-party hosts 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.
Tags34
Custom scripts7
Third parties5
Delivered564 KB
Versions254
What we observed
A real browser loaded warentuin.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
googletagmanager.com — GoogleMeasurement sent to
sst.warentuin.nl — not GoogleMeasurement 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 ×3 — read from the measurement id, not the hostname
Consent
a consent banner was present and we accepted it. Measurement fired beforehand but carried no identifier —
analytics_storage was denied, which is Consent Mode working as designed rather than a gap. 3 hosts appeared only after consent was granted. Google recorded gcs=G100 (all denied).Third parties contacted
19 hosts — chimpstatic.com, fonts.googleapis.com, assets.spotlersearch.com, assets.spotlersearchanalytics.com, www.googletagmanager.com, www.kiyoh.com, cdn.cookie-script.com, ct.beslist.nl, and 11 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, select_content, gtm.scrollDepth, gtm.click, CookieScriptGoogleConsentUpdated, CookieScriptConsentUpdated[strict,targeting,performance,functionality], CookieScriptCategory-strict, CookieScriptCategory-targeting, CookieScriptCategory-performance, CookieScriptCategory-functionality
Where the data goes
Confirmed — a browser watched this site send measurement data to sst.warentuin.nl, not to Google. observed on warentuin.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.
reviewHardcoded http:// URL (1)
1 piece of custom code reference a plain http:// address.
WhyOn an https:// page the browser blocks or upgrades these. Blocked means the tag quietly stops working; upgraded only works if that host also serves https.
CheckCheck whether the hosts below still respond over https, and update the URLs.
Seenseen in 12.8% 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
infoUses browser storage (1)
1 piece of custom code read or write localStorage or sessionStorage.
WhyBrowser storage persists across visits and is not covered by cookie consent tooling, so it is easy to overlook when auditing what you keep on a visitor's device.
CheckConfirm nothing personal is being kept there, and that it is covered by your privacy notice.
Seenseen in 23.3% 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_PLWDP gallery injects code from x.cookie-script.com · runs page-level globals__cvt_309238_424 private injects code from dynamic.criteo.com__cvt_579DB gallery runs page-level globals__cvt_5RM3Q gallery injects code from connect.facebook.net, capi-automation.s3.us-east-2.amazonaws.com · runs page-level globals__cvt_P3FJ3 gallery injects code from ct.beslist.nl · runs page-level globals__cvt_W6NQ5 gallery injects code from ocean.kieskeurig.nl, ocean.kieskeurig.be, ocean.besteproduct.nl · runs page-level globals__cvt_WKPNZ gallery injects code from s.kk-resources.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-W7N7Z6 |
|---|---|
| Published version | 254 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:16:33 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-W7N7Z6 |
| Body checksum | a8a3104f3ae67b7ec03d0c3428b3c6027003625f5eb99b92494974532d4adbfbEvidence 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 »