container audit
GTM-5W8WVVM
68 tags, 11 custom scripts, 5 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 11 custom HTML tags carrying 6 KB of JavaScript. This runs on every page the container loads on.
- 5 third-party hosts reachable from its tags.
- Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
- 360 published versions — each one live for every visitor the moment it was published.
duplicate-ga4-configis uncommon — under 5% 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.
Tags68
Custom scripts11
Third parties5
Delivered594 KB
Versions360
What we observed
A real browser loaded hardloop.fr 2 months 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
metrics.hardloop.fr — 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 ×5 — read from the measurement id, not the hostname
Consent
Didomi answered its own API. 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
25 hosts — img.hardloop.com, apis.google.com, assets.calendly.com, www.dwin1.com, invitejs.trustpilot.com, lantern.roeyecdn.com, lantern.roeye.com, www.googletagmanager.com, and 17 more
dataLayer events seen
Next.js-hydration, FCP, TTFB, didomi-consent, didomi-ready, gtm.js, page_view, gtm.dom, gtm.load, didomi-cookies-consent, didomi-consent-changed, gtm.triggerGroup
Where the data goes
Confirmed — a browser watched this site send measurement data to metrics.hardloop.fr, not to Google. observed on hardloop.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.
reviewdocument.write (1)
1 piece 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
reviewSame GA4 property configured more than once (1)
G-5FMWHPEQ7B is configured by 2 separate tags.
WhyEach config tag initialises the property independently, so a single page view can be counted once per tag. Sessions, users and conversion rates all inherit the error.
CheckIf more than one of these fires on the same page you are double-counting. Compare against a known-good day, or check for a step change in traffic when the second tag was added.
Seenseen in 4.8% of 46,522 containers measured
infoConsent configuration detected (4)
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
infoLoads JavaScript from another host (2)
2 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 »
www-ads.gembiratech.com ×2a.omappapi.com ×1connect.facebook.net ×1sibautomation.com ×1tbs.tradedoubler.com ×1
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_MJP6G gallery injects code from x.didomi.io, x.privacy-center.org · runs page-level globals__cvt_40991253_1629 private runs page-level globals__cvt_579DB gallery runs page-level globals__cvt_KT9RV gallery injects code from dynamic.criteo.comDetected 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-5W8WVVM |
|---|---|
| Published version | 360 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:33:20 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-5W8WVVM |
| Body checksum | 7db9e4780f25c06a52dc94c4559d19fc1af063ae52f7a406039f9ed2abb0f606Evidence 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 2 months 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 »