Free tools to check your ecommerce tracking
Real browser scans of your store. Every issue comes with a plain explanation and a fix you can apply today.
Pick a tool
Three scans of your live store and two tools that run entirely in your browser.
-
Full report
Website tracking checker
A real browser scan of your store: tags, server-side signal, Safari cookie lifetimes, consent and ad blockers, with a fix for every issue.
Open tool -
Meta report
Meta Pixel and CAPI checker
Find duplicate pixels, missing ViewContent, missing event_id for deduplication and short-lived _fbp and _fbc cookies.
Open tool -
Consent report
Consent Mode v2 checker
See what your tags send before any click and after Reject, and whether Google tags carry the Consent Mode v2 signals.
Open tool -
Runs in your browser
CAPI deduplication checker
Paste a browser pixel event and a server event and see whether Meta, TikTok, Pinterest or Reddit will deduplicate them.
Open tool -
Runs in your browser
UTM builder
Build UTM tracking templates with the right dynamic macros for Facebook, Google, TikTok and Reddit ads.
Open tool
How the scanner works
-
We open your store in a real browser
A clean Chromium browser loads your home page and one product page, like a first-time visitor.
-
We watch every tag, cookie and consent signal
Before any click and after Reject, with every tracking hit stopped before it leaves our browser.
-
You get a score and a fix list
Issues sorted into Fix today, Improve and Working, each with an estimated fix time.
-
No signup to scan
Enter a URL and get the summary. An email is only needed for the detailed fixes.
-
Our browser sends no tracking hits
Every request to a pixel or analytics endpoint is stopped, so your reports stay clean.
-
Reports are private by default
Reports are never indexed. Only people you send the link to can open them.
Frequently asked questions
Is it really free?
Yes. Every tool on this page is free and needs no account. The scan tools show your score and every issue we found without any signup; the detailed fixes and evidence are sent to your email so you can come back to them.
Do you store my data?
We keep the raw scan evidence for 7 days and the report details for 30 days, then delete them. We keep the score history without any personal data. If you ask for the full report we keep your email address to send it, and you can ask us to delete it at any time. The CAPI deduplication checker and the UTM builder run entirely in your browser and upload nothing.
Will the scan show up in my Meta or Google reports?
No. Our scanner stops every request to an analytics or advertising collection endpoint before it leaves our browser, so no platform receives a page view or an event from us. Server-side setups that send events when a page loads may still see the visit; our requests carry the header X-AxiTrace-Scanner: 1 so you can filter them.
Why do I need to enter my email for the details?
The summary shows your score and the headline of every issue for free. The full report, with why each issue matters, how to fix it and the evidence we recorded, lives at a private link that we email to you. That keeps the report yours and lets you forward it to whoever fixes your tracking.
How is this different from Stape or Meta Pixel Helper?
Meta Pixel Helper shows what fires on one page in your own browser. Stape's tools focus on server-side tagging setups. These checkers load your whole store as a first-time visitor, compare what happens before and after Reject, measure how long Safari keeps your cookies and check deduplication across Meta, TikTok, Pinterest and Reddit, then give you a prioritised list of fixes.
Guides that go with the tools
- Safari deletes your tracking cookies after 7 days Why Safari caps cookies set by JavaScript or a CNAME, what it does to returning visitors and how to test your store. Read the guide
- How to check your Meta Pixel and Conversions API The five checks that matter, from a pixel that loads once to event_id and the _fbp and _fbc cookies, and how to run each by hand. Read the guide
- How to test Consent Mode v2 before and after Reject Read the gcs and gcd parameters in the Network tab and find the tags that ignore the visitor's choice. Read the guide
- Why events count twice and how to test a pair How Meta matches a browser event with its server copy, the six ways the match breaks and how other platforms differ. Read the guide