container audit
GTM-K8Z9D4F
18 tags, 12 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 12 custom HTML tags carrying 35 KB of JavaScript. This runs on every page the container loads on.
- 1 third-party host reachable from its tags.
- 434 published versions — each one live for every visitor the moment it was published.
inner-htmlis 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.
Tags18
Custom scripts12
Third parties1
Delivered424 KB
Versions434
What we observed
A real browser loaded landrover.com 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
tags.landrover.com — 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 ×2 — read from the measurement id, not the hostname
Consent
OneTrust answered its own API. 2 measurement hits left the page before it was granted, carrying a client id (whether that is permitted depends on jurisdiction, and this was not a European visit). 2 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted). 6 advertising hosts were contacted before anything was granted.Third parties contacted
25 hosts — modules.jaguarlandrover.com, rum.hlx.page, www.googletagmanager.com, unpkg.com, cdn.cookielaw.org, geolocation.onetrust.com, cdn.rudderlabs.com, www.jaguarlandrover.com, and 17 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, GDPR Pref Allows Cats 1,2,3,4, Core RS Setup Complete, setNameplate, jlr-at-library-loaded, gtm.timer, RS onLoaded
Where the data goes
Confirmed — a browser watched this site send measurement data to tags.landrover.com, not to Google. observed on landrover.com 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
reviewWrites innerHTML (1)
1 piece 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
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
infoConsent configuration detected (2)
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 »
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_NF7PV gallery injects code from unpkg.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-K8Z9D4F |
|---|---|
| Published version | 434 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-11 20:54:54 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-K8Z9D4F |
| Body checksum | c3d666046b28b42500a15e2821411c1198810bc3a4d886014045fcd40f1b7db2Evidence 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 »