WhatsApp Conversion Tracking

Why the person your ad sent to WhatsApp disappears

Click-to-WhatsApp (CTWA) is one of the most used ad formats in medical tourism: someone sees the ad, taps "message on WhatsApp", and a chat starts. At that moment Meta learns one thing — a conversation began. It never sees the rest.

The rest is where the information is. Of a hundred chats, forty ask a price and vanish, fifteen book an appointment, five have surgery. Until those five are reported, the algorithm keeps optimising for people who send messages — message counts rise, revenue does not.

The fix is to report the outcome. The difficulty: the outcome is not something software can know on its own. Whether the patient had the operation is known by the consultant. So this product accepts a simple truth — a human marks it, the system sends it.

One tap to mark

The Meta Conversion screen lists the people your ads brought in, newest first: name, the opening of their first message, which channel they came from and how long ago. The list is grouped by day — today, yesterday, earlier.

Each card carries up to three buttons; a typical setup is Interested · Appointment · Sale. They are not hard-coded: you choose which of your own patient statuses appear on the card. Tapping one changes the patient's status — the work you already do in the CRM, reduced to a tap.

The screen is mobile-first because the person doing this is rarely at a desk. Pull to refresh, scroll to load more.

Not every mark carries the same weight

Marking someone does not mean Meta can recognise them. So each card states its signal strength plainly:

• Ad-linked — the person clicked an ad and wrote on WhatsApp. Meta can tie them to that ad; this is the strongest signal and the one campaigns optimise on.
• Matchable — no ad link, but a phone number or account identity exists. Meta matches the person without attributing them to a specific ad. Instagram and QR-code chats sit here.
• No identifier — neither a phone number nor ad data. On this card the buttons are disabled and the missing piece is named instead: add a phone number.

That third tier looks like a detail and prevents the most expensive silent failure: a user believing they marked and sent something when nothing left at all.

Tapped the wrong one? You have 15 minutes

After marking, the card reads "marked · will be sent within about 15 minutes". It does not say "sent", because it has not been.

Undo inside that window and nothing reaches Meta. When the window closes the system re-reads the record: if the status still stands it sends, if it changed it does not. On a team working from phones, mis-taps are certain, which makes this window one of the most important parts of the product.

The screen answers "why is nothing being sent?" itself

The classic failure of measurement setups is silence: everything looks configured, and months later you discover no conversion ever left. The readiness bar at the top prevents that by checking each step for real rather than assuming it:

• Is a WhatsApp number connected?
• Is it connected through the WhatsApp Business API (WABA) — if not, no ad link is ever produced, and this is the most common mistake
• Is a Meta pixel connected?
• Have the statuses that appear on the cards been chosen?
• Are the status-to-event mappings active?

If something is missing the bar says so and points at the step that is still open.

What runs behind the tap

All the button does is change the patient's status. The Meta Conversions API side takes it from there: the mapped event is built, identifiers are hashed, fifteen minutes pass, the event is sent and the dispatch is logged.

Which has a useful consequence: a consultant changing that status in the CRM's normal flow triggers exactly the same conversion. The Meta Conversion screen is not a separate world — it is the same flow, sized for a phone.

Related pages