container audit
GTM-TB7ZTT2
19 tags, 9 custom scripts, 3 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 9 custom HTML tags carrying 7 KB of JavaScript. This runs on every page the container loads on.
- 3 third-party hosts reachable from its tags.
Tags19
Custom scripts9
Third parties3
Delivered398 KB
Versions14
What we observed
A real browser loaded ticketmaster.com.mx 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
OneTrust answered its own API. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 0 fired afterwards. That is the outcome consent is meant to produce. Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — uk.tmconst.com, prismic-images.tmol.io, www.googletagmanager.com, promoted.ticketmaster.com, s1.ticketm.net, www.google.com, www.gstatic.com, cdn.cookielaw.org, and 17 more
dataLayer events seen
gtm.js, homepage.mx.ticketmaster.iccp-discovery, gtm.dom, gtm.load, OneTrustLoaded, OptanonLoaded, consent.mx.statuschange.onetrust, gtm.triggerGroup
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on ticketmaster.com.mx 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.
reviewUniversal Analytics tags still shipped (2)
2 Universal Analytics tags are still in the container.
WhyUniversal Analytics stopped processing data in July 2023. These tags still download and execute on every matching page, and send to an endpoint that discards them.
CheckNothing is being collected from these. Confirm the equivalent GA4 tag exists, then delete them.
Seenseen in 23.2% of 46,522 containers measured
infoConsent configuration detected (1)
The container declares one or more consent signals.
WhyConsent handling is present in the container. This describes what the artifact declares; what actually happened on the page is measured separately, above.
CheckConfirm these settings match the consent policy you intend to enforce, and compare them with the before-and-after observation.
Seenseen in 44.6% 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-TB7ZTT2 |
|---|---|
| Published version | 14 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 10:41:33 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TB7ZTT2 |
| Body checksum | b04e5477760455134473a81021ac100a9f7c881ec7bbdab9a201d0ef64d2fc3eEvidence 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 »