container audit
GTM-5H9LJ6Q
42 tags, 17 custom scripts, 3 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 17 custom HTML tags carrying 19 KB of JavaScript — more than 70% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 3 third-party hosts reachable from its tags.
- Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
inner-htmlis uncommon — under 6% of the containers we have measured have it. That is context rather than a verdict: a server container is rarer still and is a sign of a mature setup. What it means is in the finding itself.
Tags42
Custom scripts17
Third parties3
Delivered514 KB
Versions125
What we observed
A real browser loaded telefonica.com.br 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
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). Google recorded
gcs=G111 (all granted).Third parties contacted
23 hosts — elasticteste-gneuexcgg0fyeud0.a03.azurefd.net, rum.hlx.page, static.cloudflareinsights.com, plugin.handtalk.me, assets.adobedtm.com, www.googletagmanager.com, edge.adobedc.net, vivo-observa-prd.apm.eastus2.azure.elastic-cloud.com, and 15 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, bannerImpression, virtual_view_promotion
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on telefonica.com.br 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.
reviewWrites cookies directly (8)
8 pieces of custom code set cookies in code.
WhyCookies set this way bypass GTM's consent settings, because the consent checks live in the tag templates rather than in raw JavaScript.
CheckIf any of these cookies are used for analytics or advertising, confirm they are still gated on a consent decision.
Seenseen in 21.2% of 46,522 containers measured
reviewWrites innerHTML (1)
1 piece of custom code assign to innerHTML.
WhyAssigning innerHTML parses the string as HTML. If any of it comes from the URL, the page or a cookie, that is a script-injection route into your own site.
CheckCheck whether the assigned value is a fixed template or built from something a visitor can influence.
Seenseen in 5.7% of 46,522 containers measured
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
infoUses browser storage (13)
13 pieces of custom code read or write localStorage or sessionStorage.
WhyBrowser storage persists across visits and is not covered by cookie consent tooling, so it is easy to overlook when auditing what you keep on a visitor's device.
CheckConfirm nothing personal is being kept there, and that it is covered by your privacy notice.
Seenseen in 23.3% of 46,522 containers measured
infoVendor IDs written into custom code (3)
3 vendor IDs are pasted directly into custom HTML rather than held in a variable or template.
WhyChanging a property, pixel or account then means editing every tag that mentions it, and any one that gets missed keeps sending to the old destination indefinitely.
CheckFine if the ID never changes. If you have ever migrated a property, check that none of these still point at the old one.
Seenseen in 31.4% of 46,522 containers measured
infoLoads JavaScript from another host (1)
1 piece of custom code fetch and run JavaScript from another host.
WhyWhatever that host serves executes with full access to the page — it can read the DOM, cookies and form fields. The code is not in this container, so it can change at any time without any change here.
CheckConfirm you recognise every host below and that someone owns the relationship. A host you cannot name is the one to chase.
Seenseen in 54.4% 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-5H9LJ6Q |
|---|---|
| Published version | 125 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 09:49:50 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-5H9LJ6Q |
| Body checksum | 39c3a6aecf0abb1e1f67140a1a70290a92abf4e5897b5a8fe4018f058e7d4df1Evidence 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 »