How Do You Track Conversions on Facebook and Meta Ads?

You track conversions on Facebook and Meta Ads by running two methods together: the browser-based Meta Pixel and the server-side Conversions API (CAPI), matched by a shared event_id so Meta counts each conversion once instead of twice. Meta's own documentation recommends this dual setup rather than either method alone, because browser tracking alone misses a meaningful share of real conversions.

Why the Pixel Alone Isn't Enough

The Meta Pixel is a JavaScript snippet that fires in the visitor's browser when they complete a tracked action — a purchase, a lead form submission, a signup. It's the standard starting point for any Meta Ads account, but it depends on the browser actually loading and executing that script. Ad blockers, Safari's Intelligent Tracking Prevention, iOS App Tracking Transparency prompts, and shortened cookie lifespans all interfere with that signal.

What the Conversions API Adds

The Conversions API sends the same event data as a direct server-to-server call instead of a browser request, so it isn't affected by browser-level blocking. It pulls conversion events from your web server, ecommerce platform, or CRM and posts them straight to Meta using your Pixel ID and an access token generated in Events Manager. Running Pixel and CAPI together and deduplicating them recovers roughly 20-30% of conversion data that browser-only tracking loses, according to 2026 implementation guidance. Meta itself calls this combination the standard for accurate attribution and, as of 2026, offers a one-click setup inside Events Manager that connects a dataset without custom code.

Setting It Up

Create a pixel. In Meta Business Suite, open Events Manager, select "Connect a new data source," and choose Web.

Retrieve the Pixel ID. Click into the new pixel's details page to copy the numeric Pixel ID you'll need for both the browser and server-side setup.

Generate a CAPI access token. Still inside Events Manager, generate the API access token tied to that same pixel.

Send matching events from both sources. Fire each tracked action — purchase, lead, add-to-cart — from the Pixel and, separately, from your server via CAPI.

Avoiding Double-Counted Conversions

Running both methods on the same event without matching them creates duplicate counts — Meta logs the purchase once from the browser and once from the server, inflating reported conversion volume and understating true cost per conversion. Meta deduplicates events by matching the event_name and event_id fields exactly across the two sources within a 48-hour window; if either field is missing or doesn't match, both events are counted separately. Getting that event_id generated once and passed identically to both the Pixel call and the CAPI call is the single most common point of failure in a dual setup.

Bottom Line

Start with the Meta Pixel if you have no tracking in place yet, then add the Conversions API as a second layer covering the same events rather than a separate tracking plan, and confirm every event carries a matching event_id before trusting your combined conversion count. If your reported conversion volume jumps sharply right after adding CAPI, check deduplication first — a spike that size usually means events aren't matching correctly, not that server-side tracking recovered that much previously invisible volume overnight.

Sources: Meta for Developers' Conversions API and Meta Pixel documentation; implementation and deduplication detail from Stape, Cometly, and Adsuploader's 2026 coverage of Pixel + Conversions API setup.