container audit
GTM-59SJPQ8
106 tags, 4 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 4 custom HTML tags carrying 9 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.
Tags106
Custom scripts4
Third parties1
Delivered487 KB
Versions258
What we observed
A real browser loaded golfdigest.co.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
googletagmanager.com — GoogleMeasurement sent to
sgtm.golfdigest.co.jp — not GoogleMeasurement is first-party; the container still loads from Google. These are separate decisions, and this is the more common of the two.
Forwarded to
GA4 ×4 — read from the measurement id, not the hostname
Consent
Quantcast answered its own API. 4 measurement hits left the page before it was granted, carrying a client id (whether that is permitted depends on jurisdiction, and this was not a European visit). no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision. Google recorded
gcs=G1 (no consent signal). 7 advertising hosts were contacted before anything was granted.Third parties contacted
25 hosts — i.gimg.jp, cdnjs.cloudflare.com, securepubads.g.doubleclick.net, www.googletagmanager.com, fundingchoicesmessages.google.com, cdn-edge.karte.io, www.clarity.ms, cdn.hera.d2c.ne.jp, and 17 more
dataLayer events seen
spideraf.pv.score.block, gtm.dom, gtm.load
Where the data goes
Confirmed — a browser watched this site send measurement data to sgtm.golfdigest.co.jp, not to Google. observed on golfdigest.co.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.
reviewWrites cookies directly (5)
5 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
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-59SJPQ8 |
|---|---|
| Published version | 258 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 10:17:27 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-59SJPQ8 |
| Body checksum | 2482c6d489c0044a54751e331b71c7e591789f695973565d5b434cbf3af8b394Evidence 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 »