tagora
container audit

GTM-5J9LZDFB

This container is published but empty — no tags, so nothing fires.

Tags0
Custom scripts0
Third parties0
Delivered315 KB
Versions3

What we observed

A real browser loaded aus.com 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 OneTrust answered its own API. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 2 fired afterwards. That is the outcome consent is meant to produce. 10 hosts appeared only after consent was granted. Google recorded gcs=G111 (all granted).
Third parties contacted 25 hosts — cdn.cookielaw.org, cdn.jsdelivr.net, use.fontawesome.com, code.jquery.com, fast.wistia.com, www.googletagmanager.com, fast.wistia.net, geolocation.onetrust.com, and 17 more
dataLayer events seen gtm.js, gtm.dom, OneTrustLoaded, OptanonLoaded, gtm.load, gtm.click

Where the data goes

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

aus.com

What this audit describes

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

ContainerGTM-5J9LZDFB
Published version3 — the identity of this configuration. It changes only when someone publishes.
Read at2026-08-22 09:49:59 UTC (2 months ago)
Sourcehttps://www.googletagmanager.com/gtm.js?id=GTM-5J9LZDFB
Body checksum20f8cb1d3ed0e65ba5db39e914f5b824b702b6476fa3692a07c541f1c5491167
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-5J9LZDFB

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 »