container audit

GTM-WZ63HHLP

This container ships 68 hand-written scripts (44 KB of JavaScript) to every visitor — more than 96% of the 46,522 containers we have measured. That is an application's worth of code, delivered as tag configuration.

6 third-party hosts reachable from its tags.

Tags181

Custom scripts68

Third parties6

Delivered511 KB

Versions17

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.

reviewHardcoded http:// URL (49)

49 pieces of custom code reference a plain http:// address.

WhyOn an https:// page the browser blocks or upgrades these. Blocked means the tag quietly stops working; upgraded only works if that host also serves https.

CheckCheck whether the hosts below still respond over https, and update the URLs.

Seenseen in 12.8% of 46,522 containers measured

reviewWrites cookies directly (1)

1 piece 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

infoLoads JavaScript from another host (58)

58 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

infoConsent configuration detected (1)

The container declares one or more consent signals.

WhyConsent handling is present in the container. This describes what the artifact declares; what actually happened on the page is measured separately, above.

CheckConfirm these settings match the consent policy you intend to enforce, and compare them with the before-and-after observation.

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

d.line-cdn.net ×49d.line-scdn.net ×49tr.line.me ×49www.googleadservices.com ×10c.amazon-adsystem.com ×1 storage.googleapis.com ×1

What the custom templates can do

Custom templates are third-party code shipped inside the container. Injecting scripts and running page globals is ordinary for them — most tag templates need it to work — so this is an inventory, not a warning. It lists the capability each template declares so you can match it against templates you meant to install.

__cvt_172498843_29 private injects code from s.yimg.jp · runs page-level globals

__cvt_172498843_77 private injects code from s.yimg.jp · runs page-level globals

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

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 »