container audit

GTM-W5DTVSDH

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

Tags15

Custom scripts0

Third parties0

Delivered473 KB

Versions10

What we observed

A real browser loaded steinel.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 c35.steinel.de — not Google

Measurement is first-party; the container still loads from Google. These are separate decisions, and this is the more common of the two.

Forwarded to GA4 ×2 — read from the measurement id, not the hostname

Consent Usercentrics 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. 9 hosts appeared only after consent was granted. Google recorded gcs=G111 (all granted).

Third parties contacted 24 hosts — web.cmp.usercentrics.eu, chimpstatic.com, player.vimeo.com, www.googletagmanager.com, connect.nosto.com, cdn.eye-able.com, v1.api.service.cmp.usercentrics.eu, jserror.nosto.com, and 16 more

dataLayer events seen gtm.js, gtm.dom, consent_status, Custom Dimensions, gtm.load

Where the data goes

Confirmed — a browser watched this site send measurement data to c35.steinel.de, not to Google. observed on steinel.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_208468665_275 private injects code from snap.licdn.com

__cvt_5RM3Q gallery injects code from connect.facebook.net, capi-automation.s3.us-east-2.amazonaws.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.

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

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 »