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

# Meta Conversions

> Tell Meta when people who came from your click-to-WhatsApp ads become qualified leads or buy, so Ads Manager reports real results and your ads find more buyers.

Meta Conversions tells Meta what happens after someone clicks one of your click-to-WhatsApp ads and starts a chat. When that contact reaches a funnel stage you choose, or confirms an order, Ciarem sends Meta an event such as **Qualified lead** or **Purchase**. Ads Manager then shows those results next to each ad, and Meta can optimize your ads for people who buy, not just people who start a chat. Admins set it up under **Settings > Integrations > Meta Conversions**.

> [!NOTE]
>
> Today, conversions are sent from WhatsApp lines. Messenger is coming soon.

## What Ciarem shares with Meta

Only contacts who came from one of your click-to-WhatsApp ads are sent, and only for 7 days after their latest ad click. For each event, Ciarem shares:

* The ad click ID that Meta attached to the chat, which tells Meta which ad the person clicked.
* The event, for example **Qualified lead** or **Purchase**.
* Its value, if you set one.

Nothing else from the conversation is shared: no messages, names, phone numbers, or emails. Contacts who wrote to you without clicking an ad are never sent.

## Turn it on

**1. Enable the integration**

Go to **Settings**, then **Integrations**, and click **Enable** on the Meta Conversions card. Ciarem opens its settings page.

**2. Turn on your WhatsApp lines**

Under **Lines**, turn on each line that receives chats from your ads. The first time, Ciarem creates a dataset for the line in Meta. A dataset is where Meta collects the events for your ad account, and you can see it in Meta's Events Manager with **Open in Events Manager**.

**3. Choose which stages Meta hears about**

Under **Funnel stages → events**, pick an event for each stage that matters (see below). Stages left on **Don't send** are never sent.

### Use a dataset you already have

If your ad account already sends events to Meta from somewhere else, for example a website pixel, you can send Ciarem's events to that same dataset. Click **Use a different dataset** on the line and paste the **Dataset ID**, which you find in Events Manager under **Data sources**. Otherwise, keep the dataset Ciarem created.

## Map funnel stages to events

Each funnel stage can send one event when a contact from an ad enters it. A common setup:

| Funnel stage | Event |
| - | - |
| Interested | Lead submitted |
| Qualified | Qualified lead |
| Won | Purchase |

You can also set a fixed **Value (optional)** and its currency for each event, for example the average value of a sale. Meta reports that value with the event.

Each event is sent once per ad click. If a contact goes back and enters the same stage again, Meta isn't told twice. The initial stage isn't in the list, because every new contact lands there first.

Admins edit the stages themselves from the **Funnel stages** button in the Contacts header. See [Contacts and funnel stages](https://help.ciarem.ai/using-ciarem/contacts-and-stages.md).

## Orders

If you use the [checkout module](https://help.ciarem.ai/ai-agent/taking-orders.md), keep **Send confirmed checkout orders as Purchase** on. Each order a contact from an ad confirms is sent as a **Purchase** with the order's total and currency.

> [!WARNING]
>
> If you sell through checkout, don't also map a funnel stage to **Purchase**, or every sale counts twice in Ads Manager.

## Check that it works

### Send a test event

**Test event** sends a sample event to a line's dataset, so you can check the connection before real leads arrive.

1. In Events Manager, open your dataset, go to **Test events**, and copy the test event code.
2. In Ciarem, pick the **Line**, paste the **Test event code**, and click **Send**.

A test event needs a real ad click on that line in the last 7 days. If there isn't one, click one of your own click-to-WhatsApp ads, send a message, and try again. Opening the ad from a shared post link doesn't count: only a click on the ad itself carries the ad click ID.

### Recent events

**Recent events** lists what Ciarem sent: the contact, the event, and whether it was **Sent**, **Failed**, or **Pending**. At the top of the page you also see how many events were sent and failed in the last 7 days, and how many lines are on.

## Turn it off

Turn off the switch at the top of the Meta Conversions page to stop sending. Your lines, datasets, and stage mapping are kept and apply again when you turn it back on. To stop one line only, turn that line off under **Lines**.

## Troubleshooting

### "This channel was connected before Ciarem could send conversions"

WhatsApp lines connected before October 9, 2026 didn't grant Ciarem permission to send events to Meta. Click **Reconnect** on the line and go through the WhatsApp connection again once. Your conversations, contacts, and settings stay as they are.

### "This line's Meta connection can't read that dataset"

The dataset ID you pasted belongs to a business this line's connection can't reach. Check the ID in Events Manager, or keep the dataset Ciarem created.

### Events don't show in Events Manager

* Check **Recent events** in Ciarem. If the event is there as **Sent**, Meta received it.
* Meta can take up to 30 minutes to show events in the dataset's **Overview**, and test events sometimes don't appear under **Test events** at all. Look at **Overview** again after a while.
* If nothing shows in **Recent events**, check that the integration and the line are on, that the stage has an event mapped, and that the contact clicked an ad in the last 7 days.


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