Meta Pixel vs Conversions API: Differences and Setup

Facebook & Instagram ads · Tracking

Meta Pixel and
Conversions API.

The Meta Pixel is code in the visitor’s browser that reports actions such as purchases and leads to Meta. The Conversions API sends the same events from your server, so more of them arrive when browsers, ad blockers or privacy settings stop the Pixel. Use both together, with the same event name and event ID so Meta counts each event once, and test them in Events Manager. Malta Digital checks the Pixel and Conversions API on every Meta ads account we take on.

Malta Digital blog: Meta Pixel and Conversions API.  Set up and checked.
Purchase · deduplicatedBrowser + server, same event ID

Short answer

The Meta Pixel reports website actions such as purchases and leads from the visitor’s browser; the Conversions API sends the same events from your server, so more arrive when browsers or ad blockers stop the Pixel. Use both, with the same event name and event ID so Meta counts each once, and test them in Events Manager. Malta Digital checks this on every account it takes on.

Key takeaways

  • What is the difference between the Meta Pixel and the Conversions API? The Pixel sends events from the visitor’s browser; the Conversions API sends them from your server or platform. Meta recommends using both.
  • Do I need the Conversions API if I have the Pixel? It is strongly recommended, because the Pixel alone misses events blocked by browsers, ad blockers and privacy settings.
  • What is event deduplication? Sending the same event name and event ID from the Pixel and the server, so Meta counts each purchase or lead once.

The short answer

Why tracking decides how well your ads do.

Meta does not just report your results. It learns from them. Every purchase, lead or booking your website reports tells Meta what kind of person converts, and it uses that to find more people like them. If half your sales never reach Meta, the campaign learns from half the data, looks worse than it is, and spends your budget less well.

The Meta Pixel and the Conversions API are the two ways your website reports those results. The Pixel runs in the visitor’s browser. The Conversions API, often shortened to CAPI, runs on your server or platform. Meta recommends using both, because each covers gaps in the other.

In Events Manager, the Pixel and the Conversions API now sit together in what Meta calls a dataset: one place that receives events from your website, server, app or CRM. If you see “dataset” where you expected “pixel”, it is the same thing with a broader name.

Diagram: a website visitor action sent by the Meta Pixel from the browser and by the Conversions API from the server, deduplicated by Meta, then used for reporting and optimisation
How the Pixel and the Conversions API work together.

The Pixel

What the Meta Pixel does.

The Pixel is a small piece of JavaScript on your website. When someone views a page, adds to cart, starts checkout, submits a form or buys, it sends an event to Meta, with details such as the value and currency of a purchase. Meta uses those events to report results in Ads Manager, to build retargeting audiences, and to optimise delivery towards people likely to take the same action.

The standard events most businesses need are PageView, ViewContent, AddToCart, InitiateCheckout and Purchase for shops, and Lead, Contact, Schedule or CompleteRegistration for service businesses. Use Meta’s standard event names where they fit, because Meta understands them, and add custom events only for things the standard list does not cover.

The Pixel has a weakness: it depends on the browser. Ad blockers, browser privacy features, iOS settings and cookie choices can stop events reaching Meta. Each missed purchase is a sale your campaign cannot learn from.

The Conversions API

What the Conversions API adds.

The Conversions API sends events from your server, your shop platform or a gateway directly to Meta. It does not depend on the visitor’s browser, so it fills many of the gaps the Pixel leaves. It can also send events that never happen on a website at all, such as a lead from your form that later became a paying customer in your CRM.

Events sent through the Conversions API can include customer details such as an email address or phone number, which Meta hashes and uses to match the event to a person on Facebook or Instagram. The better the match, the more useful the event. Events Manager shows this as Event Match Quality for each event, and it is worth checking.

The Conversions API does not get around consent. If a visitor has not agreed to marketing tracking under your cookie and privacy setup, the server should respect that choice too. Agree with whoever runs your website how consent is passed to both the Pixel and the server.

Meta Pixel vs Conversions API, summarised from this article
Meta PixelConversions API
Where it runsIn the visitor’s browserOn your server, platform or a gateway
Blocked byAd blockers, some browser privacy settings, consent choicesNot by the browser; still subject to consent and Meta’s data rules
SetupA code snippet or platform integrationA platform integration, the Gateway, or a developer
Offline and CRM eventsNoYes, for example a lead that became a customer
DeduplicationSends event name and event IDSends the same event name and event ID

Setup

How to set it up on your website.

Shopify and WooCommerce: use the official Meta integration for your platform. It installs the Pixel and sends server events through the Conversions API, with deduplication built in. Choose the strongest data-sharing setting your consent setup allows. Our guide to Facebook ads for online shops covers the rest of the shop setup.

WordPress, Wix and other builders: use the official Meta integration or a well-supported plugin where one exists, connect it in Events Manager, and check that the events you need are actually sent. Custom websites: add the Pixel to your pages and send server events through the Conversions API from your backend, or use the Conversions API Gateway, which Meta offers as a simpler hosted option.

Whatever the platform, fire the conversion on the right step: a Purchase on the order confirmation, a Lead when the form is successfully submitted, not when the page loads. And send the value and currency correctly, deciding once whether values include VAT and delivery, so your return on ad spend means what you think it means.

Deduplication

Deduplication: counting each event once.

When the Pixel and the Conversions API both report the same purchase, Meta needs to know it is one purchase, not two. That is deduplication. It works when the browser event and the server event carry the same event name, such as Purchase, and the same event ID, usually the order number or a unique ID generated when the action happens.

If deduplication is missing, purchases can be counted twice, your ROAS looks better than it is, and Meta optimises on wrong data. If the IDs never match, Events Manager will show a deduplication warning. Platform integrations handle this for you; custom setups need a developer to pass the same ID to both.

Not sure your tracking is right?

Apply now and send us your website. We’ll check your Pixel, Conversions API and deduplication and tell you what we’d fix first. Free, no obligation.

Proof

€573,222 in tracked sales.

From 1 January to 28 May 2026, an online store we ran ads for spent €95,470.88 on Facebook and Instagram. Meta Ads Manager tracked 9,085 website purchases worth €573,222.05, an average ROAS of 6.00.

Meta Ads Manager screenshot: €95,470.88 spent, €573,222.05 tracked sales
Real Ads Manager screenshot. Cost per purchase blurred. Tracked purchase value is not profit. All case studies.

Want tracking set up properly so results like this are measured? Contact us

Health and finance

Clinics and finance sites: data restrictions.

If your website is about health, wellness or financial services, Meta may restrict what your Pixel and Conversions API can share. Meta calls this Core Setup. In practice it removes custom parameters and most of the page address beyond your domain from events, which can limit how specific your conversion events and audiences can be. Sending events from the server does not avoid it.

You can check whether this applies in Events Manager, in your dataset’s settings, under data restrictions. If it does, keep conversion tracking simple, use standard events on clear thank-you pages, and never put health or financial details in a page address, event or parameter. Clinics in Malta should read our guide to Facebook ads for clinics alongside this.

Check it

How to check it works.

Install the free Meta Pixel Helper extension for Chrome and browse your site: it shows which Pixel events fire on each page and flags errors. In Events Manager, open Test Events and watch browser and server events arrive in real time as you go through the site. Then place a real test order or submit a real enquiry and confirm it appears once, with the right value and currency.

After that, check Events Manager every week or two, and always after a website change. A new theme, a checkout update or a cookie banner change can quietly stop events. Look for warnings, falling event counts and Event Match Quality. In Ads Manager, the results column should roughly match the orders or enquiries you actually received.

For your own analytics, the Pixel is not enough. To see Meta traffic in Google Analytics, tag your ads with UTM parameters, as explained in our guide to Facebook ads UTM parameters.

Common mistakes

Common tracking mistakes.

Purchases counted twice because deduplication is missing. Values sent including VAT and delivery without anyone realising. A Lead event firing when the form page loads instead of when it is sent. Two different Pixels on the same site sending events to two accounts. A cookie banner that blocks the Pixel with no server-side setup. And nobody checking Events Manager after a website update.

The most expensive one is optimising for the wrong event. If your campaign uses the Sales objective but the Pixel only reports page views, Meta has nothing useful to learn from. Our guide to Facebook ads objectives explains how the objective and the tracked event fit together.

A few straight answers

What you might be wondering.

What is the difference between the Meta Pixel and the Conversions API?

The Pixel sends events from the visitor’s browser; the Conversions API sends them from your server or platform. Meta recommends using both.

Do I need the Conversions API if I have the Pixel?

It is strongly recommended, because the Pixel alone misses events blocked by browsers, ad blockers and privacy settings.

What is event deduplication?

Sending the same event name and event ID from the Pixel and the server, so Meta counts each purchase or lead once.

How do I test the Meta Pixel?

Use the Meta Pixel Helper extension and Test Events in Events Manager, then place a real test order or enquiry and check it appears once.

How do I install the Meta Pixel on Shopify, WordPress or Wix?

Use the platform’s official Meta integration where one exists, connect it in Events Manager, then check the events with Test Events and the Meta Pixel Helper.

What is a dataset in Events Manager?

Meta’s name for the place that holds your Pixel and Conversions API events, plus any app or offline events, in one source.

Why are my Pixel events restricted?

If Meta classifies your site as health, wellness or financial services, it may apply Core Setup, which limits what events can share. Check the data restrictions in Events Manager.

Can Malta Digital set up my Pixel and Conversions API?

Yes. We check and fix tracking on every account we manage. Meta ads management starts from €1,249 a month plus ad spend.

A useful first step

Ready for tracking you can trust?

We set up and check the Pixel and Conversions API, fix deduplication and keep an eye on Events Manager while we run your ads. Meta ads management from €1,249 a month plus ad spend.

Apply now for Meta ads management