container audit

GTM-WWCS47

This container ships 43 hand-written scripts (39 KB of JavaScript) to every visitor — more than 90% of the 46,522 containers we have measured. That is an application's worth of code, delivered as tag configuration.

5 third-party hosts reachable from its tags.
1,073 published versions — each one live for every visitor the moment it was published.
duplicate-ga4-config is uncommon — under 5% of the containers we have measured have it. That is context rather than a verdict: a server container is rarer still and is a sign of a mature setup. What it means is in the finding itself.

Tags62

Custom scripts43

Third parties5

Delivered540 KB

Versions1073

What we observed

A real browser loaded e-fellows.net 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 www.e-fellows.net — the site's own host

Measurement sent to google-analytics.com — Google

The container is self-hosted; the measurement still goes to Google. The first-party path that a tagging server provides is not being used for the data itself.

Third parties contacted 1 host — cloud.ccm19.de

dataLayer events seen gtm.js, page_view, TMSHelperReady, gtm.dom, gtm.load, jQuery_ready

Where the data goes

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

reviewSame GA4 property configured more than once (1)

AW-1033317700 is configured by 2 separate tags.

WhyEach config tag initialises the property independently, so a single page view can be counted once per tag. Sessions, users and conversion rates all inherit the error.

CheckIf more than one of these fires on the same page you are double-counting. Compare against a known-good day, or check for a step change in traffic when the second tag was added.

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

infoUses browser storage (2)

2 pieces of custom code read or write localStorage or sessionStorage.

WhyBrowser storage persists across visits and is not covered by cookie consent tooling, so it is easy to overlook when auditing what you keep on a visitor's device.

CheckConfirm nothing personal is being kept there, and that it is covered by your privacy notice.

Seenseen in 23.3% 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.googleadservices.com ×7 air.jobiqo.com ×2 www.google-analytics.com ×2 app.varify.io ×1 cdn.leadinfo.net ×1

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_545271_863 private injects code from x.piwik.pro · runs page-level globals

__cvt_5RM3Q gallery injects code from connect.facebook.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.

e-fellows.net

What this audit describes

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

Container	`GTM-WWCS47`
Published version	`1073` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 18:22:25 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-WWCS47`
Body checksum	`c482691626278d99619f56210e34e621daa2f11d216525e00aa090ebf3808ed7` 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-WWCS47

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 »