tagora
container audit

GTM-WMFM3KXN

5 tags, no hand-written scripts, 0 third-party hosts — smaller than 83% of the 46,522 containers we have measured, and carrying none of the hand-written JavaScript most of them do.

Tags5
Custom scripts0
Third parties0
Delivered371 KB
Versions9

What we observed

A real browser loaded formelskin.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 data.formelskin.de — the site's own host, and googletagmanager.com
Measurement sent to formelskin.de — not Google, at /data/g/collect

Measurement 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 ×3 — read from the measurement id, not the hostname
Consent Klaro 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. 1 host appeared only after consent was granted. Google recorded gcs=G100 (all denied).
Third parties contacted 14 hosts — widgets.trustedshops.com, a.storyblok.com, o403186.ingest.sentry.io, dev.visualwebsiteoptimizer.com, www.googletagmanager.com, app.storyblok.com, pagead2.googlesyndication.com, analytics.google.com, and 6 more
dataLayer events seen gtm.js, PageView, gads_session_seed, gtm.dom, gtm.load, consent_status, gtm.historyChange, gtm.historyChange-v2

Where the data goes

Confirmed — a browser watched this site send measurement data to formelskin.de, not to Google. observed on formelskin.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_223722225_3 private injects code from stapecdn.com, formelskin.de, data.formelskin.de · 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.

formelskin.de

What this audit describes

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

ContainerGTM-WMFM3KXN
Published version9 — the identity of this configuration. It changes only when someone publishes.
Read at2026-08-23 18:19:56 UTC (a month ago)
Sourcehttps://www.googletagmanager.com/gtm.js?id=GTM-WMFM3KXN
Body checksum0ee7e229cee49df9fa8ff0147803348c9f8eb2dcb755b8b73357d7f0998c2e33
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-WMFM3KXN

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 »