container audit
GTM-TBXGHH7
7 tags, no hand-written scripts, 1 third-party host — smaller than 80% of the 46,522 containers we have measured, and carrying none of the hand-written JavaScript most of them do.
- 1 third-party host reachable from its tags.
Tags7
Custom scripts0
Third parties1
Delivered373 KB
Versions10
What we observed
A real browser loaded asianstudies.org 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 — GoogleMeasurement sent to
google-analytics.com — GoogleConsent
Cookiebot answered its own API. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 1 fired afterwards. That is the outcome consent is meant to produce. 7 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
14 hosts — use.fontawesome.com, consent.cookiebot.com, fonts.googleapis.com, static.cloudflareinsights.com, consentcdn.cookiebot.com, cdn.jsdelivr.net, stats.wp.com, www.clarity.ms, and 6 more
dataLayer events seen
cookie_consent_preferences, cookie_consent_statistics, cookie_consent_marketing, 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 asianstudies.org 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 »
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.
What this audit describes
Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.
| Container | GTM-TBXGHH7 |
|---|---|
| Published version | 10 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:09:25 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TBXGHH7 |
| Body checksum | 03a4f32d5ae3fc59dab6eaf6bc70cc45891d4cc21e9ed0bcb8d69313c821ffb3Evidence 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.
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 »