container audit

GTM-MFZGFSR5

10 tags, no hand-written scripts, 2 third-party hosts — smaller than 75% of the 46,522 containers we have measured, and carrying none of the hand-written JavaScript most of them do.

2 third-party hosts reachable from its tags.

Tags10

Custom scripts0

Third parties2

Delivered452 KB

Versions12

What we observed

A real browser loaded onyx.app 2 months 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 onyx.app — the site's own host, at /gt_m5w8x/gtm.js rather than the default path, and googletagmanager.com

Measurement sent to google-analytics.com — Google

The container is self-hosted; the measurement still goes to Google. The first-party path that a tagging server provides is not being used for the data itself.

Consent a consent platform is present, but our browser could not complete the accept step — so the before-and-after comparison did not run here.

Third parties contacted 14 hosts — api.cr-relay.com, cdn.vector.co, api.vector.co, www.redditstatic.com, www.googletagmanager.com, snap.licdn.com, px.ads.linkedin.com, www.google.com, and 6 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 onyx.app 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

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 ×3 www.googleadservices.com ×2

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_196014214_6 private injects code from snap.licdn.com

__cvt_PBGZL gallery injects code from www.redditstatic.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.

onyx.app

What this audit describes

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

Container	`GTM-MFZGFSR5`
Published version	`12` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 17:45:56 UTC (2 months ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-MFZGFSR5`
Body checksum	`b02cba4fcc1c3ca3dc5708cd9f016ae697572cfb0ecb3d9c4bd45e68a721a110` 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 2 months 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-MFZGFSR5

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 »