container audit

GTM-P6XG3QFS

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

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

Tags25

Custom scripts14

Third parties5

Delivered456 KB

Versions16

What we observed

A real browser loaded kao-kirei.com 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 OneTrust answered its own API. 3 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). 10 hosts appeared only after consent was granted. Google recorded gcs=G111 (all granted). 10 advertising hosts were contacted before anything was granted.

Third parties contacted 25 hosts — assets.adobedtm.com, kao-h.assetsadobe3.com, dpm.demdex.net, cdns.gigya.com, www.googletagmanager.com, js.withdesk.com, kao.demdex.net, cm.everesttech.net, and 17 more

dataLayer events seen gtm.js, gtm.dom, OneTrustLoaded, OptanonLoaded, gtm.load, cdcuid_update_complete, gtm.triggerGroup

Where the data goes

Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on kao-kirei.com 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

infoLoads JavaScript from another host (6)

6 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

infoVendor IDs written into custom code (1)

1 vendor ID is pasted directly into custom HTML rather than held in a variable or template.

WhyChanging a property, pixel or account then means editing every tag that mentions it, and any one that gets missed keeps sending to the old destination indefinitely.

CheckFine if the ID never changes. If you have ever migrated a property, check that none of these still point at the old one.

Seenseen in 31.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 »

connect.facebook.net ×8 www.facebook.com ×7 www.googleadservices.com ×7 analytics.tiktok.com ×6 www.google-analytics.com ×4

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.

kao-kirei.com

What this audit describes

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

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

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 »