container audit

GTM-W8R2T467

34 tags, 8 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).

8 custom HTML tags carrying 11 KB of JavaScript. This runs on every page the container loads on.
1 third-party host 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.

Tags34

Custom scripts8

Third parties1

Delivered457 KB

Versions46

What we observed

A real browser loaded newshades.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 not observed loading

Measurement sent to google-analytics.com — Google

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

Third parties contacted 25 hosts — a.storyblok.com, cdn.shopify.com, events.drip-apex.com, consent.cookiebot.com, consentcdn.cookiebot.com, monorail-edge.shopifysvc.com, bat.bing.com, www.clarity.ms, and 17 more

dataLayer events seen gtm.js, shopify_page_view, page_load, view_homepage, gtm.dom, gtm.load, gtm.triggerGroup, cookie_consent_preferences, cookie_consent_statistics, cookie_consent_marketing

Where the data goes

Nothing fired — we loaded the page and no tag library or measurement request ran, which usually means a consent banner held everything back. The container below still describes what would run once it does. observed on newshades.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.

reviewdocument.write (1)

1 piece of custom code call document.write.

Whydocument.write blocks the HTML parser while it runs, and browsers ignore it entirely once the page has finished parsing — so an async-loaded tag using it can silently do nothing.

CheckIf these tags fire on page load they are costing render time; if they fire later they may not be working at all. Worth confirming the tag still does what it was added to do.

Seenseen in 18.4% of 46,522 containers measured

infoConsent configuration detected (3)

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 »

connect.facebook.net ×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_5RM3Q gallery injects code from connect.facebook.net · runs page-level globals

__cvt_MQDKZ gallery injects code from www.clarity.ms · 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.

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

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 »