For most diagnostic labs and clinics, the phone and WhatsApp are where bookings happen. A visitor reads a test page, taps the green icon, and the real conversion takes place in a chat that the website never sees. Many sites count that tap as a conversion and report a very healthy-looking number. A tap is not an enquiry. Some people tap and close the app. Some tap three times. Some start a chat that never reaches a person who can book.
This article is for marketing leads and analysts at diagnostic centres, labs and clinics who track calls and WhatsApp in GA4 and Google Ads. It separates the stages, shows the events, and explains how to count each stage once. The examples use a hypothetical diagnostics chain with home sample collection in several Indian cities.
Three stages, three events
Treat every phone or WhatsApp contact as moving through up to three stages.
| Stage | Meaning | Where it is observed | Event name |
|---|---|---|---|
| Click | The visitor tapped a call or WhatsApp button | The browser | call_click, whatsapp_click |
| Started | A call connected or an inbound message arrived | Call tracking or WhatsApp system | call_connected, chat_started |
| Qualified | A staff member confirmed a genuine booking enquiry | CRM or staff action | qualify_lead (with lead_channel) |
Only the first stage can be measured by a website tag. The second and third need your telephony or messaging system and, for qualified, a person.
Which stage should Google Ads optimise on? Not the click. If bidding optimises on clicks to the WhatsApp icon, it will find people who tap icons. Use "started" at minimum, and "qualified" where you have enough volume and the import is reliable. Report all three, with their ratios, so you can see where the drop-offs are.
Stage 1: click events
GA4's enhanced measurement has an automatic outbound `click` event for links that lead away from your domain, with parameters including link_url, link_domain and an outbound flag. A wa.me link will trigger it. That is useful as a check but it is not a clean design, because the event name is generic and every outbound link produces it.
Build your own events instead:
whatsapp_clickwithclick_location(header, testpage, stickybar, bookingconfirmation), `pagetypeandlanguage`.call_clickfortel:links with the same parameters.
Do not send the phone number, the pre-filled message text or the page text as parameters. A WhatsApp link can include pre-filled text; if that text can describe a test or condition, keep it out of analytics and out of the event.
Do not mark the automatic click as a key event. If you mark whatsapp_click as a key event, use it as a secondary signal and not as the primary one.
Stage 2: conversation started
This is the first stage with real information, and it happens outside the browser.
Calls. A call tracking number reports whether a call was answered and its duration. Google's website call conversion documentation describes forwarding numbers swapped onto the site by a snippet, with a call length minimum you set so that very short calls are not counted as conversions. Choose a minimum that fits your call pattern; a lab that takes quick bookings needs a lower one than a clinic with longer consultations. Our guide to call tracking for healthcare covers choosing a provider.
WhatsApp. An inbound message to your business number is the equivalent. If you use the WhatsApp Business Platform or a tool built on it, you can record the first inbound message time. Our own tool WaCRS (wacrs.com) helps plan WhatsApp outreach campaigns and manage business conversations, and any comparable system can supply the same record. The requirement is only that someone can export "first inbound message from this chat, at this time".
Joining a click to a conversation
A GA4 event cannot know that a chat started unless something carries an identifier from the browser to the message. A practical method:
- On the click, the page generates a short random reference, for example four characters.
- The WhatsApp link's pre-filled text includes it: "Hi, I'd like to book a test. Ref K7QX". Do not put personal data in the text.
- The browser sends
whatsapp_clickwith that reference asenquiry_ref, and the reference is saved on your side together with the GA4client_idandsession_id. - When the first inbound message arrives, your system finds the reference, marks the chat as started and sends a server-side event to GA4.
The Measurement Protocol exists for this: Google describes it as a way to augment automatic collection with server-to-server and offline interactions, joined to online interactions by client_id. To tie the event to a session's geographic and device data, include the session_id and send the event within 24 hours of the session start. After that, the latest tagging data for the client is used. Validate payloads with the validation server Google provides.
The reference may not always survive. Some people delete the pre-filled text; some open WhatsApp from a saved contact. Expect only a share of chats to match, and report matched and unmatched separately. Do not guess at the unmatched ones.
For calls, most call tracking tools give you a session identifier or click ID when the call is tied to a visit; send the connected-call event with the same method.



