Setting Up Meta Pixel & Conversions API Properly: The Tracking Base

You can run the best creatives in the world – if your tracking is broken, Meta’s AI optimises on a distorted picture and burns budget. Signal quality is the fuel of every automated campaign: it decides who the algorithm recognises as a buyer, how expensive your auctions get and whether your reports tell the truth. This article shows how to combine Meta Pixel and Conversions API properly, prevent duplicates cleanly and lift Event Match Quality to a level the AI can work with.

Pixel and Conversions API: two channels, one goal

The Meta Pixel is the classic route: a script in the browser reporting page views, carts and purchases. Its problem is its environment – ad blockers, browser privacy features and the iOS restrictions of recent years mean a relevant share of events simply never arrives.

The Conversions API (CAPI) reports the same events server-side – straight from your shop system to Meta, independent of what happens in the browser. It doesn’t replace the pixel, it complements it: the pixel provides browser context, the CAPI provides reliability. Only the dual setup gives the AI a complete picture – and that picture determines how well Meta can predict your next conversion. Patchy signals mean worse predictions and therefore more expensive auctions; the link to your costs is more direct than many think (more in our article on Meta Ads costs).

Deduplication: the heart of the dual setup

When pixel and CAPI both report the same purchase event, Meta has to recognise that it is one purchase – not two. That works via deduplication: both channels send the same event name and the same event_id. Meta then keeps the event that arrived first and discards the duplicate.

Sounds trivial, but it is the most common source of setup errors. Typical symptoms of missing deduplication: Ads Manager shows noticeably more purchases than your shop backend, ROAS figures look too good to be true, and the AI optimises on inflated numbers. So always check in pairs: if the pixel sends a “Purchase” with an event_id, the CAPI must send exactly the same “Purchase” with the same event_id – not “purchase”, not without an ID, not with its own logic.

Event Match Quality: make matching easy for the AI

Server-side events are only as valuable as Meta’s ability to match them to real people. That is exactly what Event Match Quality measures per event type in the Events Manager – as a rule of thumb, aim for a score above 7.

The lever is simple: send more parameters. Hashed email address, phone number and name lift the score the most; external IDs and click IDs help on top. Important: hashing is usually handled by your shop system or the integration – you don’t have to hand Meta plain-text data, but you do have to transmit the parameters at all. A setup that only sends an anonymous event_id gives away most of the CAPI’s benefit.

The four most common mistakes in practice

Purchase without value and currency. A purchase event without value and currency makes value-based optimisation and any ROAS analysis impossible. Check that both fields are filled consistently – including correct handling of discounts and shipping costs.

Content IDs that don’t match the catalogue. The IDs in your events must exactly match the IDs in your product feed. Otherwise dynamic retargeting breaks, and catalogue campaigns learn with the wrong products. This reconciliation belongs in every setup check.

Pixel and CAPI with different logic. If the browser fires on “add to cart” but the server only fires at checkout start, you create data gaps that no deduplication can heal. Both channels must send the same events for the same user action.

Tracking that bypasses consent. In the EU you need active consent for Meta tracking – and the CAPI is not a loophole, just another transport. Tie both channels to your consent management: no consent, no events, on any channel. Anything else isn’t a tracking setup, it’s a legal risk.

Setup and testing: how to proceed

For Shopify and Shopware, the native integrations take you most of the way – which settings actually matter is covered in our guide Setting up Meta Ads for Shopify & Shopware.

After the setup: test first, trust later. The test events tab in the Events Manager shows you live which events arrive via which channel and whether deduplication kicks in. Then check three control points: does every important event arrive via both channels? Is the Event Match Quality of your purchase events above the benchmark? And do the purchases in Ads Manager roughly match your shop backend? That last reconciliation is the most honest test of the whole setup.

Conclusion

Pixel plus Conversions API, clean deduplication via event_id, high Event Match Quality and consent coupling – that is the tracking base every Meta campaign stands on. It is unglamorous, but it decides the quality of everything that follows: optimisation, scaling, reporting. That is exactly why our work as a Meta Ads agency almost always starts with tracking – and in the free account check we look at precisely this base alongside your campaigns.