container audit

GTM-5XQXSCLC

37 tags, 0 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).

1 third-party host reachable from its tags.

Tags37

Custom scripts0

Third parties1

Delivered417 KB

Versions8

What we observed

A real browser loaded peugeot.fr 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 — Google

Measurement sent to peugeot-g10-server-side-tagging-prod-406671236336.europe-west9.run.app — not Google

Measurement 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 ×8 — read from the measurement id, not the hostname

Consent 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. 2 hosts appeared only after consent was granted. Google recorded gcs=G100 (all denied).

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 gdprconsent, gtm.js, gtm.dom, gtm.load, gtm.click, gdprclosepopin, gtm.linkClick, gtm.timer

Where the data goes

Confirmed — a browser watched this site send measurement data to peugeot-g10-server-side-tagging-prod-406671236336.europe-west9.run.app, not to Google. observed on peugeot.fr 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.

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

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.google-analytics.com ×37

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.

peugeot.fr

What this audit describes

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

Container	`GTM-5XQXSCLC`
Published version	`8` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-22 09:53:16 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-5XQXSCLC`
Body checksum	`33097aae88103d16897862121bf6d2deac9a87204a89196b318b0772375e6dc9` 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-5XQXSCLC

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 »