tagora
container audit

GTM-MBWHQQN9

22 tags, 0 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).

Tags22
Custom scripts0
Third parties1
Delivered365 KB
Versions2

What we observed

A real browser loaded vccloud.vn 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 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). 2 hosts appeared only after consent was granted.
Third parties contacted 25 hosts — bizflycloud.vn, images.dmca.com, manage.bizflycloud.vn, hn.ss.bfcplatform.vn, chat.bizfly.vn, fonts.googleapis.com, www.googletagmanager.com, static.hotjar.com, and 17 more
dataLayer events seen gtm.dom, gtm.load

Where the data goes

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

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.

vccloud.vn

What this audit describes

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

ContainerGTM-MBWHQQN9
Published version2 — the identity of this configuration. It changes only when someone publishes.
Read at2026-08-23 17:45:04 UTC (2 months ago)
Sourcehttps://www.googletagmanager.com/gtm.js?id=GTM-MBWHQQN9
Body checksum6a624638323a636121587e8982da7547760f108eb459345727d782de971fd3b8
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-MBWHQQN9

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 »