container audit

GTM-TSJ9CV8

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

2 third-party hosts reachable from its tags.

Tags83

Custom scripts51

Third parties2

Delivered480 KB

Versions52

What we observed

A real browser loaded creativepark.canon 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

Third parties contacted 9 hosts — www.googletagmanager.com, www.youtube.com, fonts.gstatic.com, googleads.g.doubleclick.net, static.doubleclick.net, i.ytimg.com, www.gstatic.com, www.google.com, and 1 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 creativepark.canon 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

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 »

www.google-analytics.com ×28creativepark.canon ×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.

creativepark.canon

What this audit describes

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

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

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 »