tagora
container audit

GTM-K9RBBWF

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

Tags2
Custom scripts1
Third parties3
Delivered345 KB
Versions4

What we observed

A real browser loaded kossev.info 2 months 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 no consent gate responded on this page, so there was nothing to hold measurement back (banners are often shown only to visitors in certain regions, and this was not a European visit).
Third parties contacted 7 hosts — fonts.googleapis.com, static.cloudflareinsights.com, rs.adocean.pl, www.googletagmanager.com, analytics.google.com, stats.g.doubleclick.net, www.google.co.il
dataLayer events seen 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 kossev.info 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.

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

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 »

d7d3cf2e81d293050033-3dfc0615b0fd7b49143049256703bfce.ssl.cf1.rackcdn.com ×1t.contentinsights.com ×1www.google-analytics.com ×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.

kossev.info

What this audit describes

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

ContainerGTM-K9RBBWF
Published version4 — the identity of this configuration. It changes only when someone publishes.
Read at2026-08-23 17:36:52 UTC (2 months ago)
Sourcehttps://www.googletagmanager.com/gtm.js?id=GTM-K9RBBWF
Body checksumc65626229791015d912f30c1a14ea58bbe07ded7fc05cbcec854468009811e3b
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 2 months 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-K9RBBWF

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 »