STERLING LAB
SINCE2013
MARKETS10 COUNTRIES
AUDITFREE · 5 DAYS

Meta CAPI & Pixel checker

14 questions about your Meta Pixel and Conversions API.

Short answer

The Meta CAPI & Pixel Checker is a free self-audit of a Meta Pixel and Conversions API setup. You answer 14 yes, no or not-sure questions and get a score out of 100 and a list of likely gaps, biggest first, each linked to a fix. It does not scan your website or read your Meta account, and your individual answers are not sent anywhere.

This Meta CAPI and Pixel checker is a free self-audit. Answer yes, no or not sure for each check. You get a score out of 100 and a list of the likely gaps, biggest first, each linked to an article that explains the fix. No email, no sign-up, nothing is scanned and nothing is read from your Meta account.

Updated . Plain-text versions for tools and AI assistants: markdown and JSON spec.

Run the self-check

The note under each question says where to look in Events Manager.

Events reach Meta

0 of 3 answered
Your key events (a purchase, a lead) reach Meta from the browser pixel and also from a server through the Conversions API.

Events Manager → your dataset → Overview: each key event should list both Browser and Server as sources.

Each event has one pixel and one server source. A store app plus a Tag Manager pixel, or two CAPI plugins, are not both sending the same purchase.

Open your confirmation page with the Meta Pixel Helper extension: one Purchase (or Lead) fire is expected. Then list every app, plugin and container that sends events to the dataset.

After the last change to tags, plugins or the server, someone completed a test conversion and saw it in Test Events as a Browser row and a Server row.

Events Manager → Test Events: open your test URL, complete a purchase or a lead form, and look for two rows for the same conversion, one labelled Browser and one labelled Server.

Deduplication and value

0 of 4 answered
For each event the pixel and the server send the same event name and the same event ID, so Meta can merge the two copies into one.

Test Events: expand the Browser row and the Server row for the same conversion and compare the Event ID field character for character. A missing or different ID means the copies are not merged.

The event ID is born once, on one side, and handed to both channels: as eventID in the pixel call and as the top-level event_id field of each server event, not inside user_data or custom_data.

In your tag template or code, find where the ID is generated and where each channel reads it. Test Events shows an event ID on the server row only when Meta read the field.

Purchase events carry the real order value and currency (a lead event carries the value you assigned to a lead), on the pixel and on the server copy.

Test Events: open a test purchase and compare the value and currency parameters of both rows with the real order.

Server events are sent soon after the action happens, not in a late batch, and you know how long the delay is.

Ask whoever runs the integration when the server event is sent: at once from the order or form, or later from a queue or an export. Compare the event time in Test Events with the time of your test.

Matching quality

0 of 4 answered
You know the current Event Match Quality of each key event and have looked at which customer details are missing when it is low.

Events Manager → Overview → open the event: Event Match Quality is shown per event, with the parameters that would improve it.

The server events include the browser’s _fbp and _fbc cookie values in user_data.

Test Events → expand the Server row → user_data: fbp and fbc should be present as strings, not empty.

Customer details sent through the Conversions API (email, phone, name, city, zip) are hashed with SHA-256, in lower case, before they leave your server.

Test Events → expand the Server row → user_data: hashed values look like long opaque strings. Plain text, or a warning icon, means a field is not hashed.

Your cookie banner and the pixel agree: the pixel starts after consent is given, and you know what the server sends for visitors who never use the banner.

Settings and upkeep

0 of 3 answered
The domain your events come from is verified in your Meta business account.

Meta Business settings → Brand safety → Domains: your website domain should be listed and verified.

You have opened the Aggregated Event Measurement settings for your domain and the events you optimize for are in the priority list, with the most important one first.

Events Manager → Aggregated Event Measurement (or Web Event Configuration): compare the list and its order with the conversions your campaigns optimize for.

In the last month someone compared the purchases or leads Ads Manager reports with real orders or leads in your shop, CRM or inbox.

Compare last month’s Meta-reported conversions with your own records. A steady gap is normal; a sudden drop, or a number that stops moving, means something broke.

What the checker looks at

The questions follow an event from your site to Meta. Events reach Meta covers whether the pixel and the Conversions API both send your key events, from one source each, and whether a test shows both copies arriving. Deduplication and value covers the shared event ID, the field it travels in, the value and currency on the event, and how soon the server copy is sent. Matching quality covers Event Match Quality, the fbp and fbc values, hashed customer details and the cookie banner. Settings and upkeep covers domain verification, Aggregated Event Measurement and a regular check against real orders.

For the reasoning behind the event ID checks, read Meta CAPI installed, attribution still broken.

How the score is calculated

Each check has a weight of 1, 2 or 3. Checks that decide whether Meta can merge and value your events weigh the most. A “Yes” earns the full weight, “Not sure” earns half, “No” earns nothing. A check marked as not applicable is left out of both sides of the sum.

The checks with weight 3 are core checks: Events sent by pixel and by CAPI; Same event name and event ID; Value and currency on Purchase and Lead. A “No” or “Not sure” on any of them keeps the result out of the top band, even when the score is 80 or higher, and the result names the core check to look at first.

The fix list is sorted by points lost, biggest first: a “No” loses the full weight of the check, a “Not sure” loses half of it. Checks that lose the same number of points keep the order of the table below.

Score = (sum of weights answered Yes + ½ × sum of weights answered Not sure) ÷ sum of weights of the applicable checks × 100, rounded to a whole number.

All 14 checks and their weights, 27 points in total
CheckStageWeight
Events sent by pixel and by CAPIMeta Conversions API setupEvents reach Meta3
One source per eventMeta CAPI installed, attribution still broken: the dedup keyEvents reach Meta2
A test conversion seen in Test EventsConversions API and the duplicate-event trapEvents reach Meta1
Same event name and event IDMeta CAPI installed, attribution still broken: the dedup keyDeduplication and value3
Event ID passed in the right fieldMeta CAPI installed, attribution still broken: the dedup keyDeduplication and value2
Value and currency on Purchase and LeadFacebook ads not converting: find the leakDeduplication and value3
Server events sent soon after the actionMeta CAPI installed, attribution still broken: the dedup keyDeduplication and value1
Event Match Quality checked per eventMeta CAPI installed, attribution still broken: the dedup keyMatching quality2
fbp and fbc sent with server eventsMeta CAPI installed, attribution still broken: the dedup keyMatching quality2
Customer details hashed before sendingMeta CAPI installed, attribution still broken: the dedup keyMatching quality2
Cookie banner and pixel agreeConsent Mode v2 and missing GA4 conversionsMatching quality1
Domain verified in Meta BusinessMeta Ads service: CAPI deduplication and account setupSettings and upkeep1
Events prioritized in Aggregated Event MeasurementMeta Ads service: CAPI deduplication and account setupSettings and upkeep2
Monthly check against real ordersServer-side tracking serviceSettings and upkeep2

Worked example

An online shop whose pixel and server both send events and that needs no cookie banner marks the banner check as not applicable, which leaves 26 of the 27 points in play. The server generates its own event ID, so “Same event name and event ID” is No. Nobody has looked at Event Match Quality, nobody knows whether customer details are hashed, and nobody has checked domain verification, so those three are Not sure. Everything else is Yes.

  1. Applicable weight: 27 − 1 = 26
  2. Lost: 3 + 1 + 1 + 0.5 = 5.5, so earned is 20.5
  3. Score: 20.5 ÷ 26 × 100 = 78.8, shown as 79

The fix list starts with the event ID, then Event Match Quality, hashing and domain verification. The event ID is a core check, so the result names it as the first thing to fix. The band is 50 to 79.

How to read your result

80 to 100
Solid on paper. The remaining items are tidy-up work. Re-run the check after any change to tags, plugins, consent or the server.
50 to 79
Gaps worth fixing. Some of what Meta merges and optimizes on is partial or guessed. A failed or unconfirmed core check holds you here even with a score of 80 or more. Start with the first item in the fix list.
0 to 49
Hard to trust. Fix the top items before you change budgets or optimization events, then run the check again.

These bands are our own cut-offs for deciding what to do next, not a benchmark. The order of the fix list matters more than the number itself.

What a self-check cannot see

Answers describe what you believe is set up. They cannot show an event ID that differs between the browser and the server, a field Meta does not read, or data that ad blockers and browsers drop before it arrives. Open Test Events and compare the two rows yourself, as described in our event ID article. Our Conversions API setup guide covers the setup, and the server-side tracking service page explains when a server is worth building.

For Google Ads and GA4, run the Conversion Tracking Checker, and for the cookie banner that gates your pixel, the Consent Mode v2 Checker. If you would rather have it checked inside the accounts, request a free conversion tracking audit of your Meta, Google Ads and GA4 setup.

Questions about the checker

Does the Meta CAPI and Pixel checker connect to my Meta account?

No. It asks questions and scores your answers. Nothing is loaded from your site, your pixel or your Meta account, so the result is only as good as the answers. Each question has a short note on where to look in Events Manager.

Why does “Not sure” count as half?

An unknown is not a confirmed failure, but it is not a pass either: nobody is watching that check. Half the weight keeps it visible in the score and on your list.

Is the score a benchmark against other advertisers?

No. The weights and the 80 and 50 thresholds are our own definitions, chosen to rank what matters most for deduplication and attribution. They are not drawn from industry data, and the score does not compare you with anyone.

What happens to my answers?

They stay in your browser tab, are not sent anywhere, and disappear when you leave or start over. Our site analytics receives only an aggregate: that the check was started and finished, with the final score, the band and the number of gaps, and the score again if you click the audit link. The individual answers are never sent.

Why can a high score still stay in the middle band?

The three checks with weight 3 are the events reaching Meta from both the pixel and the server, the shared event ID, and the value and currency. A No or a Not sure on any of them keeps the result out of the top band, even when the score is 80 or higher, because the rest of the setup cannot make up for events that are not merged or carry no value. This rule is our own definition, like the weights and thresholds.

Where do the questions come from?

From our published article on the Pixel and Conversions API event ID, our Meta Ads and server-side tracking service pages, our Conversions API guides, and Meta’s own terms: Conversions API, event ID, Event Match Quality, Aggregated Event Measurement and Test Events. Where our site gives no fact, the check is worded as an action to carry out, not as a statistic.

What does the free audit add on top of this?

We look inside your Meta dataset and the rest of your tracking and test the same points directly, instead of relying on answers, then send a written report with the fixes in order.