container audit
GTM-KTCL6ZR
16 tags, 5 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 5 custom HTML tags carrying 8 KB of JavaScript. This runs on every page the container loads on.
- 1 third-party host reachable from its tags.
- 736 published versions — each one live for every visitor the moment it was published.
Tags16
Custom scripts5
Third parties1
Delivered363 KB
Versions736
What we observed
A real browser loaded hertz.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
google-analytics.com — GoogleThird parties contacted
21 hosts — api.mqcdn.com, fonts.googleapis.com, js.stripe.com, analytics.google.com, www.google.com, cdn-prod.eu.securiti.ai, assets.adobedtm.com, www.googletagservices.com, and 13 more
dataLayer events seen
gtm.js, headerFooterReady, gtm.dom, gtm.pageError, gtm.load
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on hertz.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.
reviewWrites cookies directly (1)
1 piece 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
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
infoLoads JavaScript from another host (1)
1 piece 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
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 »
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_39391016_3716 private runs page-level globals__cvt_39391016_3706 private injects code from ecom.mss.hertz.io, ecom.nonprod.mss.hertz.ioDetected 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-KTCL6ZR |
|---|---|
| Published version | 736 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-12 22:26:13 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-KTCL6ZR |
| Body checksum | b15808dfa47dfdd10f1946d22fd5e84102dbeea8dfe8732c9ec9575ccbc9c795Evidence 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 »