container audit
GTM-T37F5BH
This container is published but empty — no tags, so nothing fires.
Tags0
Custom scripts0
Third parties0
Delivered353 KB
Versions9
What we observed
A real browser loaded opel.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. 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
7 hosts — rum.hlx.page, schema.milestoneinternet.com, ressource.gdpr-banner.awsmpsa.com, api.gdpr-banner.awsmpsa.com, europe-west1-cookiebannergdpr.cloudfunctions.net, www.googletagmanager.com, www.google-analytics.com
dataLayer events seen
gdprconsent, gtm.js, gtm.dom, gtm.load, gtm.click, gdprclosepopin, gtm.linkClick
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on opel.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.
No findings were raised for this container.
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 »
No third-party hosts were found in this container's tags.
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-T37F5BH |
|---|---|
| Published version | 9 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 13:32:14 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-T37F5BH |
| Body checksum | e4a77ed5131c2557d64772e9d93dce0097a4417b3d0e5e96a159ec36b08fe714Evidence 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 »