Back to ResourcesMeta CAPI Guide

What Is Meta Conversions API (CAPI) and How Does It Work?

A plain-language explanation of Meta's Conversions API, why advertisers use it, and how it fits into a lead-driven sales process.

Last updated: August 29, 2026

What Is Meta Conversions API?

Meta Conversions API (CAPI) is a way for a business's own server — not just a visitor's browser — to send event data directly to Meta. Instead of relying only on the Meta Pixel (which runs in the browser and can be blocked or limited), CAPI lets your backend tell Meta directly: "this person took this action."

Why Does Meta Conversions API Matter for Advertisers?

Browser-based tracking has real limits — ad blockers, cookie restrictions, and privacy features in modern browsers all reduce what a Pixel alone can see. Many meaningful actions also just don't happen in a browser at all: a WhatsApp inquiry, a sales conversation that closes days later, a purchase confirmed over a phone call. CAPI gives advertisers a way to report those events too, from wherever the record of them actually lives — typically a CRM or backend system.

How Does Meta CAPI Work?

A server sends an event to Meta's Graph API, identifying the event (its name, timestamp, and a unique event ID) along with hashed customer match parameters — like an email or phone number run through SHA-256 hashing, never the raw value — so Meta can match the event to the right ad account and, where applicable, deduplicate it against any matching browser-side event.

What Events Can Be Sent to Meta via CAPI?

Meta supports a range of standard event names (leads, purchases, registrations, and others) as well as custom events. Which ones a given business actually sends depends on what that business tracks and at which stages of its own funnel.

How Sale2x Uses Meta Conversions API

Sale2x sends a Conversions API event automatically whenever a lead's status changes in the CRM. There are five event types, mapped to lead status: Lead (captured), Contact (contacted), QualifiedLead (qualified), Purchase (converted), and LeadLost (lost). Each event is sent server-side with SHA-256-hashed match data, and requires a connected Meta ad account and Pixel. This gives Meta real downstream signal about which leads actually became customers — not just who clicked an ad — which can provide additional conversion signal for advertising measurement and optimization. It doesn't guarantee a specific cost or performance outcome; actual results still depend on your account, audience, and campaign setup. See the full platform capabilities.

Getting Started

To use Meta Conversions API through Sale2x, connect your Meta ad account and start managing leads in the CRM — see how the whole workflow fits together in how it works, or create a free account.