container audit
GTM-T87N2G6
372 tags, 593 KB delivered to every visitor — more than 96% of the 46,522 containers we have measured. Size is a description here, not a fault.
- 2 custom HTML tags carrying 2 KB of JavaScript. This runs on every page the container loads on.
- 3 third-party hosts reachable from its tags.
Tags372
Custom scripts2
Third parties3
Delivered593 KB
Versions47
What we observed
A real browser loaded unfi.com 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
a consent banner was present and we accepted it. 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. 3 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
13 hosts — cdnjs.cloudflare.com, cdn-prod.securiti.ai, app.securiti.ai, www.googletagmanager.com, player.vimeo.com, snap.licdn.com, f.vimeocdn.com, i.vimeocdn.com, and 5 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, gtm.click, gtm.linkClick
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on unfi.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.
infoOne variable that a great deal depends on (83)
"gtm.triggers" is read by 83 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
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 »
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_12061031_82 private runs page-level globals__cvt_12061031_64 private injects code from snap.licdn.comDetected 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-T87N2G6 |
|---|---|
| Published version | 47 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:08:25 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-T87N2G6 |
| Body checksum | b2cb3bd14121852c48a7b8c3916d9b920e89a240460bad28e1edd49ac1b30866Evidence 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 »