container audit
GTM-TRZFQ4N
77 tags, 0 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 1 third-party host reachable from its tags.
Tags77
Custom scripts0
Third parties1
Delivered556 KB
Versions268
What we observed
A real browser loaded cch.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
www.wolterskluwer.com — the site's own host, at /GTM-55QQCTWV/gtm.js rather than the default path, and googletagmanager.comMeasurement sent to
www.wolterskluwer.com — not Google, at /GTM-55QQCTWV/ag/g/cMeasurement 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
OneTrust 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
19 hosts — cdn.wolterskluwer.io, www.wolterskluwer.com, fonts.googleapis.com, assets.contenthub.wolterskluwer.com, cdn.cookielaw.org, geolocation.onetrust.com, privacyportal-de.onetrust.com, cdn.debugbear.com, and 11 more
dataLayer events seen
OneTrustLoaded, OptanonLoaded, gtm.js, gtm.dom, gtm.load, gtm.triggerGroup
Where the data goes
Confirmed — a browser watched this site send measurement data to www.wolterskluwer.com, not to Google. observed on cch.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.
infoOne variable that a great deal depends on (48)
"eventLabel" is read by 48 tags and triggers — more than anything else in this container.
WhyGTM shows you where a variable is defined, never how much depends on it. Editing this one touches a large share of the container at once, and whatever breaks will surface somewhere that looks unrelated to the change.
CheckBefore changing it, check what reads it. If it feeds both measurement and consent or routing logic, split those uses apart first.
Seenseen in 10.1% 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 »
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-TRZFQ4N |
|---|---|
| Published version | 268 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 10:45:11 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TRZFQ4N |
| Body checksum | 2df19d6e571a756c8c749ae22f3166b1bb558d07f3d5dce737c095d1d23a4605Evidence 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 »