container audit
GTM-TK8Z594Q
409 tags, 583 KB delivered to every visitor — more than 96% of the 46,522 containers we have measured. Size is a description here, not a fault.
- 3 custom HTML tags carrying 3 KB of JavaScript. This runs on every page the container loads on.
- 4 third-party hosts reachable from its tags.
Tags409
Custom scripts3
Third parties4
Delivered583 KB
Versions120
What we observed
A real browser loaded hipro-job.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
google-analytics.com — GoogleConsent
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).
Third parties contacted
25 hosts — cdn.jsdelivr.net, www.googletagmanager.com, use.typekit.net, ajax.googleapis.com, www.google.com, ad.doubleclick.net, p.typekit.net, s.yimg.jp, and 17 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on hipro-job.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
infoOne variable that a great deal depends on (106)
"gtm.triggers" is read by 106 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
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 »
www.google-analytics.com ×406biz.hipro-job.jp ×3corp.tech.hipro-job.jp ×1images.microcms-assets.io ×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-TK8Z594Q |
|---|---|
| Published version | 120 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:10:47 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TK8Z594Q |
| Body checksum | 6698cefd663dc9b8bcc19729e4096dc4f95e16536bbb57c7f90600b024c0a792Evidence 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 »