container audit
GTM-TSD8TZBV
84 tags, 10 custom scripts, 5 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 10 custom HTML tags carrying 6 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.
Tags84
Custom scripts10
Third parties5
Delivered561 KB
Versions14
What we observed
A real browser loaded munters.com 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
load.srvsi.munters.com — 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
Cookiebot answered its own API. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 2 fired afterwards. That is the outcome consent is meant to produce. 6 hosts appeared only after consent was granted. Google recorded
gcs=G100 (all denied).Third parties contacted
24 hosts — consent.cookiebot.com, www.google.com, consentcdn.cookiebot.com, www.googletagmanager.com, www.gstatic.com, analytics.google.com, bat.bing.com, pagead2.googlesyndication.com, and 16 more
dataLayer events seen
gtm.js, Pageview, gtm.dom, html5_video, gtm.load, gtm.click, cookie_consent_preferences, cookie_consent_statistics, cookie_consent_marketing
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on munters.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.
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 (4)
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 (2)
2 pieces 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_K8GSG gallery runs page-level globals__cvt_242939966_118 private injects code from snap.licdn.comDetected 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-TSD8TZBV |
|---|---|
| Published version | 14 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:12:59 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TSD8TZBV |
| Body checksum | 35eecc6f99d7fb41a0707c2f6af7da8fd3d0d92c824ead846046183628c1b7a1Evidence 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 »