container audit

GTM-P5J6D7GL

This container is published but empty — no tags, so nothing fires.

Tags0

Custom scripts0

Third parties0

Delivered315 KB

Versions1

What we observed

A real browser loaded smile-zemi.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 tracker.smile-zemi.jp, ga4lap.smile-zemi.jp — not Google

Measurement 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 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). 7 hosts appeared only after consent was granted. Google recorded gcs=G111 (all granted).

Third parties contacted 25 hosts — fonts.googleapis.com, cdn.jsdelivr.net, unpkg.com, www.googletagmanager.com, www.youtube.com, smilezemi.microcms.io, tr.webantenna.info, cdn-blocks.karte.io, and 17 more

dataLayer events seen gtm.js, gtm.dom, spideraf.pv.score.ok, gtm.elementVisibility, gtm.load

Where the data goes

Confirmed — a browser watched this site send measurement data to tracker.smile-zemi.jp, ga4lap.smile-zemi.jp, not to Google. observed on smile-zemi.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.

No findings were raised for this container.

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 »

No third-party hosts were found in this container's tags.

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.

smile-zemi.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-P5J6D7GL`
Published version	`1` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 17:59:54 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-P5J6D7GL`
Body checksum	`407f712282558a29c773bff45c6f24f274ff4a8de99ef2cdc9766196141f2063` 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-P5J6D7GL

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 »