Skip to content
Bach.ai

Guide · Updated

How do the Meta Pixel and Conversions API work together?

Short answer

Run both, and make Meta count each purchase once. The Pixel records events in the browser; the Conversions API sends them from your server, which browser errors and ad blockers affect less. When both send the same purchase, give them the same event_name and event_id so Meta deduplicates it, then check Event Match Quality in Events Manager.

Ads Manager's conversion counts, and the signal Meta optimizes on, come from the events your Pixel and server send. When both send the same purchase without deduplication, Meta may count it twice and your conversion numbers run high. Event Match Quality, a score from 0 to 10 based on the last 48 hours of server events, shows how well those events match to Meta accounts. Start with the three posts below, then go to the question that fits your setup. For definitions of CAPI, deduplication and the Pixel, see the Meta ads glossary.

Start here

  1. How do I diagnose duplicate events between pixel and CAPI?

    A ledger keyed on event name and ID for finding duplicate Pixel and CAPI events.

  2. Should events come from the browser or the server?

    Which events should come from the browser, which from the server, and the key that joins them.

  3. Why is my Meta pixel not firing on Shopify?

    Five steps for a pixel that isn't firing on Shopify, including how to remove a duplicate pixel safely.

How do I set up the Conversions API?

Why are my events duplicated, missing or not firing?

Is my tracking good enough to optimize on?

Does my store platform set up Pixel and CAPI properly?

Sources: About Conversions API, About deduplication for Meta Pixel and Conversions API events, About event match quality (checked 1 October 2026).

Last updated

See what your Meta ads are really costing you.

Connect your account and Bach ranks potential revenue leaks with estimates and actions you can review. Free for 7 days, no credit card.

Start Free Audit
Start your free audit