1What it does
Most shops sell in Messenger or WhatsApp chats, not on a website, so an ordinary pixel never sees a sale and a Click-to-Messenger or Click-to-WhatsApp ad never learns who bought. With this setting on, OmniConva sends your orders and leads straight to your own Facebook dataset through the Conversions API. Ads Manager can then count purchases, and your ads look for people likely to buy, not just people likely to message.
- Messenger orders are matched to the person who messaged your Page.
- Orders from a WhatsApp chat that started with a click-to-WhatsApp ad are matched to that ad click (clicks from the last 7 days).
- Other orders are matched by the buyer's phone number, name and city, which are hashed (SHA-256) before they leave OmniConva.
2Get your dataset (pixel) ID
- Open Meta Events Manager (business.facebook.com/events_manager) in the business portfolio that owns your Page and ad account.
- If you already have a pixel or dataset, select it. If not, create one with Connect data sources → Web and give it a name — you don't need a website for this.
- On the dataset's Settings tab, copy the Dataset ID (sometimes shown as Pixel ID) — a 15–16 digit number.
3Generate a Conversions API token
- In Events Manager, open the dataset and go to its Settings tab.
- In the Conversions API section, press Generate access token.
- Copy the token straight away and keep it somewhere safe — Meta doesn't show it again.
4Link the dataset to your Page and WhatsApp
For Messenger and WhatsApp orders to match your ad clicks, Meta requires the dataset to be linked to your Facebook Page and your WhatsApp Business account.
- Open Business Settings (Meta Business Suite → Settings).
- Under Data sources → Datasets, select your dataset.
- Under Connected assets → Add assets, add the Page you connected to OmniConva, and your WhatsApp account if you use WhatsApp.
5Turn it on in OmniConva
- In the dashboard, open Settings → Facebook Pixel.
- Paste the ID and token into Dataset (pixel) ID and Conversions API access token.
- Turn on Send orders to Facebook.
- Under Count a Purchase, choose when an order counts as a purchase: when it's placed, when it's confirmed (the default) or when it's delivered.
- Switch on what you want under Events to send and Which orders and leads, then press Save changes.
On save, OmniConva checks the ID and token with Facebook. If they match it shows the dataset's name; if not, it shows Facebook's error.
6Which events are sent, and when
| Setting | Name in Facebook | When it's sent |
|---|---|---|
| Purchase | Purchase | At the point you chose under Count a Purchase, with the order total |
| Order placed | OrderCreated | As soon as the order is created |
| Order shipped | OrderShipped | When staff, the courier or your website marks it shipped |
| Order delivered | OrderDelivered | When it's delivered |
| Order cancelled | OrderCanceled | When it's cancelled |
| Order returned | OrderReturned | When a delivered order comes back |
| Lead submitted | LeadSubmitted | When a lead has a name, a phone number and what they want, from the AI or your team |
| Checkout started | InitiateCheckout | When the AI starts an order in chat and the customer has picked a product |
Only Purchase is on by default. Under Which orders and leads, choose separately whether orders and leads the AI takes and Quick Orders and leads your team adds are sent. Facebook has no undo: if an order is cancelled or returned after its Purchase, OrderCanceled or OrderReturned is sent when it's on.
7Test it
- In Events Manager, open the dataset's Test events tab and copy its code (for example TEST12345).
- Paste it into Test event code in OmniConva and press Send test event. The event shows under Test events within a few seconds.
- If you like, save the code and take a real order to see it arrive under Test events too.
- When you're done, clear Test event code and press Save changes.
8Checking what was sent, and Retry
- Recent events at the bottom of the settings page lists the latest events: green is sent, amber is waiting and red failed, with Facebook's reason.
- Each order's page has a Facebook line with that order's events. If one failed, press Retry to send it again.
- For network or temporary Facebook errors OmniConva retries on its own. A wrong or expired token shows as Last error from Facebook on the settings page — save a new token.
9What is sent
The event name and time, the order number, total, currency, and product IDs and quantities. The buyer's phone number, name, email, city and country (whichever are known) are hashed before sending — the plain text never leaves. Messenger chats add your Page ID and the buyer's Page-scoped ID, and chats from a click-to-WhatsApp ad add the ad click ID. Everything goes only to your own dataset, with your token; OmniConva doesn't use it for its own ads. The privacy policy has the details.
Turning the setting off or removing the token stops sending at once, including events still waiting.
Still need help?
Email us with your account's mobile number and what you were trying to do.
contact@omniconva.com