container audit
GTM-K94GQFF
53 tags, 24 custom scripts, 12 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 24 custom HTML tags carrying 11 KB of JavaScript — more than 80% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 12 third-party hosts reachable from its tags — more than 80% of the 46,522 containers we have measured.
Tags53
Custom scripts24
Third parties12
Delivered503 KB
Versions56
What we observed
A real browser loaded royalhost.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 — ajax.googleapis.com, www.google-analytics.com, www.googletagmanager.com, s.yimg.jp, connect.facebook.net, www.clarity.ms, static.hotjar.com, d.line-scdn.net, 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 royalhost.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.
reviewUniversal Analytics tags still shipped (9)
9 Universal Analytics tags are still in the container.
WhyUniversal Analytics stopped processing data in July 2023. These tags still download and execute on every matching page, and send to an endpoint that discards them.
CheckNothing is being collected from these. Confirm the equivalent GA4 tag exists, then delete them.
Seenseen in 23.2% of 46,522 containers measured
reviewdocument.write (6)
6 pieces of custom code call document.write.
Whydocument.write blocks the HTML parser while it runs, and browsers ignore it entirely once the page has finished parsing — so an async-loaded tag using it can silently do nothing.
CheckIf these tags fire on page load they are costing render time; if they fire later they may not be working at all. Worth confirming the tag still does what it was added to do.
Seenseen in 18.4% of 46,522 containers measured
reviewHardcoded http:// URL (1)
1 piece 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
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 (4)
4 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
infoUses browser storage (2)
2 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
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 »
static.criteo.net ×5www.googleadservices.com ×5connect.facebook.net ×4www.facebook.com ×4d.line-cdn.net ×1d.line-scdn.net ×1dmp.im-apps.net ×1googleads.g.doubleclick.net ×1static.hotjar.com ×1tr.line.me ×1www.clarity.ms ×1www.google-analytics.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_48111245_10 private injects code from s.yimg.jp · runs page-level globals__cvt_48111245_15 private injects code from s.yimg.jp · runs page-level globals__cvt_48111245_16 private injects code from s.yimg.jp · runs page-level globals__cvt_48111245_8 private injects code from s.yimg.jp · runs page-level globals__cvt_48111245_9 private injects code from s.yimg.jp · runs page-level globalsDetected 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-K94GQFF |
|---|---|
| Published version | 56 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 14:00:53 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-K94GQFF |
| Body checksum | 7b73f3d721cdadfe8e830e7720d7ea4ae57c7d1899761140391734fa1f6ed5ecEvidence 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 »