container audit
GTM-TNPWVM3S
578 tags, 782 KB delivered to every visitor — more than 98% of the 46,522 containers we have measured. Size is a description here, not a fault.
- 1 custom HTML tag carrying 6 KB of JavaScript. This runs on every page the container loads on.
- 890 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.
Tags578
Custom scripts1
Third parties0
Delivered782 KB
Versions890
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 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
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
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.
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_192855232_4 private runs page-level globalsDetected 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-TNPWVM3S |
|---|---|
| Published version | 890 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 13:35:48 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TNPWVM3S |
| Body checksum | 7bd21e444154e1425898878c7ed39a44b17904d1264cbc7ed363004ded6b6e6cEvidence 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 »