container audit
GTM-NDLWJTT
55 tags, 18 custom scripts, 6 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 18 custom HTML tags carrying 29 KB of JavaScript — more than 70% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 6 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.
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.
Tags55
Custom scripts18
Third parties6
Delivered541 KB
Versions118
What we observed
A real browser loaded pdf-suite.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
cloud.pdf-suite.com — the site's own host, and googletagmanager.comMeasurement sent to
cloud.pdf-suite.com — 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 ×3 — read from the measurement id, not the hostname
Consent
OneTrust answered its own API. Measurement fired beforehand but carried no identifier —
analytics_storage was denied, which is Consent Mode working as designed rather than a gap. no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision. Google recorded gcs=G100 (all denied).Third parties contacted
21 hosts — avqtools.avanquest.com, avqservice.avanquest.com, avqgate.avanquest.com, qti.avanquest.com, gate.upclick.com, cdn.cookielaw.org, bzrcdn.openai.com, www.googletagmanager.com, and 13 more
dataLayer events seen
gtm.js, visitor ID ready, session ready, avqTools ready, gtm.dom, avquid is ready, OneTrustLoaded, OptanonLoaded, gtm.load
Where the data goes
Confirmed — a browser watched this site send measurement data to cloud.pdf-suite.com, not to Google. observed on pdf-suite.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 (3)
3 pieces 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
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
infoLoads JavaScript from another host (7)
7 pieces 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
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 »
static.ada.support ×3www.clarity.ms ×2bzrcdn.openai.com ×1cdn.cookielaw.org ×1cdn.livechatinc.com ×1static.zdassets.com ×1
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_K8HMJ gallery 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-NDLWJTT |
|---|---|
| Published version | 118 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 13:22:52 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-NDLWJTT |
| Body checksum | a97526474819f7c7840ffa99fa885c3dd9bacd196b76d29b763d24de2aec8827Evidence 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 »