container audit
GTM-NCWXWBN2
This container ships 41 hand-written scripts (140 KB of JavaScript) to every visitor — more than 90% of the 46,522 containers we have measured. That is an application's worth of code, delivered as tag configuration.
- 6 third-party hosts reachable from its tags.
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.
Tags41
Custom scripts41
Third parties6
Delivered484 KB
Versions15
What we observed
A real browser loaded heineken.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
www.heineken.com — the site's own host, at /hei-sst/gtm.js rather than the default path, and googletagmanager.comMeasurement sent to
www.heineken.com — not Google, at /hei-sst/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 ×6 — read from the measurement id, not the hostname
Consent
OneTrust answered its own API. Measurement fired beforehand but carried no identifier —
analytics_storage was denied, which is Consent Mode working as designed rather than a gap. no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision. Google recorded gcs=G100 (all denied).Third parties contacted
17 hosts — fonts.googleapis.com, cdn.cookielaw.org, js.monitor.azure.com, www.googletagmanager.com, geolocation.onetrust.com, pagead2.googlesyndication.com, www.google-analytics.com, westeurope-5.in.applicationinsights.azure.com, and 9 more
dataLayer events seen
gtm.js, OneTrustLoaded, OptanonLoaded, gtm.dom, gtm.load, page_view, gtm.click
Where the data goes
Confirmed — a browser watched this site send measurement data to www.heineken.com, not to Google. observed on heineken.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.
reviewWrites innerHTML (40)
40 pieces 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 (39)
39 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
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 »
www.moderationmatters.com ×39issuu.com ×1www.iard.org ×1www.nhs.uk ×1www.niaaa.nih.gov ×1www.who.int ×1
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-NCWXWBN2 |
|---|---|
| Published version | 15 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-12 22:36:59 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-NCWXWBN2 |
| Body checksum | 8cb9ca79ee804b89802a9eb7285e86075078485d3c37ffcbca8e76ea6e805485Evidence 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 »