container audit

GTM-PSVT7V2

This container ships 133 hand-written scripts (145 KB of JavaScript) to every visitor — more than 99% of the 46,522 containers we have measured. That is an application's worth of code, delivered as tag configuration.

Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
inner-html is 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.

Tags215

Custom scripts133

Third parties22

Delivered780 KB

Versions209

What we observed

A real browser loaded renault.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 odc.renault.de — the site's own host, and googletagmanager.com

Measurement sent to odc.renault.de — not Google

Measurement 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 — 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 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 — cdn.group.renault.com, cdn.cookielaw.org, www.googletagmanager.com, geolocation.onetrust.com, c.amazon-adsystem.com, mpglwmz8sx.kameleoon.eu, privacyportal-fr.onetrust.com, t.screeb.app, and 17 more

dataLayer events seen 55experience_pageChange, gtm.js, OneTrustLoaded, OptanonLoaded, gtm.dom, gtm.load, ccClose, ccFinished

Where the data goes

Confirmed — a browser watched this site send measurement data to odc.renault.de, not to Google. observed on renault.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.

reviewWrites cookies directly (16)

16 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

reviewdocument.write (10)

10 pieces of custom code call document.write.

Whydocument.write blocks the HTML parser while it runs, and browsers ignore it entirely once the page has finished parsing — so an async-loaded tag using it can silently do nothing.

CheckIf these tags fire on page load they are costing render time; if they fire later they may not be working at all. Worth confirming the tag still does what it was added to do.

Seenseen in 18.4% of 46,522 containers measured

reviewHardcoded http:// URL (7)

7 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 innerHTML (2)

2 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

infoLoads JavaScript from another host (43)

43 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

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_579DB gallery runs page-level globals

__cvt_KT4F4 gallery injects code from c.amazon-adsystem.com · runs page-level globals

__cvt_KT9RV gallery injects code from dynamic.criteo.com

__cvt_PBGZL gallery injects code from www.redditstatic.com · runs page-level globals

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.

renault.de

What this audit describes

Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.

Container	`GTM-PSVT7V2`
Published version	`209` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 18:05:03 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-PSVT7V2`
Body checksum	`de37c0671225e919214b4fe615a34bfa6121171a3ebe9bfc40f29b889dc27906` Evidence 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.

Re-audit GTM-PSVT7V2

Check another container

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 »