tagora
container audit

GTM-K4QQCRJ3

This container is published but empty — no tags, so nothing fires.

Tags0
Custom scripts0
Third parties0
Delivered315 KB
Versions1

What we observed

A real browser loaded newstribune.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 — Google
Measurement sent to google-analytics.com — Google
Consent Quantcast answered its own API. 1 measurement hit 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=G1 (no consent signal). 5 advertising hosts were contacted before anything was granted.
Third parties contacted 25 hosts — wehco-files.nyc3.cdn.digitaloceanspaces.com, cmp.osano.com, wehco.media.clients.ellingtoncms.com, faughnmedia.media.clients.ellingtoncms.com, sdk.mrf.io, securepubads.g.doubleclick.net, discovery.evvnt.com, www.googletagmanager.com, and 17 more
dataLayer events seen dataLayer-loaded, gtm.js, gtm.dom, gtm.load

Where the data goes

Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on newstribune.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.

No findings were raised for this container.

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.

newstribune.com

What this audit describes

Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.

ContainerGTM-K4QQCRJ3
Published version1 — the identity of this configuration. It changes only when someone publishes.
Read at2026-08-13 09:14:11 UTC (a month ago)
Sourcehttps://www.googletagmanager.com/gtm.js?id=GTM-K4QQCRJ3
Body checksum10246ba8040cf6455283634d71d48902943212b54d7840640e436941e3fdb443
Evidence 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.

Re-audit GTM-K4QQCRJ3

Check another container

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 »