container audit

GTM-WDCZT77P

38 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.

Tags38

Custom scripts0

Third parties0

Delivered472 KB

Versions2

What we observed

A real browser loaded kosmos.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 insight.kosmos.de — the site's own host

Measurement sent to google-analytics.com — Google

The 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 Usercentrics answered its own API. 4 hosts appeared only after consent was granted. Google recorded gcs=G111 (all granted).

Third parties contacted 23 hosts — cdn.shopify.com, web.cmp.usercentrics.eu, otlp-http-production.shopifysvc.com, shop.app, v1.api.service.cmp.usercentrics.eu, sp.stapecdn.com, kosmos-cdp-backend.tim-maier.workers.dev, app.usercentrics.eu, and 15 more

dataLayer events seen gtm.js, consent_status, page_view_stape, gtm.dom, gtm.load

Where the data goes

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

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 »

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_KF8K9 gallery injects code from analytics.tiktok.com · runs page-level globals

__cvt_KFNBV gallery injects code from connect.facebook.net · runs page-level globals

__cvt_250915489_129 private injects code from x.kosmos.de

__cvt_PBGZL gallery injects code from www.redditstatic.com · runs page-level globals

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.

kosmos.de

What this audit describes

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

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

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 »