container audit
GTM-PWWZSH
29 tags, 5 custom scripts, 2 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 5 custom HTML tags carrying 18 KB of JavaScript. This runs on every page the container loads on.
- 2 third-party hosts reachable from its tags.
Tags29
Custom scripts5
Third parties2
Delivered389 KB
Versions127
What we observed
A real browser loaded itprotoday.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 — GoogleConsent
Quantcast answered its own API. 3 measurement hits left the page before it was granted, carrying a client id (whether that is permitted depends on jurisdiction, and this was not a European visit). no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision. Google recorded
gcs=G111 (all granted). 2 advertising hosts were contacted before anything was granted.Third parties contacted
25 hosts — static.cloudflareinsights.com, www.techtarget.com, cdn.ttgtmedia.com, optimizely.techtarget.com, consent.techtarget.com, pub.doubleverify.com, www.googletagmanager.com, go.techtarget.com, and 17 more
dataLayer events seen
gtm.js, techtarget-sourcepoint-consent-ga, DriftEnabled, LinkedInInsightEnabled, GaEnabled, gtm.dom, gtm.load, gtm.triggerGroup
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on itprotoday.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 cookies directly (3)
3 pieces 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
reviewdocument.write (1)
1 piece of custom code call document.write.
Whydocument.write blocks the HTML parser while it runs, and browsers ignore it entirely once the page has finished parsing — so an async-loaded tag using it can silently do nothing.
CheckIf these tags fire on page load they are costing render time; if they fire later they may not be working at all. Worth confirming the tag still does what it was added to do.
Seenseen in 18.4% 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 (2)
2 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
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.
windowsitpro.comtheserverside.comnetworkcomputing.comdatasciencecentral.comwinsupersite.comitprotoday.comtechtarget.comhealthitsecurity.comlemagit.frcomputerweekly.com
What this audit describes
Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.
| Container | GTM-PWWZSH |
|---|---|
| Published version | 127 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-12 22:46:45 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-PWWZSH |
| Body checksum | 97417ca3999d5e349ae91e7513f3be06656064ce89178a3260051105d71ac30cEvidence 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 »