container audit

GTM-MGP5ZVP

9 tags, 4 custom scripts, 4 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).

4 custom HTML tags carrying 2 KB of JavaScript. This runs on every page the container loads on.
4 third-party hosts reachable from its tags.

Tags9

Custom scripts4

Third parties4

Delivered435 KB

Versions4

What we observed

A real browser loaded tkj.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 — Google

Measurement sent to google-analytics.com — Google

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.

Third parties contacted 25 hosts — tkj-jp-f-s.snva.jp, www.googleadservices.com, b92.yahoo.co.jp, www.googletagmanager.com, checkout-api.worldshopping.jp, makeshop-multi-images.akamaized.net, platform.twitter.com, img.ak.impact-ad.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 tkj.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

infoUses browser storage (5)

5 pieces of custom code read or write localStorage or sessionStorage.

WhyBrowser storage persists across visits and is not covered by cookie consent tooling, so it is easy to overlook when auditing what you keep on a visitor's device.

CheckConfirm nothing personal is being kept there, and that it is covered by your privacy notice.

Seenseen in 23.3% 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 »

cf.im-apps.net ×1 fls.doubleclick.net ×1 s.yimg.jp ×1 www.googleadservices.com ×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.

tkj.jp

What this audit describes

Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.

Container	`GTM-MGP5ZVP`
Published version	`4` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-22 10:04:38 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-MGP5ZVP`
Body checksum	`6f926be67fffb94ea902b32d178853a30e1c95d323ab2e401469137e27e736b4` Evidence 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.

Re-audit GTM-MGP5ZVP

Check another container

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 »