All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Tell Meta when a chat ad client buys or reaches a stage

Link a stage in your unit to a Meta event, such as “Won → Purchase”. When a client who came from a WhatsApp, Messenger or Instagram ad reaches this stage, the event is sent to Meta once.

7 min

This feature may not be turned on for your account yet — contact support to turn it on.

Before you start · 2 things · for owners
A WhatsApp Cloud number, Page or Instagram account connected, a select or status stage field

Steps

1
Open the Conversions tab in Settings → Meta Ads, and under Send conversions to Meta, turn on the asset (the number, the Page or the account).
Corteksa asks Meta for the dataset linked to the asset, or creates one.
2
Under Stage to Meta event, press Add rule, and choose the Unit → the Stage field → the Stage → the Meta event.
3
Optional: a Value field (number or currency), and the Currency in ISO format, such as SAR.
4
Press Save. Saving replaces the whole mapping table.
5
Press Send test event, and enter the Test event code from Events Manager.
The event shows on the test page in Meta.

Meta events you can use

LeadSubmitted · QualifiedLead · InitiateCheckout · AddToCart · ViewContent · Purchase · OrderCreated · OrderShipped · OrderDelivered · OrderCanceled · OrderReturned · CartAbandoned · RatingProvided · ReviewProvided

When the event is sent

When the record enters the mapped stage, whether an employee, an import or an automation moved it. It’s sent once per record and per event: if the client goes “Won → Lost → Won”, Purchase is sent once. The first ad on the record decides the channel.

The event log

Status
What it means
Sending
On its way.
Sent
Meta accepted it.
Rejected
Meta rejected it, and the reason shows.
Failed
Meta couldn’t be reached after several tries.
Expired
Older than 7 days and not sent.
Skipped – no click id
A WhatsApp ad from Status.
Skipped – WhatsApp Web number
Cortex Chat numbers don’t send conversions.
Skipped – conversions off
Turn on the asset.

You can filter the Event log tab by status, channel, event and period. The client’s name shows only to people with the “Allowed” level on the unit.

To use an existing dataset

There’s no manual choice; Meta links one dataset to each asset. Link your dataset to the asset in Events Manager, then save here again.

Clients from lead ad forms don’t go through here; they have Send lead form clients’ stages to Meta.

If something goes wrong

What you see
Why
What to do
Turning on is refused with a message from Meta
The events permission isn’t granted for the asset.
Connect the number or the Page again in the channels, or contact support.
A message that the asset has no login access
The channel’s session is disconnected.
Connect the number or the Page again.
The test event is refused
The asset isn’t turned on, or there’s no ad chat with a click ID yet.
Turn on the asset and wait for a chat from an ad.
An error when saving the mapping table
A stage that doesn’t exist, a value field with no currency, or a repeated stage.
Correct that row.

A real example

Basma Clinics
The situation

Meta optimizes their ads for people who message, not people who book.

What they did
  1. They turned on their WhatsApp Cloud number, and linked the “Attended” stage to Purchase with the visit price field.
The result

A month later, the cost of a real booking went down, because Meta now targets people who show up.

A made-up company, to show the idea. The numbers are rounded.

Good to know

One event per record and per event type.
An event older than 7 days isn’t sent.
There’s no resend button for a rejected event.
WhatsApp Web and TikTok don’t send conversions.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.