container audit

GTM-WGV23JJC

80 tags, 16 custom scripts, 3 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).

16 custom HTML tags carrying 15 KB of JavaScript — more than 70% of the 46,522 containers we have measured. This runs on every page the container loads on.
3 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.

Tags80

Custom scripts16

Third parties3

Delivered536 KB

Versions239

What we observed

A real browser loaded kartenliebe.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 sst.kartenliebe.de — the site's own host, and googletagmanager.com

Measurement sent to sst.kartenliebe.de — not Google

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 ×2 — read from the measurement id, not the hostname

Consent Didomi 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 22 hosts — widget.trustpilot.com, static.hotjar.com, sdk.split.io, auth.split.io, a.storyblok.com, www.googletagmanager.com, metrics.hotjar.io, s.pinimg.com, and 14 more

dataLayer events seen didomi-consent, didomi-ready, kl_shop_landingpage_viewed, landingpage_view, gtm.js, gtm.dom, gtm.load, didomi-cookies-consent, didomi-consent-changed

Where the data goes

Confirmed — a browser watched this site send measurement data to sst.kartenliebe.de, not to Google. observed on kartenliebe.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.

reviewWrites cookies directly (4)

4 pieces of custom code set cookies in code.

WhyCookies set this way bypass GTM's consent settings, because the consent checks live in the tag templates rather than in raw JavaScript.

CheckIf any of these cookies are used for analytics or advertising, confirm they are still gated on a consent decision.

Seenseen in 21.2% of 46,522 containers measured

infoLoads JavaScript from another host (4)

4 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 (2)

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

infoUses browser storage (1)

1 piece of custom code read or write localStorage or sessionStorage.

WhyBrowser storage persists across visits and is not covered by cookie consent tooling, so it is easy to overlook when auditing what you keep on a visitor's device.

CheckConfirm nothing personal is being kept there, and that it is covered by your privacy notice.

Seenseen in 23.3% 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 »

api.sovendus.com ×1 cdn.debugbear.com ×1 integration.loopingo.com ×1

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_KFNBV gallery injects code from connect.facebook.net, unpkg.com · runs page-level globals

__cvt_181044947_180 private injects code from dynamic.criteo.com

__cvt_579DB gallery runs page-level globals

__cvt_KDTBT gallery injects code from js.appboycdn.com · runs page-level globals

__cvt_M3KBL gallery runs page-level globals

__cvt_WKXGH gallery injects code from api.sovendus.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.

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

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 »