container audit

GTM-N3LRFH

15 tags, 3 custom scripts, 3 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).

3 custom HTML tags carrying 2 KB of JavaScript. This runs on every page the container loads on.
3 third-party hosts reachable from its tags.

Tags15

Custom scripts3

Third parties3

Delivered373 KB

Versions15

What we observed

A real browser loaded eagletribune.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 a consent banner was present and we accepted it. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 10 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 25 hosts — bloximages.chicago2.vip.townnews.com, www.google.com, cmp.osano.com, fonts.googleapis.com, a.pub.network, static.cnhionline.com, www.gstatic.com, eagletribune-cnhi-pw.newsmemory.com, and 17 more

dataLayer events seen tncms.start, 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 eagletribune.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.

reviewUniversal Analytics tags still shipped (8)

8 Universal Analytics tags are still in the container.

WhyUniversal Analytics stopped processing data in July 2023. These tags still download and execute on every matching page, and send to an endpoint that discards them.

CheckNothing is being collected from these. Confirm the equivalent GA4 tag exists, then delete them.

Seenseen in 23.2% of 46,522 containers measured

reviewHardcoded http:// URL (1)

1 piece of custom code reference a plain http:// address.

WhyOn an https:// page the browser blocks or upgrades these. Blocked means the tag quietly stops working; upgraded only works if that host also serves https.

CheckCheck whether the hosts below still respond over https, and update the URLs.

Seenseen in 12.8% of 46,522 containers measured

infoLoads JavaScript from another host (2)

2 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 (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 »

www.google-analytics.com ×4 edge ×1 secure ×1

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.

eagletribune.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-N3LRFH`
Published version	`15` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-13 11:46:15 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-N3LRFH`
Body checksum	`97a567673ca42172d211f0bfc1521b6c59b356a5aaa474d4f5e5ddc28cb560a7` 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-N3LRFH

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 »