// Free Tool · Shopify + Meta
Your tracking is lying to you.
The free Shopify Tracking and Attribution Checker reads your storefront the way Meta does and flags the tracking gaps worth chasing, no login required.
Free · read-only · about 30 seconds · no signup
// Why This Exists
Watch the leak happen
Purchase events stream from the browser toward Meta. Ad blockers, iOS, and cookie loss knock out a real share of them at the pixel drop, often 20 to 40 percent. Hover the gap and your cursor becomes the patch, then watch the capture rate climb. Finding where to patch it is what the report does.
// What The Scan Reads
Fourteen checks, five layers of your stack
The same methodology as the paid deep scan. The free pass reads everything visible from the outside; the deep scan confirms the rest against your real order data.
Tracking 05
- Pixel present on all pages
- CAPI sending Purchase
- event_id deduplication
- Event timing drift
- Action source
Data Quality 03
- Event match quality
- Advanced matching fields
- Full funnel event coverage
Shopify 03
- Checkout Extensibility
- Thank-you page alignment
- Refund events to CAPI
Consent 01
- Consent Mode v2 signal
Attribution 02
- Cross-vendor duplicates
- Shopify vs Meta revenue
// What A Surface Scan Can See
What a surface scan can and cannot see
Server-side events are invisible from the outside. That is physics, not a paywall trick, and it is exactly why the deep scan exists.
Free · Surface Scan
Reads your storefront like Meta does
- ▸Pixel presence, placement, and duplicates
- ▸Browser event wiring and event_id hints
- ▸Advanced matching fields in the payload
- ▸Consent Mode v2 signals
- ▸A grade estimate and the gaps worth chasing
Runs against your public pages. Nothing to install, nothing to connect.
Paid · CAPI Leak Report
Confirms all 14 checks with your order data
- ▸Server-side event verification, dedupe rates, refund coverage
- ▸Every leak priced in dollars per month from your last 30 days
- ▸A fix sequence your dev can execute, with a free verification rescan
Read-only order data, delivered as a permanent shareable report.
See a sample report →// From Leak To Fixed
Three steps, then the algorithm sees straight
01
Run the free scan
Thirty seconds against your storefront. You get a grade estimate and every gap visible from the outside.
02
Get the deep report
All 14 checks confirmed against real orders, each leak priced monthly, sequenced by payoff.
03
Fix and verify
Hand the report to your dev or walk the first fix with Michael. A free rescan proves the recovery.
// Straight Answers
Questions stores actually ask
Is this really free?
Yes. The surface scan is free, with no login and no card. The paid product is the deep report that confirms server-side behavior and prices each leak.
What does the scan actually look at?
Everything Meta can see from your storefront: pixel placement, duplicate tags, browser event wiring, matching fields in the payload, and consent signals.
Why can a static scan not give a definitive answer?
Server-side CAPI events, dedupe rates, and refund coverage never touch the browser, so a static read cannot confirm them. That is why the free scan never grades a Shopify store an F: a C or D here means "this needs the deep scan to confirm," not "you are broken." Confirming the rest takes read-only order data, which is what the paid report does.
Does it work for non-Shopify stores?
The methodology is built around Shopify checkout. Other platforms get the browser-side checks with partial results.
// Scan Terms
What running this scan means
The scan reads a few public pages on the storefront you enter, typically the homepage, a product page, and the cart. These are the same pages any visitor's browser already loads when they shop there. It runs once per request and stays on the public surface of the site, the same view any shopper gets without an account or a completed order, so nothing personal ever comes back from it.
A completed scan stores the store's domain, grade, and scan time. Public grade totals keep each store name private. The full result stays cached for under an hour so a second look at the same store loads instantly, and a rate-limit counter keyed to your IP address keeps the tool available for everyone.
This tool is built for stores you own, manage, or are evaluating for a legitimate business purpose, a client audit, a partnership review, or research on a storefront you are considering working with.
Scan limits apply per visitor and per store, so a single store can only be live-scanned a handful of times in a short window before the tool falls back to the most recent result already on file. Scripted or automated use sits outside those limits and gets blocked.
// Thirty Seconds, Zero Risk
Find out what Meta actually sees
Every day a leak runs, the algorithm optimizes on bad data and your budget follows it.
More on CAPI and attribution
Deeper reading on server-side tracking, dedup, and the attribution math behind DTC.
11 min read
The field guide to Meta CAPI for DTC operators
A pattern-library field guide to Meta CAPI for DTC operators. Six failure shapes, six working fixes, grounded in a 48-hour Shopify rebuild.
17 min read
Google Enhanced Conversions CAPI: the parallel build to Meta
A tutorial on Google Enhanced Conversions CAPI as the parallel build to Meta. Schema differences, the GTM server pattern, when to ship which first.
16 min read
Debugging event ID collisions in production Meta CAPI
A postmortem on event ID deduplication debugging. Three collision shapes, the BigQuery SQL to surface them, and the fix that pinned the generator.
16 min read
Meta CAPI match quality scoring: how to audit your setup
A field operator's audit pattern for Meta CAPI match quality scoring. Read Events Manager, decode the per-identifier score, and find what is leaking spend.
9 min read
Reconciling GA4, Meta, and Shopify purchase counts
The short, full, and nuanced answer on ga4 meta shopify reconciliation. Five sources of variance and the one number to trust per question asked.
11 min read
Meta CAPI Double-Counting: Why It Happens and How to Fix It
CAPI without proper event deduplication doesn't just miss conversions - it invents them. Here's how the double-counting works and how to stop it.
11 min read
The field guide to Meta CAPI for DTC operators
A pattern-library field guide to Meta CAPI for DTC operators. Six failure shapes, six working fixes, grounded in a 48-hour Shopify rebuild.
17 min read
Google Enhanced Conversions CAPI: the parallel build to Meta
A tutorial on Google Enhanced Conversions CAPI as the parallel build to Meta. Schema differences, the GTM server pattern, when to ship which first.
16 min read
Debugging event ID collisions in production Meta CAPI
A postmortem on event ID deduplication debugging. Three collision shapes, the BigQuery SQL to surface them, and the fix that pinned the generator.
16 min read
Meta CAPI match quality scoring: how to audit your setup
A field operator's audit pattern for Meta CAPI match quality scoring. Read Events Manager, decode the per-identifier score, and find what is leaking spend.
9 min read
Reconciling GA4, Meta, and Shopify purchase counts
The short, full, and nuanced answer on ga4 meta shopify reconciliation. Five sources of variance and the one number to trust per question asked.
11 min read
Meta CAPI Double-Counting: Why It Happens and How to Fix It
CAPI without proper event deduplication doesn't just miss conversions - it invents them. Here's how the double-counting works and how to stop it.