container audit
GTM-WJZTZ9M
54 tags, 0 custom scripts, 0 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
Tags54
Custom scripts0
Third parties0
Delivered369 KB
Versions150
What we observed
A real browser loaded pagro.at 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
tms.pagro.at — the site's own host, and googletagmanager.comMeasurement sent to
tms.pagro.at — not GoogleMeasurement runs through the site's own infrastructure. Part of the tag library still comes from Google, which is normal — the two are loaded separately.
Forwarded to
GA4 ×4 — read from the measurement id, not the hostname
Consent
Usercentrics answered its own API. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 4 fired afterwards. That is the outcome consent is meant to produce. 10 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
24 hosts — js.sitesearch360.com, integrations.etrusted.com, maps.googleapis.com, cdn.mth.group, web.cmp.usercentrics.eu, cdn.sitesearch360.com, www.googletagmanager.com, v1.api.service.cmp.usercentrics.eu, and 16 more
dataLayer events seen
db.consent-ready, gtm.js, db.pageview, consent_status, gtm.dom, gtm.load, db.pageview_without_items
Where the data goes
Confirmed — a browser watched this site send measurement data to tms.pagro.at, not to Google. observed on pagro.at 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 (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
infoConsent configuration detected (1)
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 »
No third-party hosts were found in this container's tags.
Detected 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-WJZTZ9M |
|---|---|
| Published version | 150 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:19:18 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-WJZTZ9M |
| Body checksum | c54174cf87087fd6da96a3b11c3d216fcc627c12cfb387714c77fd21625ffaf5Evidence 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 »