container audit

GTM-K3TH4CC

54 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.

Tags54

Custom scripts0

Third parties1

Delivered421 KB

Versions30

What we observed

A real browser loaded southland.org 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 platform is present, but our browser could not complete the accept step — so the before-and-after comparison did not run here. Google recorded gcs=G111 (all granted).

Third parties contacted 20 hosts — transcend-cdn.com, dbukjj6eu5tsf.cloudfront.net, fonts.sidearmsports.com, cdnjs.cloudflare.com, www.googletagmanager.com, www.google-analytics.com, connect.facebook.net, sb.scorecardresearch.com, and 12 more

dataLayer events seen dataLayerLoaded, 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 southland.org 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.

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

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 ×51

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-K3TH4CC`
Published version	`30` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-11 20:54:40 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-K3TH4CC`
Body checksum	`9206653fd0c47aa590291712e34f902e429b104aeba53b30a814b1086b8860e9` 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-K3TH4CC

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 »