container audit
GTM-KR523KZ
316 tags, 741 KB delivered to every visitor — more than 90% of the 46,522 containers we have measured. Size is a description here, not a fault.
- 32 custom HTML tags carrying 30 KB of JavaScript — more than 80% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 2 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.
- 510 published versions — each one live for every visitor the moment it was published.
Tags316
Custom scripts32
Third parties2
Delivered741 KB
Versions510
What we observed
A real browser loaded pulsz.com 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
google-analytics.com — GoogleConsent
OneTrust answered its own API. 5 hosts appeared only after consent was granted. Google recorded
gcs=G100 (all denied).Third parties contacted
25 hosts — storage.googleapis.com, cdn.builder.io, pulsz-landing.vercel.app, cdn.cookielaw.org, fonts.gstatic.com, www.googletagmanager.com, geolocation.onetrust.com, cdn.jsdelivr.net, and 17 more
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on pulsz.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.
infoUses browser storage (11)
11 pieces 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
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
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_KDZQ6 gallery injects code from x.cloudfront.net, storage.googleapis.com, cdn.jsdelivr.net, unpkg.com · runs page-level globals__cvt_30701258_1114 private injects code from d32tdr35c4icxo.cloudfront.net · runs page-level globals__cvt_30701258_286 private injects code from cdn.taboola.com__cvt_30701258_346 private injects code from s.yimg.com · runs page-level globals__cvt_K4VXG gallery injects code from sc-static.net, tr.snapchat.com · runs page-level globals__cvt_K8HMJ gallery runs page-level globals__cvt_M6QSS gallery injects code from x.tgtag.io · runs page-level globals__cvt_PBGZL gallery injects code from www.redditstatic.com · 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-KR523KZ |
|---|---|
| Published version | 510 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:40:26 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-KR523KZ |
| Body checksum | 9b859b8169635f1275785c22b6f1ce08ba5d0cf21b4c0a0baf082e54a00c9b40Evidence 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 »