container audit
GTM-W327BHDG
36 tags, 6 custom scripts, 0 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 6 custom HTML tags carrying 3 KB of JavaScript. This runs on every page the container loads on.
- Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
Tags36
Custom scripts6
Third parties0
Delivered546 KB
Versions45
What we observed
A real browser loaded billetto.dk 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
st-b2c.billetto.dk — the site's own host, and googletagmanager.comMeasurement sent to
st-b2c.billetto.dk — not GoogleMeasurement runs through the site's own infrastructure. Part of the tag library still comes from Google, which is normal — the two are loaded separately.
Forwarded to
GA4 ×7 — 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. 4 hosts appeared only after consent was granted. Google recorded gcs=G100 (all denied).Third parties contacted
25 hosts — bun2.billetto.com, billetto.imgix.net, marketing.billettoassets.com, billetto.co.uk, cdn.clerk.io, www.googletagmanager.com, sessions.bugsnag.com, fonts.googleapis.com, and 17 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, gtm.click, cookie_cat_necessary, cookie_cat_functional, cookie_cat_statistic, cookie_cat_marketing, cookie_cat_unclassified
Where the data goes
Confirmed — a browser watched this site send measurement data to st-b2c.billetto.dk, not to Google. observed on billetto.dk 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.
infoUses browser storage (2)
2 pieces 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
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 »
No third-party hosts were found in this container's tags.
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_MBTSV gallery injects code from stapecdn.com · runs page-level globals__cvt_KFNBV gallery injects code from connect.facebook.net, unpkg.com · runs page-level globals__cvt_TNGP6 gallery injects code from x.cookieinformation.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-W327BHDG |
|---|---|
| Published version | 45 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:15:04 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-W327BHDG |
| Body checksum | 2b2545dd9e57305388259c698ef0c6598e6de8a6f6328fd0a46b0d611f9247b9Evidence 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 »