container audit
GTM-WDGGRR
This container can hand execution to 13 third parties — more than 90% of the 46,522 containers we have measured. Each serves code it controls, which can change at any time.
- 33 custom HTML tags carrying 19 KB of JavaScript — more than 80% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 858 published versions — each one live for every visitor the moment it was published.
Tags58
Custom scripts33
Third parties13
Delivered561 KB
Versions858
What we observed
A real browser loaded lojavirtualtim.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
gtm.timbrasil.com.br — not GoogleMeasurement is first-party; the container still loads from Google. These are separate decisions, and this is the more common of the two.
Forwarded to
GA4 ×12 — read from the measurement id, not the hostname
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). 10 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — cdn-prod.securiti.ai, cdn.decibelinsight.net, resources.digital-cloud-west.medallia.com, dev.visualwebsiteoptimizer.com, collection.decibelinsight.net, app.securiti.ai, analytics-fe.digital-cloud-west.medallia.com, www.googletagmanager.com, and 17 more
dataLayer events seen
gtm.js, gtm.dom, lista-de-vitrine, gtm.triggerGroup, lista-de-ofertas, gtm.click, gtm.load
Where the data goes
Confirmed — a browser watched this site send measurement data to gtm.timbrasil.com.br, not to Google. observed on lojavirtualtim.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.
reviewHardcoded http:// URL (1)
1 piece of custom code reference a plain http:// address.
WhyOn an https:// page the browser blocks or upgrades these. Blocked means the tag quietly stops working; upgraded only works if that host also serves https.
CheckCheck whether the hosts below still respond over https, and update the URLs.
Seenseen in 12.8% of 46,522 containers measured
reviewWrites cookies directly (1)
1 piece 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
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
infoOne variable that a great deal depends on (87)
"gtm.triggers" is read by 87 tags and triggers — more than anything else in this container.
WhyGTM shows you where a variable is defined, never how much depends on it. Editing this one touches a large share of the container at once, and whatever breaks will surface somewhere that looks unrelated to the change.
CheckBefore changing it, check what reads it. If it feeds both measurement and consent or routing logic, split those uses apart first.
Seenseen in 10.1% of 46,522 containers measured
infoLoads JavaScript from another host (5)
5 pieces 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
infoVendor IDs written into custom code (2)
2 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
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 »
secure.adnxs.com ×17fls.doubleclick.net ×13analytics.tiktok.com ×3connect.facebook.net ×3s.amazon-adsystem.com ×2www. ×2www.facebook.com ×2www.google-analytics.com ×2c.amazon-adsystem.com ×1http2.mlstatic.com ×1p.teads.tv ×1sp.analytics.yahoo.com ×1www.tim.com.br ×1
What the custom templates can do
Custom templates are third-party code shipped inside the container. Injecting scripts and running page globals is ordinary for them — most tag templates need it to work — so this is an inventory, not a warning. It lists the capability each template declares so you can match it against templates you meant to install.
__cvt_5RM3Q gallery injects code from connect.facebook.net, capi-automation.s3.us-east-2.amazonaws.com · runs page-level globals__cvt_MRQN8 gallery runs page-level globalsDetected 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-WDGGRR |
|---|---|
| Published version | 858 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 13:40:05 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-WDGGRR |
| Body checksum | eb6d00e032d11d8b53be9daa14452eb77002148d4811d9ab8b4980387929f06dEvidence 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 »