Meta Pixel vs Conversions API: do you need both?

Short answer: use both. They catch different things, and with a shared event ID Meta counts each conversion once.

What each one does

	Meta Pixel (browser)	Conversions API (server)
Runs in	The visitor’s browser	Your WordPress server
Stopped by ad blockers	Often	No
Affected by browser cookie limits	Yes	No
Sees page views and on-site behaviour	Yes	Only the events you send
Sends events without a page load	No	Yes – e.g. an order completed later
Needs Marketing consent in Omea	Yes	Yes

The pixel gives Meta the browser context it uses for optimisation and audiences. The Conversions API makes sure the conversions themselves arrive. Running both is what Meta calls a redundant setup.

How double counting is avoided

Each conversion gets one event ID. Omea sends it as the pixel’s eventID and as the Conversions API’s event_id. When Meta receives the same event name with the same ID from both, it keeps one. For WooCommerce purchases the ID is wc-order-<order id>, so a reloaded thank-you page doesn’t create a second purchase either.

When the server copy matters most

• Ad blockers stop the pixel but not your server.
• Visitors who leave fast – they close the tab before the pixel has sent the event.
• Server-side events – a WooCommerce order or a sign-up that the server records without relying on the browser.

With consent, always

Neither channel is a way around the cookie banner. In Omea Consent Pro, the pixel loads only after Marketing consent (or in Meta’s own consent mode), and the Conversions API checks Marketing consent on your server before every event.

Set it up: Meta Conversions API on WordPress without sGTM.