container audit
GTM-KPNGNC
This container ships 84 hand-written scripts (49 KB of JavaScript) to every visitor — more than 97% of the 46,522 containers we have measured. That is an application's worth of code, delivered as tag configuration.
- 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.
Tags134
Custom scripts84
Third parties3
Delivered604 KB
Versions114
What we observed
A real browser loaded t-2.net 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
sgtm.t-2.net — the site's own hostMeasurement sent to
sgtm.t-2.net — not GoogleBoth wires run through infrastructure the site controls.
Forwarded to
GA4 ×2 — read from the measurement id, not the hostname
Consent
a consent platform is present, but our browser could not complete the accept step — so the before-and-after comparison did not run here. 10 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — cdn-cookieyes.com, hcaptcha.com, use.typekit.net, t-2.boost.ai, log.cookieyes.com, web-sdk.urbanairship.com, platform.twitter.com, f43724d6a2f9.w.hcaptcha.com, and 17 more
dataLayer events seen
gtm.js, EEC_promotion_impressions, RO_event_EEC, gtm.dom, gtm.load, event_WWW_Homepage_banner_impression
Where the data goes
Confirmed — a browser watched this site send measurement data to sgtm.t-2.net, not to Google. observed on t-2.net 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 (1)
1 piece 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
infoOne variable that a great deal depends on (105)
"gtm.element" is read by 105 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 (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
infoLoads JavaScript from another host (2)
2 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
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_KDQSW gallery injects code from cdn-cookieyes.com__cvt_K8GSG gallery runs page-level globals__cvt_1749811_560 private injects code from dynamic.criteo.com__cvt_1749811_564 private runs page-level globals__cvt_5RM3Q gallery injects code from connect.facebook.net, capi-automation.s3.us-east-2.amazonaws.com · runs page-level globals__cvt_KT4F4 gallery injects code from c.amazon-adsystem.com · runs page-level globals__cvt_PBGZL gallery injects code from www.redditstatic.com · runs page-level globalsDetected 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-KPNGNC |
|---|---|
| Published version | 114 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-12 22:25:34 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-KPNGNC |
| Body checksum | 466f9ab243bc6d5704d2f41761f4ddc92a3a098580e1420f6937f5b052346d42Evidence 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 »