Skip to content

Meta Pixel and Conversions API checker

Find the sales Meta never counts.

Enter your store address. In about 40 seconds you see whether your pixel fires once, sends the product events Meta learns from and is ready to match a Conversions API copy, and what the gaps cost at your ad budget.

We open your site in a real browser. Takes about 40 seconds.

  • Free, no signup
  • About 40 seconds
  • Nothing is sent to your ad accounts
Scan reportnorthwind-outdoor.example

6problems found

  • No server-side trackingCritical
  • Meta pixel loaded twiceHigh
  • Meta ad clicks are not savedHigh
  • Tags fire before consentHigh

+2more in the report

What it costs

Meta spends your budget on the sales it can see.

A purchase that never reaches Meta teaches it nothing, and one that arrives twice teaches it the wrong thing. Either way your ads are shown to people less likely to buy.

Broken tracking costs about$1,300 - $1,800a month at this budget

The range is 13% to 18% of your budget, depending on your industry.

AxiTrace sends every order to the ad platforms from your server, so they stop bidding on half the picture.

  • up to 30%

    of orders never reach the pixel

    Ad blockers, Safari and consent banners cut the browser off before the purchase fires.

  • Twice

    is how often an event counts when the pixel loads two times

    Double events inflate your numbers and make your cost per result look better than it is. It usually happens when a theme and an app both install the pixel.

  • 24 hours

    is how long Safari keeps an ad click ID set by JavaScript

    After that, a purchase can no longer be matched to the Meta ad that started it.

What the scan checks for Meta

Every check finds one way Meta loses your signal.

Every check looks for one concrete problem in how your store talks to Meta.

Pixels & events

  • The same Meta pixel is loaded twice, so PageView is counted double
  • A Meta pixel loads but never sends PageView
  • Your product page sends no ViewContent or view_item event
  • ViewContent is sent without value or currency

+2more in the report

Server-side & dedup

  • No server-side tracking: your ad platforms only get what the browser lets through
  • Browser events carry no event_id, so server events cannot be deduplicated
  • The same event_id is reused across different events

Signal quality

  • The _fbp cookie is not set
  • A click from a Meta ad would not be stored in _fbc
  • Events carry no external_id or hashed customer data

Cookie durability

  • Your identity cookies are set by JavaScript, so Safari keeps them only for 7 days

Consent

  • Tags fire before the visitor interacts with the banner

What you get

Every Meta problem with the evidence and the fix.

Sample reportThis is a sample for a fictional store. Scan your own site above.

Sample report

northwind-outdoor.example

6 things to fix today, 2 to improve, 12 already working.

Fix today (6)

Critical and high impact issues. Quick wins first.

  • Why it matters

    Every event Meta, Google and TikTok receive from your store today goes through the visitor's browser. Ad blockers, Safari's tracking prevention, consent banners and slow pages stop a share of those events before they arrive, and nothing sends them again. The platforms then see fewer purchases than you make, optimise your campaigns on incomplete data and report a lower return on your ad spend. Server-side tracking (Meta Conversions API, Google enhanced conversions, TikTok Events API) is the standard fix, and an ad account without it is working with a blind spot.

    How to fix it

    Send your events from a server as well as from the browser, starting with Purchase, for every ad platform you pay for.

    1. 1Turn on a server-side connection for each ad platform you run ads on (Meta Conversions API, Google enhanced conversions, TikTok Events API).
    2. 2Or run server-side tagging (for example a server GTM container) on a subdomain of your store.
    3. 3Make sure browser and server events share the same event_id so they are deduplicated.
    4. 4Check in each platform's events manager that server events arrive, then scan again.

    A scan sees what the browser sends, so a server feed that runs entirely behind your store does not show here. If you believe you already have one, open each platform's events manager and confirm that server events arrive for every event, not only for some.

    With AxiTrace: AxiTrace sends your events to Meta, Google, TikTok and more from your server, next to the browser tags you already have.

    What we saw
    Platforms detected in the browserMeta, Google Analytics, Google Ads, TikTok
    First-party hosts we checkednone
    Server-side patterns foundnone

Improve (2)

Medium and low impact issues worth fixing next.

Fix times are estimates for someone who can edit your theme, tag manager or app settings.

Working (12)

Checks your store passed.

  • Advertising or analytics tags were found

    Affects All tags
  • Your Meta pixel sends PageView

    Affects Meta
  • Your product page sends a product view event

    Affects MetaAffects GA4
  • ViewContent carries content_ids and content_type

    Affects Meta
  • GA4 view_item carries an items array

    Affects GA4

Score breakdown

  • Pixels & events25/100

    25% of the score

  • Server-side & dedup0/100

    20% of the score

  • Signal quality50/100

    15% of the score

  • Cookie durability50/100

    15% of the score

  • Consent0/100

    15% of the score

  • Ad-blocker exposure75/100

    10% of the score

Not checked

These checks could not run on your site, so they count neither for nor against you.

  • Cookies come from a host on a different IP, so Safari caps them at 7 days

    None of your identity cookies is set by a server, so this check does not apply.

  • Consent Mode is present but ad_user_data or ad_personalization is missing

    Google Consent Mode was not detected, so its v2 signals could not be checked.

Pixel Helper vs this checker

Pixel Helper shows what fired. The scan shows what Meta will lose.

Meta Pixel Helper shows what fires on one page in your own browser. This scan also checks cookie lifetimes, deduplication readiness and consent behaviour. Use both.

How Meta Pixel Helper and the AxiTrace checker compare
Aspect Pixel Helper This checker
Where it runs Your own browser, with your cookies and consent choices A clean browser that visits your store as a first-time visitor
Pages The page you have open Your home page plus one product page it finds on its own
Deduplication Shows the event, not whether a server copy can match it Checks that browser events carry an event_id a Conversions API copy can match
Cookies Not covered Measures how _fbp and _fbc are set and how long Safari keeps them
Consent Not covered Compares what Meta receives before any click and after Reject

Next step

Test a browser and server event pair

Paste your pixel event and your Conversions API event and see at once whether Meta will count them once. Runs in your browser, nothing is uploaded.

Check the deduplication of your events

Customer story

CentrumKrzesel.pl

One of the largest online furniture stores in Poland. Measured on 20,000+ orders.

Meta was crediting our orders to the wrong campaigns and the wrong creatives. 42% of the orders our Meta ads started came after Meta stopped counting, so the ads that really brought buyers in looked weak. AxiTrace shows you which campaign and ad generated every order - and recommends how to reallocate your budget.

Dawid, CentrumKrzesel.pl
41.6%
of the orders Meta ads started came after Meta's 7-day window
+35%
more revenue started by non-brand Google campaigns than last click showed
< 24 h
from kickoff to full tracking, on a custom-built store

Check your own store in 40 seconds.

Enter your store address. You get every problem in your tracking, a fix for each one and what they cost at your ad budget.

  • Free, no signup
  • About 40 seconds
  • Nothing is sent to your ad accounts

Frequently asked questions

Something else on your mind? Ask us directly

How do I check if my Meta Pixel is working?

Enter your store URL above. The checker loads your home page and a product page in a real browser and reports whether the pixel loads once, whether PageView and ViewContent fire with value, currency and content_ids, and whether each event carries an event_id. Every issue comes with a fix.

How do you estimate what I am losing?

The calculator applies a range of 13% to 18% to the monthly ad budget you set, depending on your industry. That is the share of ad spend stores typically lose when ad platforms bid on missing or wrong conversion data. When a scan finds only smaller problems we count the low end of the range, and when it finds none we show no loss. It is an estimate for your budget, not a measurement of your ad account.

Can this checker see my Conversions API events?

Server events travel from your server to Meta and never pass through a visitor's browser, so no outside scan can read them. What the checker can see is whether your browser events are ready to be matched with a server copy: a stable event_id, the _fbp and _fbc cookies and a sensible cookie lifetime. To compare an actual browser and server pair, use the CAPI deduplication checker.

Why does a duplicate pixel matter?

When the same pixel ID is initialised twice, often once by a theme and once by an app, every PageView and sometimes every purchase is counted twice. Meta then optimises on inflated numbers and your cost per result looks better than it is.

What are _fbp and _fbc, and why do their lifetimes matter?

_fbp identifies the browser and _fbc stores the ad click ID from fbclid. Meta uses both to match events to people and clicks. When they are set by JavaScript, Safari deletes them after 7 days, or 24 hours after an ad click, so later purchases lose their match.

Will the scan send test events to my pixel?

No. The scanner stops every request to facebook.com/tr and other collection endpoints before it leaves our browser. Your Events Manager will not show any event from the scan.

Send Meta every sale, counted once.

AxiTrace records every order on your server and sends it to Meta, Google, TikTok and 6 more ad platforms. Free up to 10,000 visits a month.

Start Free

An agency, or more than 3M visits a month? Talk to us

  • Data stored in the EU
  • GDPR, with a DPA
  • On the Shopify App Store
  • Plugin on WordPress.org
  • In ChatGPT and Claude

AxiTrace demoSample store

Store revenue$42,300last 30 days
Ad spend$9,9755 campaigns on 3 ad platforms
Store ROAS4.24revenue over ad spend
Orders1,223from every source

ROAS next to profit after costs

Store ROAS4.24 Campaign profit+$3,015

Store ROAS counts all revenue. Campaign profit subtracts the product costs and the ad spend of each campaign.

Axi, morning briefing

Two campaigns lose money after costs: Google Shopping and TikTok Video. Meta Prospecting holds a steady profit and is the one to scale in steps.

Sample data. In your own account you see your own store.

Start Free