clean baseline
No provable problems in the tracking we verified on this page today — this is your baseline.
That’s what we observed externally on one page load, not a certification of your whole setup.
Anonymized scan report: verified clean
[ site withheld ]
Anonymized, based on an actual report — the one behind the verified-clean study. The site’s address and every vendor identifier are withheld. The substantive result, passing checks, inventory, consent evidence, and coverage limit are unchanged — all four checks and every inventory row are what the report actually carries. A live report also has a share link and a watch opt-in, which a static copy cannot.
Summary
| Result | No problems proven in the scoped checks. |
|---|---|
| Verified | No duplicate GA4 pageview counting · No conflicting Meta or TikTok pixel IDs · No legacy Universal Analytics, retired Adobe DTM, or orphaned GA4/Meta loaders, and 1 more. |
| Observed | 15 vendor-and-ID rows across 10 vendor families. |
| Scope | An external scan of one observed page load from the public internet, as a visitor would see it — it verifies what fired in the browser, not the contents of the GTM container, GA4 settings, or server-side tagging. |
This page’s tracking verified clean today, and a baseline holds only until the next deploy, plugin update, or GTM publish. On a live report, this is where you would opt in to a watch so a later scan reports the next change.
What we found
What we verified
Your receipt: the checks that passed on this page today. Share it with a client or teammate as proof of a clean baseline.
- Each GA4 measurement ID was sent exactly one
page_viewbeacon on this load. - Each supported ad platform fired under a single visible pixel ID, so its data is not split across duplicate pixels.
- No Universal Analytics, retired Adobe DTM, or orphaned GA4/Meta loaders were observed.
- No consent banner was detected from our US scan region.
What we observed loading
The analytics and ad tools we recognized loading on this page.
| Vendor | ID | Behavior | Requests |
|---|---|---|---|
| Amazon Ads | — | loads | 3 |
| GA4 | G-•••••••• | 1 collect hit | 1 |
| GA4 | G-•••••••• | 1 collect hit | 1 |
| GA4 | G-•••••••• | loads and fires | 3 |
| GTM | GTM-•••••••• | loads | 1 |
| Google Ads | AW-•••••••• | loads and fires | 2 |
| Google Ads | AW-•••••••• | 2 pixel fires | 2 |
| Hotjar | •••••••• | loads | 1 |
| Meta | — | loads and fires | 5 |
| Microsoft UET | — | loads | 1 |
| Microsoft UET | •••••••• | 1 collect hit | 1 |
•••••••• | 10 collect hits | 10 | |
| Reddit Pixel | — | loads | 1 |
| Reddit Pixel | •••••••• | 1 pixel fire | 1 |
| TikTok | •••••••• | loads | 1 |
Three GA4 rows are three distinct measurement IDs, each sent the pageview exactly once — which is why the duplicate check passes. Paired rows for a vendor are a loader and a fire attributed separately.
Consent signals on the wire
Scanned from our US region, so this records what was visible and what was on the wire for consent mechanics on this page. It is not a legal compliance verdict.
What this scan could not see
- This is an external observation of one page load. It cannot see your GTM container contents, GA4 property settings, or server-side tagging.
The study this report backs: measurement verified clean on an e-commerce homepage.
The opposite outcome: an anonymized report with two findings.
See what a report says about a site you manage: run a free scan.
Report run: July 20, 2026