container audit

GTM-W8MC72X

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

2 custom HTML tags carrying 1 KB of JavaScript. This runs on every page the container loads on.
4 third-party hosts reachable from its tags.

Tags48

Custom scripts2

Third parties4

Delivered482 KB

Versions64

What we observed

A real browser loaded menta.work 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).

Third parties contacted 20 hosts — c575a2f349c8.a17e85aa.ap-northeast-1.token.awswaf.com, cdn.jsdelivr.net, www.googletagmanager.com, connect.facebook.net, pagead2.googlesyndication.com, platform.twitter.com, www.google-analytics.com, www.clarity.ms, and 12 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 menta.work 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 (4)

4 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

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

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 »

www.google-analytics.com ×6 www.googleadservices.com ×5 connect.facebook.net ×1 www.facebook.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_12496630_66 private injects code from www.clarity.ms · runs page-level globals

__cvt_12496630_78 private injects code from static.ads-twitter.com · runs page-level globals

__cvt_12496630_80 private injects code from static.ads-twitter.com · 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.

menta.work

What this audit describes

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

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

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 »