container audit
GTM-5WWV6RL
This container ships 100 hand-written scripts (68 KB of JavaScript) to every visitor — more than 98% of the 46,522 containers we have measured. That is an application's worth of code, delivered as tag configuration.
- 379 published versions — each one live for every visitor the moment it was published.
Tags300
Custom scripts100
Third parties13
Delivered765 KB
Versions379
What we observed
A real browser loaded opel.de 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
opelvauxhall-g10-server-side-tagging-prod-406671236336.europe-west9.run.app — 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 — read from the measurement id, not the hostname
Consent
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 1 fired afterwards. That is the outcome consent is meant to produce. 10 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — rum.hlx.page, schema.milestoneinternet.com, ressource.gdpr-banner.awsmpsa.com, cdn-eu.dynamicyield.com, st-eu.dynamicyield.com, api.gdpr-banner.awsmpsa.com, europe-west1-cookiebannergdpr.cloudfunctions.net, api2.gdpr-banner.awsmpsa.com, and 17 more
dataLayer events seen
dyuaevent, gdprconsent, gtm.js, gtm.dom, gtm.load, gdprclosepopin
Where the data goes
Confirmed — a browser watched this site send measurement data to opelvauxhall-g10-server-side-tagging-prod-406671236336.europe-west9.run.app, not to Google. observed on opel.de 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 (3)
3 pieces 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 (3)
3 pieces 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
infoOne variable that a great deal depends on (56)
"virtualPageURL" is read by 56 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 (21)
21 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
infoUses browser storage (8)
8 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 (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 »
fls.doubleclick.net ×109www.googleadservices.com ×12d.adup-tech.com ×6www.opel.de ×5s.d.adup-tech.com ×3www.google-analytics.com ×3insight.adsrvr.org ×2js.adsrvr.org ×2a.twiago.com ×1cdn.twiago.com ×1p.teads.tv ×1pubads.g.doubleclick.net ×1secure.adnxs.com ×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-5WWV6RL |
|---|---|
| Published version | 379 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:33:37 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-5WWV6RL |
| Body checksum | 8f2b8ad15fb20054c5be91e7d380cf07e98d14918110f96a23e349f65c4ed0bfEvidence 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 »