container audit
GTM-T922KRB
45 tags, 34 custom scripts, 7 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 34 custom HTML tags carrying 26 KB of JavaScript — more than 80% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 7 third-party hosts reachable from its tags — more than 70% of the 46,522 containers we have measured.
- Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
inner-htmlis uncommon — under 6% of the containers we have measured have it. That is context rather than a verdict: a server container is rarer still and is a sign of a mature setup. What it means is in the finding itself.
Tags45
Custom scripts34
Third parties7
Delivered496 KB
Versions37
What we observed
A real browser loaded aeg.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
www.aeg.de — the site's own host, at /gtg/gtm.js rather than the default path, and googletagmanager.comMeasurement sent to
www.aeg.de — not Google, at /analytics/g/collectMeasurement 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 ×8 — read from the measurement id, not the hostname
Consent
OneTrust answered its own API. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 8 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 — s.go-mpulse.net, cdn.cookielaw.org, www.datadoghq-browser-agent.com, c.go-mpulse.net, browser-intake-datadoghq.com, www.google.com, www.googletagmanager.com, 684d0d41.akstat.io, and 17 more
dataLayer events seen
gtm.js, OneTrustLoaded, OptanonLoaded, gtm.dom, gtm.load, gtm.elementVisibility, gtm.click, trackOptanonEvent, OneTrust_marketing_trigger, BlueConic, gtm.historyChange
Where the data goes
Confirmed — a browser watched this site send measurement data to www.aeg.de, not to Google. observed on aeg.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 (7)
7 pieces 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
reviewWrites innerHTML (1)
1 piece of custom code assign to innerHTML.
WhyAssigning innerHTML parses the string as HTML. If any of it comes from the URL, the page or a cookie, that is a script-injection route into your own site.
CheckCheck whether the assigned value is a fixed template or built from something a visitor can influence.
Seenseen in 5.7% of 46,522 containers measured
infoLoads JavaScript from another host (10)
10 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
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 »
ad2.adfarm1.adition.com ×8c.amazon-adsystem.com ×8accado.adspirit.de ×4aax-eu.amazon-adsystem.com ×3ad4.adfarm1.adition.com ×1ib.adnxs.com ×1secure.adnxs.com ×1
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.
What this audit describes
Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.
| Container | GTM-T922KRB |
|---|---|
| Published version | 37 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:08:47 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-T922KRB |
| Body checksum | 5d2ebdfa72c70f87ef88f84464651773d071db8b172d27eebb1e92b71f8075e9Evidence 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.
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 »