Meta’s Conversions API is a channel that sends your business events, such as a purchase, signup or closed sale, from your server, your website platform or your CRM straight to Meta, without depending only on the customer’s browser. It complements the Pixel and does not replace it. For a small business it pays off when the sale happens outside the website, on WhatsApp or in the CRM, or when the Pixel alone misses events. To check that it works, use the Test Events tool and confirm that each event arrives only once.
This guide shows what Meta’s Conversions API does, when it’s worth it for a small business, the precautions that prevent duplicate events and the ten-minute test to find out if yours is working. Every technical rule comes from Meta’s official documentation, which we opened for this article on October 30, 2026.
What Meta’s Conversions API is
It’s a connection between an advertiser’s marketing data and Meta, made through the server, the website platform, the app or the CRM. The official documentation says it helps with ad targeting, lowering cost per result and measuring results.
The events that arrive through it go into the same dataset that receives events from the Meta Pixel. That’s why they’re used for measurement, reporting and optimization in a similar way. A single integration can send website, app, business messaging and offline sales events.
The Pixel is code that runs in the browser of whoever visits the site. The Conversions API is your system telling Meta. What the browser didn’t see, the server did.
Search interest is small and very specific. According to the Google Ads Keyword Planner, as of October 30, 2026, “meta conversions api” gets about 110 searches per month in Brazil, with an estimated top-of-page bid of R$32.08. That is the bid Google estimates for the top of the page, not what each company pays. People who search for this are usually dealing with a real measurement problem, not just curious.
Pixel and Conversions API: How They Work Together
The Pixel records what happens in the browser, and the API records what your system knows. Using both together, with the same event arriving through both paths, is the setup Meta calls redundant, and it depends on a deduplication rule, explained below.
| Meta Pixel | Conversions API | |
|---|---|---|
| Where it runs | In the visitor’s browser | On the server, the platform or the CRM |
| What it sees | Page views, clicks, form submissions | Anything your system records, including a sale closed later |
| Depends on the browser | Yes | No |
| Requires code | A snippet on your site | Depends on the integration method |
| Main risk | Lost event | Duplicate or misattributed event |
The last row is the one that trips people up most. The Conversions API doesn’t break measurement because it’s complex. It breaks because it’s set up without checking for duplicates.
When it makes sense for a small business
It makes sense when an important part of the sale happens where the Pixel can’t see it. This is our criterion, not a Meta rule, and it works better than asking “should I have it or not?”
Signs it’s worth it.
- The sales conversation happens on WhatsApp or by phone, and the website only generates the first contact.
- You use a CRM and know which contacts became customers, but Meta doesn’t.
- The number of purchases or sign-ups in Meta is visibly lower than in your store or spreadsheet.
- You spend enough on ads that every lost event gets in the way of optimization.
It’s still not a priority if the Pixel isn’t even installed correctly, or if the goal is only reach, with no conversion you can track.
Meta’s documentation says that if you already have a Pixel, you can turn on the Conversions API for website events from Events Manager, with a one-click option, no code and no setup fee. On many website platforms, this is the shortest path for a small business. Before you hire any development work, check whether your platform already offers it.
If you’re trying to decide whether to invest in Meta or Google first, our comparison Google Ads vs. Meta Ads helps you decide where your money works harder for your type of business.
Event deduplication: the safeguard that stops you from counting a sale twice
If the same event arrives through both the Pixel and the API, Meta only discards the duplicate if both carry the same identifier. Without it, one purchase shows up as two, your cost per result looks lower than it really is, and optimization learns the wrong thing.
The official documentation describes two methods. The recommended one uses the `event_id` and the event name.
- The `eventID` sent by the Pixel must match the `event_id` sent by the API.
- The Pixel event name must match the API `event_name`.
- If the same combination arrives from both sources for the same Pixel within 48 hours, the event that arrives later is discarded.
The second method uses the `event_name` plus the `fbp` or the `external_id`, sent the same way from both the browser and the server. With it, only a server event that arrives after a browser event within the same 48 hours is deduplicated. Two browser-only or two server-only events, even if identical, are not deduplicated.
The documentation doesn’t say what happens when the `event_id` is missing, or whether Meta falls back to the second method. So the practical rule is to generate the `event_id` at the moment of the event, send the same value through both channels, and check it in testing. The full detail is on the official deduplication page.
What data to send with the event
The event needs at least one piece of user data in the correct format, and for website events the `client_user_agent` is also required. The more valid data you send, the better the chance that Meta matches the event to a person.
The customer information parameters documentation summarizes the format of each one.
| Parameter | What it is | Format |
|---|---|---|
| `em` | No leading or trailing spaces, lowercase, hashed with SHA-256 | |
| `ph` | Phone | No symbols, letters or leading zeros, with country code, hashed with SHA-256 |
| `fbc` | Click ID | Comes from the `_fbc` cookie, not hashed |
| `fbp` | Browser ID | Comes from the `_fbp` cookie, not hashed |
| `client_ip_address` | IP address | Never unhashed |
| `client_user_agent` | User’s browser | Not hashed |
For events sent from the server, you have to provide the IP address and browser manually. In the browser, the Pixel adds them on its own. If you use a platform with a ready-made integration, you don’t have to set this up by hand, but it’s worth knowing what is being sent.
Personal data is hashed for security, and your website needs to explain in its privacy policy what it collects. Before sending data about people, check with your legal counsel what your policy and the visitor’s consent cover. On the Google side, the consent mode v2 guide shows how consent affects measurement.
How to check that the Meta Conversions API is working
Open Events Manager, go to Data sources, choose your Pixel and use the Test events tab, which generates a test code for server events. The official documentation describes this path. It’s the way to see the API working before you depend on it.
The test, in six steps.
- In Events Manager, open your Pixel and go to Test events.
- Copy the test code the tool generates.
- Send a server event with that code in the `test_event_code` parameter.
- See the event appear in the testing window.
- Perform the same action on your site so the Pixel sends the same event, and confirm that both show up with the same `event_id`.
- Remove the `test_event_code` from your production sends.
According to the documentation, events sent with `test_event_code` are not discarded. They go into Events Manager and are used for targeting and measurement. The code is only for testing and should not stay in the final setup.
Once you start sending, the documentation says you can verify events within 20 minutes. Under Overview, Events Manager shows the count of raw, matched and attributed events, and the Connection Method column shows which channel each event came through.
If any `event_time` is more than 7 days old, the documentation says the entire request returns an error and no events are processed. Send events close to the time they happen.
What the Conversions API changes in your paid search
It doesn’t increase sales on its own. It improves what Meta knows about who bought, and the campaign learns from that. If the sale closes on WhatsApp, sending that sale back is what separates a campaign that optimizes for conversations from one that optimizes for customers.
If you run Google Ads, the logic is the same. Google also learns better from the sale than from the click, and the path is similar: record where the contact came from and send the result back. We explain this in conversion tracking with GA4 and CRM and, for sites that want more control over how data is sent, in server-side tagging.
How Ciclicko approaches tracking
At Ciclicko, measurement comes before the ad. We map where the sale happens, define which event represents real money, install and test the tracking, and check that the platform’s number matches the one in your CRM or store. We do this work for Google Ads and GA4, which is our specialty as a Google Partner agency.
The same discipline applies to Meta. An event with no identifier, no testing and no check against actual revenue produces a nice-looking report and the wrong decision. We don’t promise higher sales, only a number you can trust.
Frequently asked questions
What is Meta’s Conversions API? It’s a connection that sends events from your server, website platform, app or CRM to Meta, to help with targeting, measurement and lowering the cost per result.
Does the Conversions API replace the Pixel? No. It complements the Pixel. Using both requires the same event to carry the same identifier on both paths, so Meta can discard the duplicate.
How do you set up Meta’s Conversions API? If you already have a Pixel, you can turn it on for website events in Events Manager, with a one-click option. The other route is a direct integration, where your server sends requests to the API.
How do you know if the Conversions API is working? Use the Test Events tab in Events Manager, send an event with the `test_event_code`, and check that it shows up only once, with the Pixel and server events deduplicated.
How long does Meta take to show the events? According to the official documentation, you can verify within 20 minutes after you start sending.
Do you need a developer to use the Conversions API? Not always. Website platforms with a ready-made integration and the one-click option for those who already have a Pixel cover many cases. Direct integration and sending CRM sales usually call for someone who can code.
Want to measure actual sales, not just clicks?
See our work on Google Ads conversion tracking with CRM and request a review of how your sales are being measured today.