container audit
GTM-NML9DKN
100 tags, 0 custom scripts, 2 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 2 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.
- 303 published versions — each one live for every visitor the moment it was published.
Tags100
Custom scripts0
Third parties2
Delivered572 KB
Versions303
What we observed
A real browser loaded electrolux.it 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
www.electrolux.it — the site's own host, at /gtg/gtm.js rather than the default path, and googletagmanager.comMeasurement sent to
www.electrolux.it — not Google, at /analytics/g/collectMeasurement runs through the site's own infrastructure. Part of the tag library still comes from Google, which is normal — the two are loaded separately.
Forwarded to
GA4 ×3 — read from the measurement id, not the hostname
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. 7 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — cdn.cookielaw.org, s.go-mpulse.net, www.datadoghq-browser-agent.com, c.go-mpulse.net, trial-eum-clientnsv4-s.akamaihd.net, trial-eum-clienttons-s.akamaihd.net, 684d0d41.akstat.io, www.google.com, and 17 more
dataLayer events seen
gtm.js, OneTrustLoaded, OptanonLoaded, gtm.dom, gtm.load, BlueConic, gtm.elementVisibility
Where the data goes
Confirmed — a browser watched this site send measurement data to www.electrolux.it, not to Google. observed on electrolux.it 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.
infoUses browser storage (3)
3 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
infoConsent configuration detected (2)
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_NF7PV gallery injects code from unpkg.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-NML9DKN |
|---|---|
| Published version | 303 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:55:51 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-NML9DKN |
| Body checksum | 4a5e5766e4af65eb94c31452efe8405691d577d781d20a22a8dfcbaf8ea39d53Evidence 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 »