What this checker detects
A compact view of analytics, tags and conversion signals
- 01
Read public tracking evidence
The checker securely fetches one public HTML page and inspects active script, iframe, image and initialization patterns.
- 02
Separate signals from assumptions
Detected IDs and methods are reported from source evidence. Runtime-only and consent-delayed tracking remains clearly qualified.
- 03
Prioritize practical checks
Five deterministic categories surface only the highest-value issues and quick wins, with technical evidence collapsed by default.
GA4 vs GTM
GA4 is an analytics property. GTM is a container that can deliver GA4 and other tags. A GTM signal alone does not prove GA4 exists inside the container.
Why duplicate tracking matters
Repeated initialization can create measurement risk, but source evidence alone cannot prove that duplicate events fired. The checker flags only potential duplication for review.
Consent-delayed tracking
Consent platforms can release tags after a visitor choice. When consent tooling appears without tracker source signals, the report qualifies the result as possibly delayed.
Static evidence has clear limits
The checker does not execute arbitrary page JavaScript or observe network events. It cannot prove that events fired, consent is legally compliant, or tags absent from the fetched source are not loaded later.