container audit
GTM-TK9LHFB
79 tags, 7 custom scripts, 3 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 7 custom HTML tags carrying 3 KB of JavaScript. 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.
Tags79
Custom scripts7
Third parties3
Delivered517 KB
Versions152
What we observed
A real browser loaded sony.jp 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.bo.sony.jp — the site's own host, at /v3/__https://www.googletagmanager.com/gtag/js rather than the default path, and googletagmanager.comMeasurement sent to
sgtm.bo.sony.jp — 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 ×6 — read from the measurement id, not the hostname
Consent
no consent gate responded on this page, so there was nothing to hold measurement back (banners are often shown only to visitors in certain regions, and this was not a European visit). 2 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — tags.tiqcdn.com, dpm.demdex.net, www.facebook.com, smoj.demdex.net, cm.everesttech.net, static.xx.fbcdn.net, collect.tealiumiq.com, cache.dga.jp, and 17 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load
Where the data goes
Confirmed — a browser watched this site send measurement data to sgtm.bo.sony.jp, not to Google. observed on sony.jp 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.
reviewNo consent signal in the container (1)
Nothing in this container sets, reads, or gates on a consent state.
WhyThe container itself neither sets a Consent Mode default, holds any tag back for consent, nor references a known consent platform. Either enforcement lives entirely outside GTM — where it cannot be audited from here — or tags fire regardless of what a visitor chose.
CheckIf a consent platform blocks scripts before GTM loads, this is fine — confirm that is actually the case. If not, tags are firing on a choice nobody recorded.
Seenseen in 52.1% 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 »
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-TK9LHFB |
|---|---|
| Published version | 152 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 10:43:30 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TK9LHFB |
| Body checksum | 1160a24b6e07d7604abf610c5dc32c7cc84d52b6c790e93ca0a31fe9a4143b45Evidence 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 »