WhatsApp ads conversion tracking means connecting what happens inside the chat, such as a qualified lead, a confirmed appointment or a paid order, back to the ad that started it. By default, Ads Manager only sees that a conversation began. To know which ads bring sales, you need to label chats by outcome and, ideally, send those outcomes back to Meta.
This article is part of our guide to click-to-WhatsApp ads.
What Ads Manager shows by default
For a click-to-WhatsApp campaign, Ads Manager reports delivery and engagement, such as reach, clicks and the number of messaging conversations started. It cannot read your chats, so it does not know whether a conversation became a sale.
That gap causes two common mistakes:
- Scaling the ad with the lowest cost per conversation, even if its chats rarely buy.
- Switching off an ad with higher costs that actually brings serious customers.
According to WhatsApp Business, results beyond the conversation can be measured with tools such as the Meta pixel, the Conversions API and offline conversions.
Marking chats as leads or sales
Tracking starts on your side, with a simple status on every ad chat. Use a short, fixed list:
| Status | Meaning |
|---|---|
| New | Chat started, not yet answered in full |
| Qualified | Real need, right area, realistic timing |
| Appointment requested | Customer asked for a time; your team confirms it |
| Won | Paid order or confirmed booking |
| Lost | Not interested, wrong fit or no reply |
Also record the source of each chat, ideally down to the campaign or ad. A pre-filled message that names the offer (“Hi, I’d like the AC service offer”) makes this much easier.
Sending events back to Meta
Once outcomes are recorded, they can be shared with Meta so its delivery system learns which people become customers, not just who taps “Send message”.
- Conversions API: your system sends events, such as Lead or Purchase, directly to Meta from a server. For business messaging, these events can be linked to the ad chat that started the conversation.
- Meta pixel: records actions on your website, for example when a customer pays through a link that opens your checkout page.
- Offline conversions: upload outcomes later, such as sales completed in store or by phone.
Meta’s tools change regularly, so set this up with someone who keeps up with the current requirements. Only share data your privacy notice covers, and only what is needed. Once Meta receives reliable Lead or Purchase events, you can test campaigns optimised for those outcomes rather than for conversations.
Which events to send
Start with two events and make them consistent:
- Lead: sent when a chat reaches “Qualified”, not for every hello. Sending every conversation as a lead teaches Meta nothing new.
- Purchase: sent when an order is paid or a booking is confirmed, with the order value where you have it.
Agree internally on what counts as qualified, write it down and apply it the same way every week. Changing the definition halfway through makes trends meaningless.
Matching ad chats to orders
Even without a technical integration, you can match most sales to ads by hand:
- Keep one record per phone number, with the first source saved.
- Link orders to the same number, whether paid by link, cash on delivery or in store.
- Record the date of the first chat and the order, so you can see how long customers take to decide.
- Keep the first source even if the customer later returns through another channel.
Example: a customer messages from your Ramadan reel ad on Monday, asks two questions, goes quiet, then pays a link on Thursday after a follow-up. With the phone number as the key, that sale belongs to the reel ad. Our article on lead source tracking covers labelling across every channel.
Reporting weekly
A weekly report does not need to be complicated. For each campaign or ad set, list:
- Spend
- Conversations started
- Qualified leads
- Sales or confirmed appointments
- Revenue, where you can attach it
- Cost per qualified lead and cost per sale
Common reporting pitfalls to avoid:
- Counting the same customer twice because they messaged from two ads.
- Leaving chats in “New” for weeks, which hides real outcomes.
- Comparing a week with a public holiday against a normal week without noting it.
Look at trends over several weeks rather than reacting to one day. Make changes in batches, because significant edits can restart Meta’s learning phase. Our help article on reports on WhatsApp shows how these numbers can be requested by message.
How Dub Ai helps
Every ad chat on your WhatsApp number is saved in Dub Ai as a lead, keyed by phone number, with its source label, status and a short brief written from the conversation. Orders built in the chat are linked to the same contact.
With Reports and Analytics, you can ask your admin agent on WhatsApp for period comparisons, sales by period and how your Meta ads spend compares with revenue, and export reports to Excel or PDF. The Dub Ai team handles the Meta side of campaigns through our ads management service.
Frequently asked questions
Why does Meta show conversations but no sales?
Meta can see that someone tapped your ad and sent a message, but it cannot see what happened in the chat afterwards. Unless you send outcome events back, such as Lead or Purchase through the Conversions API or offline conversions, Ads Manager has nothing to report as a sale. Recording statuses on your side is the first step.
Can I see which ad brought a sale?
Yes, if you record the source at the start of each chat and link orders to the same phone number. Specific pre-filled messages per ad help, and a messaging integration that captures ad details makes it more precise. Without either, you can usually only tell the campaign, not the exact ad, so name campaigns and offers clearly.
Book your demo on WhatsApp: +971 56 552 6662