Now onboarding AuriaTrack consultants · Become a Consultant →
Guide

The Meta Conversions API for Small Business:
What the Pixel Can’t See

The Meta Conversions API lets your website or CRM tell Facebook and Instagram about a lead or a sale directly, server to server, instead of relying only on a pixel in the visitor’s browser. Here is what it is, how it differs from the pixel, why the two must share an event ID, and how to send real sales back so Meta stops optimizing for form fills.

What Is the Conversions API? CAPI vs Pixel

The Meta Pixel is a script that runs in the visitor’s browser and reports what they do. The Conversions API (often shortened to CAPI, and still widely called the Facebook Conversions API) is the same idea run from a server you control. They are not rivals. Meta’s own developer documentation recommends running the Conversions API alongside the pixel.

The pixel: browser events

A snippet on your site fires events such as PageView and Lead from the visitor's browser. It is quick to install and sees on-page behavior, but it only works if the browser loads it, runs it and lets it send.

The Conversions API: server events

Your website backend, CRM or a connected platform sends the same kind of event to Meta over the internet. Nothing depends on the visitor's browser, so ad blockers and closed tabs do not stop it.

Both together: the redundant setup

Run the pixel and the API for the same events and Meta receives whichever copy arrives. That only works if the two copies carry a shared event ID, so Meta can tell they are one event, not two.

Events the browser never sees

A quote accepted on the phone, a job paid in person, a lead marked qualified in your CRM. None of these happen on a web page, so a pixel cannot report them. A server can, days or weeks later.

Why Browser-Only Tracking Loses Events

A pixel event has to survive several things before Meta ever hears about it. Ad blockers and privacy extensions can stop the script from loading. Browsers with tracking prevention, Safari most visibly, limit how long cookies last and strip identifiers from links. A visitor can decline cookies, or close the tab before the thank-you page finishes loading. Each of those is a real inquiry that never reaches Ads Manager.

The losses are not random, either. People who research for a week before calling, or who come back on a different device, are the ones most likely to fall out of a cookie-based trail, and for a service business they are often the higher-value jobs. The mechanics are covered in Why Your iOS and Safari Conversions Disappeared.

A server event avoids most of that, because your server already knows the lead arrived: it has the form submission in hand. What it does not automatically know is which ad the person came from. That is the job of the click ID Meta adds to ad links (fbclid) and the first-party cookie that stores it, which the server sends along with the event. The Conversions API is only as good as the identifiers you keep.

One Lead, One Event: How event_id Deduplication Works

If the pixel and the server both report the same form fill without a shared ID, Meta sees two leads. This is one of the most common reasons Ads Manager reports more leads than you received. Meta’s recommended fix is matching the event name and an event ID on both copies.

1
Generate one unique ID per event

When the visitor submits the form, create an ID for that single submission, such as a random string or your own lead number. Every event needs its own; reusing one across leads hides real conversions.

2
Send it with the pixel as eventID

The browser event goes to Meta with that value in the pixel's eventID field, under a standard event name such as Lead.

3
Send the same value from the server as event_id

The Conversions API event carries the identical ID in event_id and the identical name in event_name. Lead in one place and lead_submitted in the other will not match.

4
Let Meta keep one copy

According to Meta's developer documentation (as of November 2026), matching events received within 48 hours of the first one are deduplicated, and when the copies do not meaningfully differ Meta generally keeps whichever arrived first.

5
Check it in Events Manager

Submit a test lead and confirm the event shows as received from both browser and server, then deduplicated. Meta also documents a fallback method using the fbp cookie or an external ID, but event ID plus event name is the one it recommends.

Deduplication only works across browser and server. Two browser events with the same details are not merged, and neither are two separate leads. A thank-you page that fires on every refresh still needs fixing at the source. For the other reasons Meta’s lead count runs high, see Facebook Says 40 Leads. You Got 12.

Hashed Customer Information and Event Match Quality

A server event is only useful if Meta can connect it to a person on Facebook or Instagram. It does that with customer information you send along with the event. Meta rates how well that is working with a score out of 10 called Event Match Quality, shown in Events Manager for website events.

Hash contact details

Email, phone, name, city, state, ZIP and similar fields must be hashed with SHA-256 before they are sent. Hashing turns them into fixed codes that match only if the original values were identical.

Normalize before hashing

Meta's rules include trimming spaces and lowercasing email, and stripping symbols from phone numbers while keeping the country code: (650) 555-1212 in the US becomes 16505551212. A stray capital letter produces a different hash and no match.

Send the browser identifiers unhashed

The click ID cookie (fbc), the browser ID cookie (fbp), the visitor's IP address and user agent are sent as-is. Meta's documentation says these must not be hashed.

More fields, better matching

Meta's guidance is that sending more customer information parameters can raise Event Match Quality. Email and phone on every lead, plus the click ID when the visit came from an ad, cover most of it.

Sending Lead Quality and Sales Back to Meta

Fixing lost and doubled events gets Meta an accurate count of leads. The larger gain comes from telling it what happened next. If the only conversion Meta ever sees is “submitted a form,” its delivery system goes looking for more people who submit forms, including the ones who never pick up the phone. Report which leads became booked appointments and paying customers, and it has something better to aim at.

There are two routes, depending on where your leads come from. For leads collected in Meta’s own Instant Forms, Meta’s documentation (as of November 2026) describes the Conversions API for CRM integration, paired with the Conversion Leads performance goal: your CRM sends lead stages back with the Meta lead ID, ideally daily, and Meta optimizes toward the stage you choose. Meta sets eligibility conditions for that goal, including a minimum monthly lead volume and a stage that converts within a set range and timeframe, so check the current requirements before planning around it.

For leads from your own website, the server sends a later event, such as a purchase with the job’s value, matched by the hashed email and phone and the stored click ID. Timing matters here: Meta’s API refuses most events with a timestamp more than seven days in the past, so a sale should be reported soon after it closes, not batched at month end. (Meta used to run a separate Offline Conversions API; offline events are now sent through the Conversions API itself.)

Real revenue also keeps the platform honest. A purchase value of a closed job is something you can reconcile against your own books; an estimated value per lead is not. Google has the equivalent mechanism, covered in Enhanced Conversions for Leads, and why platform counts and CRM counts differ in the first place is in Google Ads Says 30 Conversions. Your CRM Says 9.

Server-Side Does Not Mean Rule-Free

Moving tracking to a server changes where events are sent from, not what you are allowed to send. The same consent rules, platform terms and privacy policy obligations apply.

Say what you collect

Your privacy policy should explain that you use advertising cookies and share hashed contact details with ad platforms to measure ads. If you would not be comfortable explaining it, do not send it.

Respect consent where it applies

Where your visitors have the right to decline tracking, a server event for someone who declined is still tracking. Build the consent check into the server path, not just the browser.

Send the minimum

Contact fields for matching, an event name and a value. Not the message the customer typed, and not details about their health, finances or anything else sensitive. Both Meta and Google restrict sensitive data in their terms.

Hashing is not a free pass

Hashing keeps raw emails and phone numbers out of the request, but a hash can still be matched to a person. That is the whole point. Treat it as personal data, and keep the original records encrypted and access-controlled.

Real Revenue, Sent Back Server-Side

The Conversions API is a pipe. What makes it worth having is what you put through it, and for most small businesses that is the hard part: keeping the click ID with the lead, and knowing which leads turned into paying jobs.

That is the loop AuriaTrack is built around. First-party tracking on every plan stores the ad click IDs and UTMs on your own domain, so iPhone and Safari visitors stay attributable. Won deals are matched back to the lead and campaign that started them, and on the Ascent and Summit plans real revenue goes back to Meta and Google through the server-side Conversions API and Enhanced Conversions, so the platforms learn which ads bring paying customers, not just clicks. Lead contact details are encrypted when stored. See how attribution works →

Which plan includes what is laid out on the pricing page. Once revenue is flowing per campaign, try the ROAS calculator on your own numbers.

What People Ask About the Conversions API

What is the Meta Conversions API?
The Meta Conversions API is a way to send conversion events, such as leads and purchases, to Meta directly from your server or CRM instead of only from a pixel in the visitor's browser. It is often called CAPI or the Facebook Conversions API.
Do I still need the Meta Pixel if I use the Conversions API?
Yes, in most cases. Meta recommends running the Conversions API alongside the pixel, with a shared event ID so the two copies of each event are counted once. The pixel sees on-page behavior; the server fills the gaps and reports what happens offline.
How does Conversions API event deduplication work?
Meta treats a browser event and a server event as one when they share the same event name and the same event ID, sent as eventID from the pixel and event_id from the API. Per Meta's documentation, that applies to matching events received within 48 hours of each other.
What is Event Match Quality?
Event Match Quality is Meta's score out of 10 for how well the customer information on your server events can be matched to Meta accounts. Sending more correctly hashed fields, such as email and phone, plus the click and browser IDs, generally raises it.
Can I send closed sales from my CRM to Meta?
Yes. For Instant Form leads, Meta's Conversions API for CRM integration sends lead stages back with the Meta lead ID. For website leads, a server event with the sale's value can be matched using hashed contact details and the stored click ID, reported within Meta's time limits.
Is it legal to send customer emails to Meta?
It can be, when done within the law and Meta's terms: hashed, disclosed in your privacy policy, with consent where your visitors' local rules require it, and without sensitive information. Rules vary by location and industry, so check what applies to your business.

Teach Meta Which Leads Paid

Book a demo and we'll show you how your Meta leads line up against the jobs they actually became.