How the free tracking audit works
What the scanner checks
The scanner runs 24 checks across four categories: foundation, event coverage, data quality, and resilience.
Foundation covers the install itself. It looks for a Meta pixel in your page HTML, your inline scripts, your
Google Tag Manager container, and Shopify's pixel sandbox registry. It asks Meta's public config endpoint
whether each pixel ID is valid, flags stray IDs and duplicate install layers that fire the same event twice,
and scans the landing page your ads point at, because a campaign page without tracking burns money quietly.
Event coverage maps what fires where. The scanner crawls up to 6 pages and looks for the funnel events Meta
optimizes against: ViewContent, AddToCart, InitiateCheckout, and Purchase for stores, or the Lead path for
service businesses. Custom events that never map to a standard event get flagged, because Meta cannot optimize
against a name it does not recognize.
Data quality reads the parameters on your actual event calls: value and currency on Purchase, content IDs on
browse events, values on Lead events, Advanced Matching in Meta's live pixel config, and whether Meta has
placed data restrictions on your pixel. Resilience checks the infrastructure around the pixel: the Conversions
API, browser and server deduplication keys, consent banners that silently block tags, domain verification,
pixel load position, an independent analytics tool for cross-checking, and dead scripts from shut-down
platforms still loading.
A URL scan cannot see everything, and this one says so. Hosted checkout events, sealed sandbox pixels, and
Conversions API internals get marked needs-verification instead of guessed at. The full scoring math is public
on the methodology page.
The 5 leaks we find most often
- Purchase events missing value and currency. Meta gets told a sale happened but not what it was worth. Value-based bidding and ROAS reporting run blind.
- The same event firing twice. A hardcoded pixel plus a tag manager install doubles conversion counts, inflates reported results, and skews optimization.
- Consent banners silently blocking the pixel. Visitors who decline or ignore the banner fire zero events. Your own tests pass because you accepted your own banner long ago.
- No Conversions API. Ad blockers and browser privacy features drop browser-side events. Without a server-side channel, those events are gone for good.
- Ad landing pages with no tracking at all. Campaign pages built outside the main site template often ship without the pixel. Every paid click lands untracked.
Questions about the audit
Is the tracking audit really free?
Yes. The full report renders on the page with no login, no email, and no card. An optional email field appears after the report if you want a copy sent to you.
What does the scanner read?
Only what any visitor's browser already sees: public HTML, scripts, your tag manager container, Shopify's pixel sandbox registry, and Meta's public per-pixel config endpoint. No ad account access, no passwords.
Can a URL scan verify my whole setup?
No, and the report says so. Hosted checkout events, sealed sandbox pixels, and Conversions API internals need a live check in Meta Events Manager. Those items are marked needs-verification, never verified.
How long does a scan take?
About 20 seconds. The scanner reads up to 6 pages: homepage, product, collection, cart, contact, and the ad landing page you give it.
My score looks low. Is my tracking broken?
Not necessarily. The score is a verified health score: your setup only gets credit for what an external scan can prove. Sites with sealed setups see two numbers, a verified score and a potential score, and the fastest way to close the gap is a 20-minute live walkthrough.