container audit

GTM-NF5R

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

802 published versions — each one live for every visitor the moment it was published.

Tags352

Custom scripts186

Third parties28

Delivered725 KB

Versions802

What we observed

A real browser loaded nomu.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 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 — www.googletagservices.com, www.googletagmanager.com, securepubads.g.doubleclick.net, 6d8262201683ebeefa3fca8e745dc8b7.safeframe.googlesyndication.com, ob.itstarsbuilding.com, cdn.kaizenplatform.net, cdn.cookie.sync.usonar.jp, assets.v2.sprocket.bz, and 17 more

dataLayer events seen gtm.js, gtm.dom, clientIdLoaded, set_ip2cinfo, gtm.load, gtm.scrollDepth

Where the data goes

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

reviewdocument.write (84)

84 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

infoOne variable that a great deal depends on (72)

"gtm.triggers" is read by 72 tags and triggers — more than anything else in this container.

WhyGTM shows you where a variable is defined, never how much depends on it. Editing this one touches a large share of the container at once, and whatever breaks will surface somewhere that looks unrelated to the change.

CheckBefore changing it, check what reads it. If it feeds both measurement and consent or routing logic, split those uses apart first.

Seenseen in 10.1% of 46,522 containers measured

infoLoads JavaScript from another host (38)

38 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 (7)

7 vendor IDs are 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 »

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_56800_856 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.

nomu.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-NF5R`
Published version	`802` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-13 12:19:31 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-NF5R`
Body checksum	`42caef2ca663e2749fdf074e70f3b3fb600183a6a72bed8dd6d139d4b09aa140` 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-NF5R

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 »