tagora
container audit

GTM-NWN6RH6

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

Tags2
Custom scripts0
Third parties0
Delivered306 KB
Versions72

What we observed

A real browser loaded b0e8.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 3 hosts — marvel-b2-cdn.bc0a.com, cdnjs.cloudflare.com, www.brightedge.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 b0e8.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.

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

reviewEvents for a service that no longer exists (1)
Google Optimize (retired by Google in September 2023).

WhyThe container still listens for and reacts to events belonging to a product that has been switched off. Whatever those triggers fire can no longer do anything useful, and the tags behind them are still downloaded by every visitor.

CheckConfirm nothing else depends on those triggers, then remove the tags and the triggers together — deleting only the tag leaves the listener in place.

Seenseen in 0.9% 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 »

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.

b0e8.com

What this audit describes

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

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

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 »