What are the Meta Pixel and Conversions API?
The Meta Pixel is a snippet of code on your website. When someone views a page, adds to basket or sends an enquiry, it reports that event to Meta from their browser.
The Conversions API, often called CAPI, does the same job from your server, or from a platform such as your shop or CRM. Because it doesn't rely on the visitor's browser, it can report events the Pixel misses, including ones that happen offline, such as a sale closed by phone.
Why use both?
Because each covers gaps in the other. Browser tracking can be blocked by ad blockers, browser privacy settings and slow page loads. Server tracking doesn't see everything the browser does, such as some on-page actions.
Together they give Meta a fuller picture of who converts. That helps it show your ads to more people likely to act, and gives you more accurate reporting. Meta recommends running both.
How does deduplication work?
When the Pixel and the Conversions API both report the same purchase, Meta needs to know it's one purchase, not two. You tell it by sending the same event name and the same event ID from both.
Meta then keeps one and drops the duplicate. If the IDs don't match, you'll see inflated conversions, and Meta will optimise on numbers that aren't real. Checking deduplication is one of the first jobs after set-up.
What is Event Match Quality?
Event Match Quality is a score in Events Manager that shows how well the customer information sent with your server events matches people's Meta accounts. Higher match quality means Meta can link more conversions to the ads that caused them.
You improve it by sending more of the details Meta accepts, such as email address and phone number, which are hashed before sending so they aren't passed as plain text. Only send what you're allowed to under your privacy policy and consent set-up.
How do you set up the Meta Pixel and Conversions API?
Follow these steps in order. Most of it can be done in an afternoon with the right access.
- In Events Manager, create a dataset (your Pixel) inside your business portfolio.
- Install the Pixel on every page, through your platform's integration, a tag manager or the code itself.
- Pick your key events: usually Lead, Purchase, or a booking, plus page views.
- Set up the Conversions API. Shopify, WooCommerce and many other platforms have a built-in integration. Otherwise use the Conversions API Gateway or a direct server set-up.
- Send the same event name and event ID from both, so Meta can deduplicate.
- Include the customer details you're allowed to send, hashed, to raise Event Match Quality.
- Make sure both respect your cookie consent choices.
- Use the Test Events tool to check each event arrives once, from both sources.
- Compare Meta's conversion counts with your own orders or enquiries for a week.
Do you still need cookie consent with the Conversions API?
Yes, in practice. In the UK, PECR rules from the ICO require consent for non-essential cookies and similar tracking on people's devices, and UK GDPR applies to any personal data you send to Meta.
Moving tracking to your server doesn't remove those duties. Set both the Pixel and the Conversions API to follow the visitor's consent choices, and say in your privacy policy what you share and why. If in doubt, take advice.
How do you check your tracking is working?
Look in three places. Test Events shows events arriving in real time while you click through your site. Diagnostics in Events Manager flags problems such as missing parameters or duplicate events. And your own records, orders or enquiries, should roughly match what Meta reports.
Check again after any website change, new plugin or platform move. Tracking breaks quietly, and nobody notices until results drop.