container audit

GTM-P5VBCKG

5 tags, no hand-written scripts, 2 third-party hosts — smaller than 83% of the 46,522 containers we have measured, and carrying none of the hand-written JavaScript most of them do.

2 third-party hosts reachable from its tags.
duplicate-ads-conversion is uncommon — under 4% 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.

Tags5

Custom scripts0

Third parties2

Delivered429 KB

Versions3

What we observed

A real browser loaded buymitchell1.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 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 9 hosts — static.cloudflareinsights.com, hostedusa6.whoson.com, www.googletagmanager.com, www.google-analytics.com, www.google.com, ad.doubleclick.net, analytics.google.com, stats.g.doubleclick.net, and 1 more

dataLayer events seen gtm.js, gtm.dom, gtm.scrollDepth, gtm.load

Where the data goes

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

reviewUniversal Analytics tags still shipped (1)

1 Universal Analytics tag is 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

reviewSame Google Ads conversion defined more than once (1)

1 conversion action is defined by more than one tag.

WhyA conversion ID plus label identifies one action. Two tags carrying the same pair can report the same conversion twice, inflating conversion counts and the ROAS that bidding runs on.

CheckCheck whether both tags can fire on the same page. If they can, your Ads reporting is overstating this action and automated bidding is optimising against it.

Seenseen in 3.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 »

www.googleadservices.com ×3 www.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.

buymitchell1.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-P5VBCKG`
Published version	`3` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 17:59:53 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-P5VBCKG`
Body checksum	`b760bcf9840f4e64fc470b07a9b7e1239b3d938c1c837baacbd7edde505d8591` 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-P5VBCKG

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 »