Does Meta show more purchases for a campaign than your shop’s order list does? One possible reason is that the same event reaches Meta twice: first from the browser and then from the server. Here you will find how Meta Pixel and the Conversions API work together, what Meta needs to recognise a duplicate event and how to check it.
What is the difference between Meta Pixel and the Conversions API?
Meta Pixel is a piece of JavaScript that tracks visitor activity on your website. It runs in the visitor’s browser and sends events to Meta, such as a page view or a purchase. The Conversions API connects your own systems to Meta: your server, website platform, app or CRM sends the events to Meta. Meta processes them in the same way as Pixel events, so you can use them for measurement, reporting and ad optimisation.
A Pixel that runs in the browser depends on what the browser allows. Ad blockers and privacy extensions can interfere with Pixel requests. An event sent from a server does not depend on the browser, so the same event can be sent both ways. If you already have a Pixel, you can add the Conversions API for website events with one click in Events Manager. You do not have to write code or pay a setup fee.
| Topic | Meta Pixel | Conversions API |
|---|---|---|
| Where the event happens | In the visitor’s browser. | On your server, website platform or CRM. |
| What it depends on | The browser: blockers and privacy extensions can interfere with requests. | Your own system, not the visitor’s browser. |
| What you need | The Pixel code on the page or a Tag Manager tag. | A connection in Events Manager if you already have a Pixel, or your own server integration. |
When I look at the results of Meta ads, I do not stay inside the ad account. I review the offer, the creative, the landing page and the Pixel and Conversions API measurement together.
How does Meta recognise a duplicate event?
When the same purchase reaches Meta through both the Pixel and the Conversions API, Meta has to understand that it is one purchase. For that, both events need the same name and the same ID. In the Pixel these are event and eventID, in the Conversions API event_name and event_id. Meta removes the duplicate only if the events reach the same Pixel ID within 48 hours. Later events with the same ID are discarded.
The ID has to reach both sides from the same place. For a purchase, the order number works well: the page code and the server get it from the same order and do not need to agree on it separately.
Another option is to use the event name together with fbp or external_id instead of the ID, as long as they are the same on the browser and server events. This method generally works only if the browser event reaches Meta first.
The first thing I look at is whether the browser and the server count the same action twice. For that I open the Preview mode in GTM and the browser network requests, and I review the plugins in use.
What does a Conversions API event need?
A website event in the Conversions API needs a few required fields: client_user_agent, action_source and event_source_url. The event time (event_time) is given in Unix seconds and can be up to 7 days old. If the time is older, Meta rejects the whole request, not just one event.
Before sending, you have to hash the customer data: email, phone, name, gender, date of birth, city, state, postal code and country (hashing turns a value into an irreversible code). The parameters client_ip_address, client_user_agent, fbc and fbp are not hashed, so you send them as they are. If you use a Meta Business SDK, the SDK does the hashing for you.
Practical tip
Send the event only once the action has really succeeded: the form is submitted or the purchase is made. Otherwise Meta optimises for the wrong action.
How do you check that an event is not sent twice?
Go through these four steps after every change.
- Open Test Events. In Meta Events Manager you find it under Data Sources, in your Pixel. Click “Open Website” and do a real action on the site, for example submit a form. Events can take a few minutes to appear and an ad blocker may hide them. The Pixel Helper browser extension shows a green mark next to each event when the Pixel works.
- Check that the event arrives from both sources. To see server events, send a test code (test_event_code) with the Conversions API request. The Pixel’s Overview shows how many events Meta received, how many were matched to a user, how many were attributed to an ad and which connection method they came through. Events should appear within 20 minutes.
- Compare the name and the ID. Open a single event and check that the name and the ID are the same on the browser and the server event. If they differ, Meta cannot match the events.
- Remove the test code. test_event_code is for testing only and must not be in the production request.
I check events in test mode and on real user actions, not only by looking at the setup.
What happens with consent?
Meta’s consent logic is not the same as Google Consent Mode, so I check it separately. Adding the banner is not enough. I look at what the Pixel and the server events actually do before and after the visitor’s choice. For the Google side, read the article “Cookie Consent and Consent Mode”.
Do you need the Conversions API?
If the Pixel works, events fire at the right moment and Meta’s numbers match your own data, you do not need to add anything straight away. If Meta shows fewer purchases or enquiries than your data, first check whether the event fires at the right moment. Add a second way of sending events only after that. Server-side GTM is a separate step, covered in the article “Server-side GTM: when it pays off and when it doesn’t”.
As a next step, open Events Manager and make one test purchase or test form submission. Check whether the event arrives from both the browser and the server, and whether the name and the ID are the same. You can get a first overview of your measurement with the GA4 and GTM checklist. If you want someone experienced to look at your Meta measurement and campaign, see Meta ads management or the conversion tracking service.
Sources
- Meta for Developers: Deduplicate Pixel and Server Events
- Meta for Developers: Conversions API
- Meta for Developers: Using the Conversions API
- Meta for Developers: Conversions API parameters
- Meta for Developers: Server event parameters
- Meta for Developers: Meta Pixel
- Analytics Mania: Facebook conversion tracking with Google Tag Manager (additional source)
Facts checked against official documentation on 27 October 2026.
Richard Pikmets