Ads that learn from the delivered order
Meta's algorithm looks for people who resemble whoever "succeeded" for you. Tell it a message is success and it brings people who message; tell it a placed order is success and it brings people who order then refuse at the door. Here we tell it what you actually want: whoever bought and received.
- Store, WhatsApp, Messenger and Instagram
- Purchase, delivered and returned
- Without message content or customer numbers
Only the order's value, currency and number and the chat or ad-click reference are sent to Meta. A store buyer's details are sent hashed, as Meta requires. Message content and phone numbers never leave us.
Why the ad brings many messages and few orders
A messages ad learns from "started a conversation", so it finds people who like to ask. A sales ad learns from "completed checkout", and with cash on delivery many orders are refused at the door. The algorithm never learns what happened next unless someone tells it — which is what we do.
How it works
Link the pixel to your store
In one tap from the ads settings, or ArabyBot creates a pixel for your store.
The ad's customer is recognised
From the ad click to the chat or store, with the click reference Meta sends.
Every change in the order is reported
Purchase on confirmation, Delivered on arrival, Returned on refusal — once per order.
Optimise for delivered orders
Once enough delivered orders arrive, you choose on the ad builder to learn from them.
What we tell Meta
Store sales
With the pixel in the browser and the Conversions API from the server together, so no order is lost to an ad blocker or a browser.
WhatsApp sales
For whoever came from a click-to-WhatsApp ad and ordered in the chat, tied to that ad click.
Messenger and Instagram sales
For whoever came from a Messenger or Instagram messages ad and ordered, tied to their chat on the Page.
Delivered and returned
The Delivered event teaches the ad from the order that arrived, and Returned tells it who does not resemble a buyer.
The sales signal here versus the pixel alone
| The pixel alone | ArabyBot | |
|---|---|---|
| Chat sales | Cannot see them | From WhatsApp, Messenger and Instagram |
| The delivered order | Does not know it | A separate event the ad learns from |
| Ad blockers and browsers | Some sales are lost | From the server too |
| Setup | Code on the site and manual tokens | One-tap linking |
Questions people actually ask
What is the difference between the pixel and the Conversions API?
The pixel is code in the visitor's browser that tells Meta what they do, and an ad blocker can stop it. The Conversions API tells Meta directly from the server, so sales arrive even when the pixel is blocked. We use both together without counting an order twice.
Are WhatsApp sales reported to Meta?
Yes, for whoever came from a click-to-WhatsApp ad: the order value and the ad-click reference go to your WhatsApp account's dataset, so the ad learns from people who ordered, not only from people who messaged.
When do I choose to optimise for delivered orders?
When the pixel receives at least ten delivered orders a week; below that the ad never leaves the learning phase. The ad builder shows you the count and opens the option when it is enough.
Are my customers' messages or numbers sent?
No. From chats only the order value and number and the chat or ad-click reference are sent. From the store, the buyer's details are sent hashed, as Meta requires.
Also asked as: «بيكسل فيسبوك» · «كونفرجن api» · «تتبع المبيعات فيسبوك» · «اعلانات تجيب طلبات» · «اعلان يجيب مبيعات» · «تثبيت بيكسل فيسبوك» · «ربط بيكسل فيسبوك بالمتجر» · «اعلانات تجيب رسايل ومفيش طلبات» · «meta conversions api» · «meta conversions api (capi)» · «meta conversions api vs pixel» · «meta conversions api setup» · «meta conversions api for crm» · «conversions api for business messaging»
An ad that learns from people who buy and receive
Store, WhatsApp, Messenger and Instagram · purchase, delivered and returned
Start free