container audit

GTM-5BF3GL2

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

Tags21

Custom scripts0

Third parties1

Delivered397 KB

Versions24

What we observed

A real browser loaded ricoh.co.jp 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 13 hosts — ce.mf.marsflag.com, apis.google.com, www.googletagmanager.com, content.googleapis.com, img03.en25.com, www.google.com, ad.doubleclick.net, googleads.g.doubleclick.net, and 5 more

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

Where the data goes

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

G-1W7QW96RNV 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

infoConsent configuration detected (1)

The container declares one or more consent signals.

WhyConsent handling is present in the container. This describes what the artifact declares; what actually happened on the page is measured separately, above.

CheckConfirm these settings match the consent policy you intend to enforce, and compare them with the before-and-after observation.

Seenseen in 44.6% 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 ×20

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.

ricoh.co.jp ricoh.jp

What this audit describes

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

Container	`GTM-5BF3GL2`
Published version	`24` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-22 09:48:31 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-5BF3GL2`
Body checksum	`97c74028d84118584f59c490b4eeb72e4023760b336995732dc24327b5b281bc` 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-5BF3GL2

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 »