tagora
container audit

GTM-NDGM7K

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

Tags3
Custom scripts0
Third parties0
Delivered317 KB
Versions47

What we observed

A real browser loaded wtaj.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 not observed loading
Measurement sent to google-analytics.com — Google
Third parties contacted 4 hosts — fonts.googleapis.com, i0.wp.com, h104216-ucdn.mp.lura.live, cdn.bestreviews.com

Where the data goes

Nothing fired — we loaded the page and no tag library or measurement request ran, which usually means a consent banner held everything back. The container below still describes what would run once it does. observed on wtaj.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.

No findings were raised for this container.

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 »

No third-party hosts were found in this container's tags.

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.

wtaj.com

What this audit describes

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

ContainerGTM-NDGM7K
Published version47 — the identity of this configuration. It changes only when someone publishes.
Read at2026-08-23 17:53:38 UTC (a month ago)
Sourcehttps://www.googletagmanager.com/gtm.js?id=GTM-NDGM7K
Body checksuma468cc84f6d4a27647b5a7f410145ad69544e7d8ecdfe1e304ae212a098855c6
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-NDGM7K

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 »