Meta Conversions API (CAPI): Setup, Deduplication, and Why You Still Need the Pixel

Do You Need the Meta Conversions API?

The short answer is yes, for almost every advertiser. The table below gives you the specific answer for your setup.

Drowning in Meta Ads?

Put your campaign on autopilot with Nova.

Read more

What the Meta Conversions API Is (and What It Isn't)

The Meta Conversions API (CAPI) is a server-to-server integration that sends conversion event data directly from your server to Meta, without relying on the user's browser.

You may have heard that the Meta Conversions API replaces the Facebook Pixel. It doesn't. Disabling the Pixel after implementing CAPI removes browser-side matching signals. Based on how Meta's deduplication model works, this degrades rather than improves attribution because you've eliminated one of two independent measurement paths instead of adding a second.

Here's how the two systems work:

The Meta Pixel fires from the user's browser when a user takes an action: viewing a product, initiating checkout, or completing a purchase. It captures data client-side, which means it's subject to browser restrictions, iOS privacy controls, ad blockers, and ITP (Intelligent Tracking Prevention in Safari).

The Meta Conversions API (CAPI) fires from your server when a conversion event occurs. It sends the same data directly to Meta's API, bypassing the browser entirely. A server-to-server signal can't be blocked by browser extensions or iOS ATT.

Why you need both: When both signals fire for the same event, Meta deduplicates them server-side using the event_id parameter, so the conversion is counted once, not twice. The result is more complete conversion data than either signal provides alone, and your ROAS becomes more accurate because the learning algorithm has better signal to optimize against.

Pixel and CAPI are redundant measurement paths, not alternatives. Think of them as two independent witnesses to the same conversion event. Having both consistently yields more complete data than either signal alone.

The 'facebook conversions api' and 'capi meta' terms refer to the same system. Meta rebranded from Facebook to Meta in 2021, but the underlying API and Events Manager interface use both names.

New to Meta Ads tracking? Start with the complete guide to setting up Meta Ads for the full foundation, then follow how to set up the Meta Pixel first. The Conversions API works alongside the Pixel rather than replacing it.

Why CAPI Exists: The Browser Signal Problem

Browser-only tracking is increasingly unreliable for three compounding reasons:

Pixel-only accounts are systematically undercounting conversions. CAPI is a primary server-side fix that recovers many browser-blocked events. Combine it with first-party data, clean tagging, and Advanced Matching for best results. Other mitigations (consented CRM uploads, attribution modeling) also help, but CAPI is the most direct structural solution.

How to Set Up the Meta Conversions API

There are three setup paths depending on your platform. Use the one that matches your stack.

Conversions API on Shopify (Native Integration)

Shopify's native Meta integration handles conversions api shopify setup automatically once connected. No developer required.

CAPI on WooCommerce (Plugin-Based)

Direct Server-Side Integration (Custom / Headless)

For custom checkout systems, headless commerce setups, or events beyond standard e-commerce, this is the facebook capi integration path for developers.

Event Match Quality: What Score You Need

Event Match Quality (EMQ) is Meta's score (0-10) for how well your customer signals match Meta user profiles. Higher EMQ = more conversions attributed = more accurate signal for the algorithm.

How to improve EMQ:

• Pass SHA-256 hashed email with every event where available
• Pass hashed phone number where customers provide it at checkout
• Pass first name, last name, and zip code for purchase events
• Enable Advanced Matching in Meta Pixel settings (browser-side)
• Use CAPI to send these parameters even when browser signals are blocked

Where to check: Meta Events Manager, your dataset, Event Match Quality column

Deduplication: How Meta Prevents Double-Counting

When both Pixel and CAPI fire for the same conversion, Meta counts it once. This works via the event_id parameter, a unique identifier you generate for each event.

Purchase occurs
       |
       +---> Pixel fires (browser)     --+
       |     event_id: "order_12345"     +--> Meta matches event_id --> 1 conversion
       +---> CAPI fires (server)        --+
             event_id: "order_12345"

Symptoms of a deduplication failure

• Conversion counts in Meta are significantly higher than actual orders
• ROAS looks unexpectedly strong while profit doesn't match
• Events Manager Activity Log shows near-identical duplicate events

In Meta Events Manager, check the Diagnostics tab. It flags duplicate events if deduplication is failing. Cross-reference your Meta-attributed conversions against your actual platform order volume as a sanity check.

The failure that looks like good news

Notice what separates this symptom list from every other tracking problem. A broken pixel shows up as a drop, and a drop prompts questions. A deduplication failure shows up as a rise: more conversions, stronger ROAS, a campaign that suddenly looks like it deserves more budget. Nobody opens Diagnostics to investigate a number that improved. The cross-check described above, Meta-attributed conversions against actual order volume, is the thing that catches it, and it is a manual check nobody has scheduled for the week it finally matters.

Running that check on a schedule is one of Nova's standing jobs. Nova is AdAdvisor's AI media buyer for Meta, and she audits your pixel, your server events, and your event match quality on a recurring basis rather than whenever someone remembers to look. Because she also holds your break-even ROAS, margins, and average order value from onboarding, a reported return that climbs while the underlying economics stay flat is exactly the kind of discrepancy she is built to raise rather than act on. In Suggest mode every action she proposes waits on your approval before it runs. Once she has earned it, Autopilot executes inside the spend caps, geographies, and exclusions you set and pings you only when she hits something she cannot decide alone.

Access to Nova is by application while the founding cohort onboards.

How to Verify CAPI Is Working

After setup, confirm CAPI is firing correctly before trusting your attribution data.

Common CAPI Problems and Fixes

How Do You Send Offline Conversions and CRM Events to Meta?

There is no separate Offline Conversions API anymore. Offline and CRM conversions now go through the regular Conversions API to a dataset, with an action_source value that tells Meta where each conversion happened.

Meta retired the standalone Offline Conversions API in May 2025, and offline event sets gave way to datasets. Meta's offline events documentation now calls the Conversions API its recommended method for sending offline and physical store events, and lists the old Offline Conversions API as a legacy integration.

In practice, every event type now uses one endpoint: POST /{DATASET_ID}/events. In-store sales go in with action_source set to physical_store. CRM lead-stage events for Conversion Leads go in with system_generated.

Why the label matters: action_source is how Meta tells a server copy of a website purchase apart from a sale that happened at a till, on a call, or inside your CRM. Meta requires event_source_url for website events sent through the Conversions API, so a store sale labelled website either fails that requirement or carries a URL where nothing happened. A mislabelled source likely leaves offline revenue counted as web revenue, which skews any channel-level ROAS comparison.

Which action_source Value Should You Use?

Pick the value that describes where the conversion happened, not where the data came from. Meta's Server Event Parameters reference lists nine values:

How Do You Send CRM Conversions to Meta?

CRM conversions go to Meta as a separate Conversions API integration built for lead generation. Meta's CRM integration guide keeps it apart from your website setup because the required parameters differ and the data comes from your CRM rather than your web servers.

Per Meta's payload specification, each CRM event needs action_source set to system_generated, a lead_event_source naming your CRM, and event_source set to crm. Meta recommends storing the 15 to 17 digit Meta Lead ID and sending it with every event. Without it, send identifiers such as hashed email or phone.

Two timing rules catch most broken CRM integrations. The event_time can be at most 7 days before you send the event, and it has to fall after the lead was created, or Meta may discard it.

{
  "event_name": "qualified_lead",
  "event_time": 1761040800,
  "action_source": "system_generated",
  "user_data": {
    "lead_id": 1234567890123456
  },
  "custom_data": {
    "lead_event_source": "Salesforce",
    "event_source": "crm"
  }
}

For the funnel side of this setup, including which lead stages to send and how qualified-lead signals feed optimization, see our guide to AI lead generation for Meta ads.

Still on Offline Event Sets? How to Migrate to a Dataset ID

If an integration still posts to an offline event set through the old Offline Conversions API, it has most likely not delivered events since May 2025. The fix is to send the same events to the Conversions API under a dataset ID. Zapier, for example, retired its Facebook Offline Conversions app and moved users to its Conversions apps with a Physical Store action source and a new Dataset field (Zapier's notice).

How Late Can You Upload an Offline Conversion?

Meta's documentation gives more than one number here, so check the current docs for your event type before you set an upload schedule. The figures below are what Meta's pages said when we checked them in October 2026. Daily uploads, which Meta recommends, keep you inside all of them.

The same offline and CRM data can also feed audiences: Meta notes that every action_source value supports both measurement and custom audience creation. Building audiences from customer data is covered in our guide to Facebook Custom Audiences, while this page stays on the measurement side.

CAPI Setup Checklist

Before trusting attribution data after CAPI implementation, verify all of the following:

• Meta Pixel installed and firing on all key pages (confirmed in Test Events)
• CAPI enabled for your platform (Shopify Maximum, WooCommerce plugin, or direct API)
• event_id matching between Pixel and CAPI for every conversion event
• SHA-256 hashed email passed with every purchase event
• Hashed phone number passed where customers provide it
• Event Match Quality score 7+ on Purchase events in Events Manager
• No warnings in the Events Manager Diagnostics tab
• Both browser and server event rows visible in Test Events for the same conversion
• Attributed conversions within 10-15% of actual order volume under a 1-day click window
• Offline and CRM events sent to your dataset with the correct action_source (physical_store for store sales, system_generated for CRM lead stages)

Summary

The Meta Conversions API is a complementary tracking signal, not a Pixel replacement. Setting up both, with correct event_id deduplication, gives Meta the most complete conversion data available and improves the algorithm's ability to optimize your spend. For advertisers using AI-assisted tools like AdAdvisor, CAPI health is a prerequisite: automated budget and bidding recommendations depend on accurate ROAS data, which depends on accurate attribution. Weak CAPI health produces unreliable ROAS, which makes any AI-driven recommendations untrustworthy. Offline and CRM conversions run through the same API: send them to your dataset with the right action_source, physical_store for store sales and system_generated for CRM lead stages, and upload daily because Meta's documented windows differ.

AdAdvisor monitors Pixel and CAPI health as part of its account-level tracking diagnostics, flagging attribution signal issues before they affect your budget decisions.

Sources

• Meta for Developers: Server Event Parameters (Conversions API)
• Meta for Developers: Sending Offline Events Using the Conversions API
• Meta for Developers: Conversions API for CRM integration
• Meta for Developers: Conversions API for CRM integration, Payload Specification
• Meta Business Help Center: Best practices for offline events data
• Meta Business Help Center: Decide which dataset creation option is right for your business
• Zapier Help Center: Changes impacting Facebook Offline Conversions users