Free diagnostic · no login · no email · no pixel ID needed

Free Meta pixel audit.
We’ll show you exactly where it leaks.

Your Meta tracking has leaks. Paste your URL and the pixel audit scans your live site in about 20 seconds: the pixel, inside your tag manager, Meta’s own config for your pixel, your consent stack. Then we hand you a prioritized fix list with the evidence to back it up.

reads inside GTM containersreads Meta’s live pixel configx-rays Shopify’s pixel sandbox
Sharpen the estimate · optional

We only read what any visitor’s browser already sees: no passwords, no ad account access. The full report is free. No email, no gate, no catch. Scored per our public methodology, or watch us scan our own site, live.

How the free Meta pixel 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.

How to run a Meta pixel audit

Three steps, and none of them need a pixel ID, a login, or access to your ad account.

  1. Paste your URL. The homepage is enough. If your ads point somewhere specific, add that landing page in the optional field: campaign pages built outside the main site template are where tracking goes missing most often, so it is worth auditing that page on its own. You can also tell us your business model and monthly spend, which sharpens the estimate but is not required.
  2. The scanner runs its 24 checks. It takes about 20 seconds. It reads up to 6 pages, looks for your pixel in the page HTML, your inline scripts, your Google Tag Manager container, and Shopify's pixel sandbox registry, asks Meta's public config endpoint whether each pixel ID is valid, maps which funnel events fire where, reads the parameters on those event calls, and checks the infrastructure around the pixel: server-side signal, deduplication keys, consent banners, and domain verification.
  3. You get a prioritized leak report. Every finding is ordered by severity, with the evidence the scanner used to reach it. Anything an external scan cannot prove, like hosted checkout events or whether server events actually deduplicate, is marked needs-verification rather than guessed at. The report renders on the page. No email, no gate.

The 5 leaks we find most often

  1. 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.
  2. The same event firing twice. A hardcoded pixel plus a tag manager install doubles conversion counts, inflates reported results, and skews optimization.
  3. 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.
  4. No Conversions API. Ad blockers and browser privacy features drop browser-side events. Without a server-side channel, those events are gone for good.
  5. 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 Meta pixel 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.

Can this tool audit my Facebook pixel automatically?

Yes. Paste your site URL and the tool runs the audit for you, with no login and no pixel ID. To do it by hand, confirm exactly one pixel loads on every page, check that ViewContent, AddToCart, InitiateCheckout, and Purchase (or Lead) fire where they should, confirm Purchase carries value and currency, and confirm your consent banner is not blocking the tag. The Facebook pixel and the Meta pixel are the same thing, so the same audit applies.

What does a pixel audit check?

This one runs 24 checks across four categories. Foundation covers the install: pixel presence in your HTML, inline scripts, GTM container, and Shopify's pixel sandbox registry, plus stray IDs and duplicate install layers. Event coverage maps which funnel events fire on which pages. Data quality reads the parameters on your event calls, including value and currency, content IDs, and Advanced Matching. Resilience covers the Conversions API, deduplication keys, consent banners, domain verification, and pixel load position.

Does the pixel audit check the Conversions API and deduplication?

It checks what a URL scan can prove. The scanner looks for server-side signal (server-side GTM, Shopify's native channel, tagging-provider fingerprints) and for eventID parameters on your conversion events, which is what browser and server events need in order to deduplicate. It cannot confirm that server events actually arrive or actually deduplicate, because only Meta Events Manager shows that. Those items come back marked needs-verification rather than passed.

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.

Keep reading