container audit
GTM-W3QGZ3PD
58 tags, 0 custom scripts, 0 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
Tags58
Custom scripts0
Third parties0
Delivered476 KB
Versions13
What we observed
A real browser loaded zeb.be 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
data.zeb.be — the site's own host, 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
a consent platform is present, but our browser could not complete the accept step — so the before-and-after comparison did not run here. 3 hosts appeared only after consent was granted. Google recorded
gcs=G100 (all denied).Third parties contacted
25 hosts — procdn.swymrelay.com, cdn.shopify.com, shop.app, onsite.optimonk.com, api.eu1.exponea.com, www.clarity.ms, cdn.brcdn.com, otlp-http-production.shopifysvc.com, and 17 more
dataLayer events seen
gtm.js, gtm.dom, page_view_stape, gtm.load, cookiehub_ready, cookiehub_necessary, cookiehub_consent_update, cookiehub_dialog
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on zeb.be 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
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 »
No third-party hosts were found in this container's tags.
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-W3QGZ3PD |
|---|---|
| Published version | 13 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:15:20 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-W3QGZ3PD |
| Body checksum | cbe083685838a44d4004d8072835fa838c42f4f033dabee732d78c2b3aceda61Evidence 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 »