container audit

GTM-WS2HF4K

42 tags, 2 custom scripts, 4 third-party hosts — 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.
4 third-party hosts reachable from its tags.

Tags42

Custom scripts2

Third parties4

Delivered406 KB

Versions40

What we observed

A real browser loaded xn--allestrungen-9ib.de 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 — Google

Measurement sent to google-analytics.com — Google

Consent OneTrust answered its own API. Measurement fired beforehand but carried no identifier — analytics_storage was denied, which is Consent Mode working as designed rather than a gap. 10 hosts appeared only after consent was granted. Google recorded gcs=G100 (all denied).

Third parties contacted 25 hosts — cdn3.downdetector.com, cdn.ziffstatic.com, securepubads.g.doubleclick.net, cdn.cookielaw.org, geolocation.onetrust.com, openads-cdn.adsrvr.org, config.aps.amazon-adsystem.com, client.aps.amazon-adsystem.com, and 17 more

dataLayer events seen virtualPageview, zdconsentloaded, zdconsent-loaded, gtm.js, gtm.dom, gtm.load, zdconsentgiven, zdconsent-targeting, evidonConsentGiven, zdconsent-functional, zdconsent-analytics, gtm.click, +2 more

Where the data goes

Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on xn--allestrungen-9ib.de 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

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

infoConsent configuration detected (1)

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 »

www.google-analytics.com ×40b ×1 sb ×1 secure-us.imrworldwide.com ×1

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.

xn--allestrungen-9ib.de downdetector.co.uk

What this audit describes

Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.

Container	`GTM-WS2HF4K`
Published version	`40` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 18:21:19 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-WS2HF4K`
Body checksum	`68996a09c0d4c6aa703531942c43c73dd54588ecfea37870e7c9f86237106ffd` Evidence 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.

Re-audit GTM-WS2HF4K

Check another container

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 »