Meta Conversions API

The Meta Conversions API (CAPI) is a server-side interface that lets businesses send conversion events directly to Meta — independent of browser cookies and pixel tracking. Since iOS 17 broke much of client-side signal collection, CAPI has become the most important data source for Meta ad optimization, especially for Click-to-WhatsApp Ads.

What is the Meta Conversions API?

The Meta Conversions API (CAPI, formerly Server-Side API) is an official interface that allows businesses to send conversion events directly from their server to Meta. Classic tracking runs through the Meta Pixel in the user's browser; CAPI runs server-side and is therefore unaffected by cookies, ad blockers, or browser restrictions.

Since iOS 17 and the gradual sunset of third-party cookies, pure pixel implementations typically lose 20–40% of tracking accuracy. Meta optimizes ad delivery based on incoming conversion signals — without CAPI, the algorithm learns significantly worse, which measurably reduces campaign performance.

How does CAPI work?

User action: A lead is qualified, an appointment booked, or a purchase completed — on your platform, in your shop, or in your Unified Inbox.
Server event: Your system creates an event object with event name (e.g. Lead, Purchase), timestamp, hashed user data (email, phone), and the original click ID of the ad.
Sent to Meta: The event is posted via HTTPS to Meta's CAPI endpoints.
Attribution & optimization: Meta matches the event to the originating ad via the click ID and uses the signal for lookalike audiences, bid optimization, and reporting accuracy.

CAPI for Click-to-WhatsApp Ads

For Click-to-WhatsApp Ads, CAPI is especially valuable. Since the conversion (lead, appointment, sale) happens in WhatsApp rather than in the browser, the classic pixel cannot capture the event. The only way to signal Meta that a conversation closed in business is a server-side event via CAPI.

Four standard events are worth tracking for CTWA funnels:

Lead — after successful qualification by the bot or first response from the team
Schedule — after appointment booking via WhatsApp
AddToCart — when the chat leads to a cart action
Purchase — for completed purchases, ideally with the actual revenue value

CAPI requires personally identifiable data (email, phone, first name) to be hashed before transmission — typically with SHA-256. Meta matches hashes against its own data without ever receiving plaintext.

From a GDPR perspective the data chain still requires notice and consent: privacy policies must list the CAPI integration with Meta Inc. (USA), and cookie banner logic should include server triggers if they are coupled to browser actions. The full framework is covered in the GDPR-compliant messaging glossary.