Meta’s Ads Manager can show how many WhatsApp chats each ad started. It can’t show which of those chats came from people ready to buy, until the business tells it. That takes two things: knowing which ad each chat came from, and recording what the chat turned into, a qualified lead or a sale, in a form Meta can match back to the ad.
In the free WhatsApp Business app, that means one setting and Meta’s own chat labels. On the WhatsApp Business Platform, it means storing the ad details that arrive with the chat and sending results back through Meta’s Conversions API.
- Chats aren’t buyers — Ads Manager’s standard WhatsApp result counts conversations started, not leads or sales
- Business app — turn on event sharing and use the app’s predefined lead and order labels within 7 days of the click
- API — a chat from an ad arrives with the ad’s ID and a click ID; store both with the lead
- Send results back — lead and purchase events then show up per ad in Ads Manager
- Then optimize for them — after 10 events in 30 days, Meta can aim the ad at leads or purchases instead of chats
Why the chat count doesn’t tell you which ads work
The result Meta reports for these ads is messaging conversations started, which its Business Help Center defines as “the number of times a messaging conversation was started with your business after at least 7 days of inactivity, attributed to your ads.” The Business app’s own ad metrics report the same thing as conversations started. Two ads with the same chat count can bring in very different customers, and neither number says which.
Meta’s guidance makes the same point for sales campaigns:
When choosing Purchases through Messaging as the performance goal, measure your campaigns based on Meta Purchases and Cost per On-Meta Purchase, rather than conversations started.
— Meta Business Help Center, optimizing click-to-message ads for purchases
Those purchase numbers only exist once the business shares them.
In the WhatsApp Business app: labels do the tracking
A business running WhatsApp from the free app can share results with Meta without any code. Meta’s lead optimization guide sets out what counts:
- Turn on sharing. In the app, tap Tools, then Your customers’ activity, and switch on Allow Meta to receive information about events.
- Use the predefined labels. For leads: Lead, New customer or Follow up. For purchases: New order, Pending payment, Paid or Order complete. Meta warns that “if you use custom labels, the lead events you share may not be attributed.” WhatsApp is renaming labels to lists as it rolls out, so the same options may appear under Lists.
- Label within 7 days. The chat must come from a click-to-WhatsApp ad and be labeled within 7 days of the click.
A “Lead” label should mean the same thing every time. That is easier when the chat asks every lead the same few questions, as in qualifying WhatsApp leads automatically.
On the WhatsApp Business API: keep the ad with the lead
On the API, a message that arrives from a click-to-WhatsApp ad carries a referral object. Meta’s webhook reference lists what is in it: the ad’s ID (source_id), its URL, headline, primary text and media, and a click ID (ctwa_clid). Save the ad ID and click ID on the lead’s record in the CRM, and the same field can route the chat to the right team member.
The click ID is what links a result back to the ad. Meta’s Conversions API documentation spells out the sequence:
Upon receiving the ctwa_clid, store it with the conversation. When a conversion has happened within a conversation, send the corresponding ctwa_clid via the Conversions API.
— Meta for Developers, Conversions API for Business Messaging
The event list runs to 14 types. The three that answer “which ads bring buyers” are LeadSubmitted, QualifiedLead and Purchase. A business that works with a messaging partner may not need to build this itself: Meta says the partner “can share messaging events back to Meta on your behalf.”
| Step | Business app | Business API |
|---|---|---|
| Which ad started the chat | Meta’s side: labeled chats count if they came from an ad | The referral object, stored with the lead |
| Marking a lead or sale | Predefined labels, within 7 days of the click | A QualifiedLead or Purchase event with the click ID |
| Who sends it to Meta | The app, once sharing is on | Your own integration or messaging partner |
Read the results per ad, then optimize for them
Once events flow, Ads Manager reports them against each ad. Meta’s page on messaging events gives the example that “you can see the number of purchases and cost per purchase for your ads that click to business chats.” Leads appear under Columns, then Customize columns, then Conversions.
The same events open two performance goals: Maximize number of leads through messaging and Maximize number of purchases through messaging. Each needs 10 or more qualifying events shared in 30 days. Meta’s own figure for the lead goal: “Ads that click to WhatsApp optimized for leads experienced 24% lower CPL, on average, compared to those that optimized for conversations.” That is Meta measuring its own product, and Meta notes the lead goal is still being gradually introduced.
Also Read: Meta Business Agent vs. Building Your Own WhatsApp Automation
Key Takeaways
- Conversations started is a chat count — it can’t separate ads that bring buyers from ads that bring browsers
- Business app — share events and use Meta’s predefined lead and order labels within 7 days; custom labels may not count
- API — store the ad ID and click ID from the
referralobject with every lead - Send outcomes back —
QualifiedLeadandPurchaseevents turn Ads Manager’s report into leads and sales per ad - Ten events in 30 days — unlock optimizing for leads or purchases instead of chats
Frequently Asked Questions
Do ads in WhatsApp Status carry a click ID?
No. Meta’s webhook reference says the ctwa_clid property is omitted entirely for messages that start from an ad in WhatsApp Status. The documentation drops only the click ID, so the chat can still be tagged with the ad it came from, but there is no click ID to send back through the Conversions API.
What if a WhatsApp lead buys on my website instead of in the chat?
Send that sale through Meta’s Conversions API for web, not the business messaging version. Meta’s documentation says messaging events should only represent customer interactions that occur in the messaging thread, not conversions on other channels like websites, and that a conversion outside the thread should still go back to Meta through the relevant Conversions API product.
Does Meta see the chat when I share lead and purchase events?
No. WhatsApp’s Help Center says that when the Business app shares customer activity with Meta, message and call content isn’t shared, and neither are customer names, email addresses or phone numbers. What it shares is order details such as status and when an order was created, updated or paid for. Customers are told separately that Meta receives limited information when they open a chat within seven days of interacting with a business’s ad.
Can Meta label WhatsApp leads automatically?
In some countries, yes, with two catches. Automatic events label orders and leads in chats for you, but Meta says that using them for ad optimization is only available for ads that click to Messenger and Instagram Direct at this time, so they don’t yet feed WhatsApp ad optimization. In the Business app, turning them on may also limit broadcast lists, disappearing messages, greeting and away messages, and message editing and deletion.
Do these WhatsApp ad metrics work for ads shown in Europe?
Not fully. Meta’s definition of messaging conversations started excludes conversations from ads delivered to or from Europe or Japan, and its setup guide for click-to-WhatsApp ads says certain messaging-related metrics will be unavailable for ads delivered to and from Europe, Japan and South Korea. A business advertising there should count leads and sales on its own side as well.
Final Thoughts
An ad that fills the inbox and an ad that fills the order book can look identical in Ads Manager until results are shared. In the app, the work is a setting and consistent labels. On the Business Platform, it is two stored fields and one API call per result.
A good first step is to label this week’s ad chats as they come in, since only chats labeled within 7 days of the click count, and compare the ads by leads after a fortnight. The WhatsApp automation guide covers the rest of the setup that sits around it.
Know which of your ads actually sell?
ClubUnbrick connects click-to-WhatsApp ads to the CRM and reports, so every lead carries the ad that brought it in.
What We Offer
- Ad-to-lead tracking — The ad ID and click ID saved with every WhatsApp lead.
- Results sent back to Meta — Qualified leads and sales shared through the Conversions API.
- Lead qualification — Questions in the chat that decide which leads count as qualified.
- Reporting — Leads and sales per ad, not just chats.
Already labeling chats in the Business app? We can start from what you have.
