container audit
GTM-K4XT6D8
117 tags, 16 custom scripts, 4 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 16 custom HTML tags carrying 18 KB of JavaScript — more than 70% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 4 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.
Tags117
Custom scripts16
Third parties4
Delivered601 KB
Versions256
What we observed
A real browser loaded payone.com 2 months 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
sswt.payone.com — the site's own host, and googletagmanager.comMeasurement sent to
sswt.payone.com — not GoogleMeasurement 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
Usercentrics answered its own API. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 1 fired afterwards. That is the outcome consent is meant to produce. 4 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
15 hosts — widget.moin.ai, www.googletagmanager.com, unpkg.com, web.cmp.usercentrics.eu, v1.api.service.cmp.usercentrics.eu, app.usercentrics.eu, uct.service.usercentrics.eu, consent-api.service.consent.usercentrics.eu, and 7 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, gtm.elementVisibility, consent_status
Where the data goes
Confirmed — a browser watched this site send measurement data to sswt.payone.com, not to Google. observed on payone.com 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 (6)
6 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
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
infoOne variable that a great deal depends on (57)
"gtm.triggers" is read by 57 tags and triggers — more than anything else in this container.
WhyGTM shows you where a variable is defined, never how much depends on it. Editing this one touches a large share of the container at once, and whatever breaks will surface somewhere that looks unrelated to the change.
CheckBefore changing it, check what reads it. If it feeds both measurement and consent or routing logic, split those uses apart first.
Seenseen in 10.1% of 46,522 containers measured
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 »
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_NMDHS gallery injects code from app.usercentrics.eu, web.cmp.usercentrics.eu · runs page-level globals__cvt_46687144_1249 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__cvt_NF7PV gallery injects code from unpkg.comDetected 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-K4XT6D8 |
|---|---|
| Published version | 256 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:35:43 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-K4XT6D8 |
| Body checksum | e3a6df33c0f272b0978c3c083c49fa3f38e90b95832e85d3e03b940444e34a50Evidence 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 2 months 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 »