container audit

GTM-MWNVK59

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

Tags55

Custom scripts0

Third parties1

Delivered410 KB

Versions24

What we observed

A real browser loaded line.games 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 — www.google-analytics.com, www.googletagmanager.com, connect.facebook.net, www.google.com, analytics.google.com, www.google.co.il, stats.g.doubleclick.net

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 line.games 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

infoOne variable that a great deal depends on (47)

"user_id" is read by 47 tags and triggers — more than anything else in this container.

WhyGTM shows you where a variable is defined, never how much depends on it. Editing this one touches a large share of the container at once, and whatever breaks will surface somewhere that looks unrelated to the change.

CheckBefore changing it, check what reads it. If it feeds both measurement and consent or routing logic, split those uses apart first.

Seenseen in 10.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

What the custom templates can do

Custom templates are third-party code shipped inside the container. Injecting scripts and running page globals is ordinary for them — most tag templates need it to work — so this is an inventory, not a warning. It lists the capability each template declares so you can match it against templates you meant to install.

__cvt_51161261_42 private injects code from connect.facebook.net · runs page-level globals

__cvt_51161261_43 private injects code from t1.daumcdn.net · runs page-level globals

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.

line.games

What this audit describes

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

Container	`GTM-MWNVK59`
Published version	`24` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 17:50:01 UTC (2 months ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-MWNVK59`
Body checksum	`c1dcc234bf74ac2547f6ea3275104a31bcd514041455cac0bda4f7815c3fc5ff` 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-MWNVK59

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 »