# Conversion API (CAPI)

The **Conversion API** is Meta’s server-side tracking system that sends **real conversion data** (messages, bookings, purchases, payments) **directly from your system to Meta**.

Instead of relying only on browser cookies or the Facebook Pixel, which can be blocked, deleted, or restricted; CAPI sends important conversion events directly from your backend or CRM to Meta.

This solves a major problem:

* Browser tracking is unreliable
* iOS updates block pixels
* Cookies expire or get rejected

CAPI ensures Meta understands **what actually converts**, not just who clicked.

<figure><img src="/files/F5kp55jrRjFz6QXVrf2r" alt=""><figcaption><p><em>Source: Official Facebook</em></p></figcaption></figure>

{% embed url="<https://developers.facebook.com/docs/marketing-api/conversions-api/business-messaging>" %}

### Trackable Events by CAPI -

* Purchases
* Leads & registrations
* Bookings & appointments
* Offline sales
* WhatsApp-driven conversions
* CRM updates (e.g. qualified leads, repeat purchases)

All of this flows securely and privately, to Meta from your system.

<details>

<summary>The Difference between Facebook Pixel and Conversions API</summary>

The [Facebook Pixel](/facebook-advertising-strategy/metas-pixel-optimization-guide.md) and Conversions API are both tools provided by Meta to help advertisers track user interactions and measure the effectiveness of their advertising campaigns. However, they differ in their functionality, implementation, and use cases:

| Event-based Action | FB Pixel | Conversions API |
| ------------------ | :------: | :-------------: |
| Initiate Checkout  |     ✅    |        ✅        |
| Add Payment Info   |     ✅    |        ✅        |
| Purchase           |     ✅    |        ✅        |
| Lead               |     ✅    |        ✅        |
| Registration       |     ✅    |        ✅        |
| Contact            |     ✅    |        ✅        |
| Page View          |     ✅    |        ✅        |
| View Content       |     ✅    |        ✅        |
| Search             |     ✅    |        ✅        |
| AddToCart          |     ✅    |        ✅        |
| AddToWishlist      |     ✅    |        ✅        |
| Cancelled Order    |          |        ✅        |
| LeadScore          |          |        ✅        |
| Offline Purchase   |          |        ✅        |
| Completed Order    |          |        ✅        |

The **Pixel** is ideal for tracking website activity and attributing conversions to specific ad campaigns, while the **CAPI** provides a more robust solution for tracking offline events, cross-device conversions, and other non-website interactions. Advertisers may choose to use one or both of these tools depending on their tracking needs and objectives.

</details>

***Remarks:** Starting with Graph API version 17 onwards, released on May 23, 2023, Offline Conversions API will no longer support offline events. We anticipate that the Offline Conversions API will be discontinued in the third quarter of 2024. We recommend that advertisers with Offline Conversions API integrations convert their integration into a Conversions API integration and do not update their Offline Conversions API until they have successfully done so.*

### Why Conversion API Matters (Especially in 2026)

Without CAPI:

* Ads optimize for clicks, not results
* Meta’s algorithm lacks learning signals
* Your cost per lead increases over time

With CAPI:

* Meta learns which conversations turn into revenue
* Campaigns self-optimize toward high-value users
* ROAS improves consistently

For small businesses, this means **smarter spend, not bigger budgets**.

### How CTWA + Conversion API Work Together

This is where real growth happens.

#### A Simple Example Flow

1. User sees a CTWA ad on Instagram
2. Clicks → opens WhatsApp chat
3. Starts a conversation
4. Books an appointment or makes a payment
5. Conversion event is sent via CAPI to Meta
6. Meta optimizes ads toward similar high-intent users

Instead of guessing, your ads now learn from **real business outcomes**.

### When Should Small Businesses Start Using CTWA & CAPI?

You should consider CTWA + CAPI if:

* You’re already getting inquiries via WhatsApp
* You want better-quality leads, not just more leads
* You’re spending on ads but can’t measure real ROI
* You want to scale without hiring more staff

CTWA isn’t a “later-stage” tool but a **foundation** for sustainable growth.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.islash.io/features/ctwa-and-conversion-api/conversion-api-capi.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.