Click-to-WhatsApp ads: tell Meta which leads became customers

If you run Click-to-WhatsApp ads for a clinic, a villa or a coaching centre, the honest answer to "which ads are working?" is: the ones whose chats turn into paying customers, and Meta only knows that if you tell it. This post explains how that reporting works in plain words, what a sensible setup looks like, and the mistakes that quietly waste the effort.

Why can't the website pixel see a WhatsApp conversion?

A normal ad sends someone to your website, where a tracking pixel records what they do. A Click-to-WhatsApp ad sends them into a chat instead, so the pixel has nothing to watch.³ Wati's guide, dated 14 August 2026, says Meta creates a click identifier called ctwa_clid for eligible conversations and that it arrives with the customer's first WhatsApp message through the API webhook (the automatic message that your software receives).³

Meta's developer documentation describes the same thing from its side: the ID is "a personal identifier, unique per click", you read it from the referral object in the messages webhook, and you send it back when a conversion happens in the conversation.¹ The channel for sending it back is the Conversions API, which is Meta's way for a business's own system to report results from its server.¹

What does the report look like?

Meta's guide shows a sample payload that sets action_source to business_messaging, messaging_channel to whatsapp, and carries the WhatsApp business account ID and the ctwa_clid inside user_data.¹ The guide lists these standard event names for business messaging:¹

Can Meta spot leads and purchases on its own?

Partly. Meta says that, with the customer's opt-in, it analyses new message threads from Click-to-WhatsApp ads using "a combination of regex and natural language processing" and, when it detects a lead or purchase, sends an automatic_events webhook that the provider can pass on through the Conversions API.² The same page says this is not available to business customers in the European Union, the United Kingdom or Japan.²

Automatic detection is a guess from message text. If your real definition of a good lead is "booked a consultation and paid the advance", only your own records know that. That is why most Indian providers let you choose the trigger yourself.

How do other tools choose what counts as a lead?

These are the vendors' own descriptions, not Meta's. The two also disagree on how many purchase signals you need: Wati suggests at least 10 as a best practice, while DoubleTick tracks progress toward 50.³⁴ Meta's onboarding page does not give a number, so treat both as vendor rules of thumb.¹

Worked example: a dental clinic in Pune

This is an illustration, not a real clinic. A clinic spends on Click-to-WhatsApp ads and gets 300 chats in a month. Its receptionist moves each chat through four stages: New enquiry, Consultation booked, Treatment started and Paid.

Without reporting, Meta sees 300 chats and cannot tell the 18 paying patients from the 240 who never booked. With reporting, the ad system can learn from the 18. The clinic can also see that an ad producing 100 chats and 2 payments is worse than one producing 40 chats and 9 payments.

What bananaleaf.ai does here

bananaleaf.ai is an AI sales assistant and CRM that runs on your own WhatsApp number. When a chat starts from a Click-to-WhatsApp ad, we store the ad's ID, headline and the click ID from the first message, and the first ad that brought a person is kept even if they tap a later ad. You can map each pipeline stage to one Meta business messaging event. A stage move queues the event, and a background worker sends it, so a Meta outage never blocks you from moving a card. Each person is reported once per event, and the contact page shows the status and any Meta error. A "sync all leads in this stage" button sends the people already there. In our testing, Meta refused events older than 7 days, so sync reports those as too old instead of faking the time. Chats that started before we began capturing ad data have no ad attached and cannot be recovered.

A definition sheet to copy before you start

Fill this in once and put it where your team can see it:

Lead (LeadSubmitted): the person has given ______ (name, treatment or stay dates, budget) and we can follow up. Qualified (QualifiedLead): a staff member confirmed ______ (they are in our city, can afford it, want to book). Purchase (Purchase): we have received money in the bank or UPI, and the amount is ______. Never send: chats that only said "hi", staff tests, or people who asked for a refund.

What to do this month

1. Write the three definitions above, with your team, before touching any tool.
2. Check that your ads open WhatsApp. The DoubleTick guide says the Conversions API works only for Click-to-WhatsApp campaigns.⁴
3. Confirm your provider stores the ctwa_clid from the first message. Without it nothing can be matched to an ad.¹
4. Map each stage to a name from Meta's list, not a website event name.¹
5. Send a real amount with every purchase, so ad spend can be compared with revenue.³
6. Decide on automatic detection. If you use Meta's, remember it is not offered in the EU, UK or Japan, and ask your provider about the Embedded Signup version, since Meta's page said version 2 would be deprecated on 15 October 2026.²
7. Review after four weeks: compare cost per paying customer by ad, and pause the ads with chats but no payments.