> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Meta Conversion

> Report conversion events to Meta's Conversions API to measure the return on your Click-to-WhatsApp ads.

The **Meta Conversion** node sends a conversion event (for example, a purchase or a lead) to **Meta's Conversions API** from your flow. This lets Meta know which Click-to-WhatsApp ads deliver results so you can measure their return on investment.

> [card] [Meta documentation](https://developers.facebook.com/docs/marketing-api/conversions-api/business-messaging)
>
> Conversions API for Business Messaging.

***

## When to use it

Place it at the point in the flow where the conversion happens. Common cases:

* Purchase or payment confirmation
* Qualified lead registration
* Appointment or demo scheduling
* Subscription or trial start

## Requirements

* WhatsApp channel connected through **WhatsApp Cloud API** (sandbox and other providers are not supported).
* Conversations that come from a **Click-to-WhatsApp** ad. The click ID must be stored in the conversation memory. See [Meta Ads](https://docs.jelou.ai/en/guides/integraciones/marketing/meta-ads.md) to learn how it is stored.
* Conversion reporting turned on for the channel (it is off by default). To turn it on, open the WhatsApp channel settings and use the **Meta Conversions (CAPI)** switch.

***

## Configuration

### General

| Field | Required | Details |
| - | - | - |
| **Event** | Yes | Conversion event reported to Meta. The selector supports search. |
| **Currency** | Only for `Purchase` | `USD`, `COP`, `MXN`, `PEN`, `ARS`, `CLP`, `BRL` or `EUR`. |
| **Value** | Only for `Purchase` | A number greater than or equal to 0, or a variable such as `{{$memory.total}}`. |
| **Additional parameters** | No | Key/value pairs with extra event information. Maximum 10. |

Available events: `AddPaymentInfo`, `AddToCart`, `AddToWishlist`, `CompleteRegistration`, `Contact`, `CustomizeProduct`, `Donate`, `FindLocation`, `InitiateCheckout`, `Lead`, `Purchase`, `Schedule`, `Search`, `StartTrial`, `SubmitApplication`, `Subscribe` and `ViewContent`.

> [!NOTE]
>
> Meta only requires currency and value for the `Purchase` event. For all other events they are optional, but if you fill in the value it must be valid.

### Advanced

| Field | Required | Details |
| - | - | - |
| **Click-to-WhatsApp ID** | Yes | Identifier of the ad click. Accepts variables, for example `{{$memory._referral.ctwa_clid}}`. |

The event is sent through the project's WhatsApp Cloud API channel and signed as **JELOU**.

***

## Outputs

| Output | When it fires |
| - | - |
| **Reported** | The event was successfully reported to Meta. |
| **Error** | Reporting the event failed. |

The node has no default output: connect both outputs to control what happens in each case.

## Node status

The node shows **Ready to report** when the configuration is complete and **Setup incomplete** when something is missing. These are the most common errors:

* The **Click-to-WhatsApp ID** is empty.
* The event is `Purchase` and the currency or value is missing.
* A row of additional parameters has only the key or only the value.

> [!TIP]
>
> Use the **Error** output to store the failure in a variable or notify your team, so you don't silently lose conversions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.