tagora
container audit

GTM-MPL87MNV

This container is published but empty — no tags, so nothing fires.

Tags0
Custom scripts0
Third parties0
Delivered367 KB
Versions6

What we observed

A real browser loaded fiat.com.tr 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 cmesc46g30008uxv1usqkonpx-signal.usehardal.com — not Google, at /sgtm/g/collect

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 ×4 — read from the measurement id, not the hostname
Consent no consent gate responded on this page, so there was nothing to hold measurement back (banners are often shown only to visitors in certain regions, and this was not a European visit). 1 host appeared only after consent was granted. Google recorded gcs=G111 (all granted).
Third parties contacted 25 hosts — schema.milestoneinternet.com, cookielaw.emea.fcagroup.com, code.jquery.com, assets.adobedtm.com, livechatwidget-vega2.next4biz.net, www.googletagmanager.com, app.11sight.com, cmesc46g30008uxv1usqkonpx-signal.usehardal.com, and 17 more
dataLayer events seen gtm.js, gtm.dom, gtm.load

Where the data goes

Confirmed — a browser watched this site send measurement data to cmesc46g30008uxv1usqkonpx-signal.usehardal.com, not to Google. observed on fiat.com.tr 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.

infoUses browser storage (1)
1 piece 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 »

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.

fiat.com.tr

What this audit describes

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

ContainerGTM-MPL87MNV
Published version6 — the identity of this configuration. It changes only when someone publishes.
Read at2026-08-22 14:03:00 UTC (a month ago)
Sourcehttps://www.googletagmanager.com/gtm.js?id=GTM-MPL87MNV
Body checksumadd3616594b0d99fac86b852fdeab269f82f49f9128ff0df4ee31b605c0857c7
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-MPL87MNV

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 »