Search and measurement
Counting enquiries from WhatsApp and phone calls
A click on a call or WhatsApp button is a sign of interest, not a customer. This note shows a simple enquiry log, what GA4 can add, and what you must never send to an analytics tool.
Many Indian businesses get their enquiries through WhatsApp and phone calls, not through a form. That is convenient for customers and awkward for measurement, because an enquiry that happens inside WhatsApp or a phone call leaves no trace on your website. Here is a realistic way to count them.
What can and cannot be counted
| What you can count | What it tells you | What it does not tell you |
|---|---|---|
| A click on a “Call” button | Someone on a phone pressed it | Whether the call connected, or who called |
| A click on a “WhatsApp” button | Someone opened WhatsApp with your message | Whether they sent it |
| A form step finished | A form was completed | Whether the message is genuine |
| A real enquiry in your log | Someone contacted you and you recorded it | Which page persuaded them, unless you ask |
A click is an indicator. It is useful as a trend, and unreliable as a count of customers. A website cannot see what happens in WhatsApp or a phone call.
Seven things that get mixed up in one report
A report that says “results” is usually putting several different things in one number. Keep them apart, in this order, and note where each number comes from:
- Search impressions: how often a page appeared in Google results. Source: Search Console. Nobody necessarily saw it.
- Organic visits: people who arrived from an ordinary search result. Source: analytics, once set up.
- WhatsApp button clicks: someone pressed the button. Source: analytics events, if enabled.
- Call button clicks: someone pressed the number on a phone. Source: analytics events, if enabled. Not a connected call.
- Actual conversations: a message arrived or a call happened. Source: your phone and WhatsApp, recorded in your log.
- Qualified enquiries: conversations from a buyer who fits what you sell, in the place you serve, with a real need.
- Won projects: work agreed and paid for.
Each step is smaller than the one before. Only the last two pay the bills, and neither can be seen from the website. Judge the site by the trend from step 5 onward, and use steps 1 to 4 to ask questions about why that trend moves.
Step 1: a simple enquiry log
This is the most reliable measure, and it needs no tools. Keep a spreadsheet and add a row for every enquiry:
- date;
- channel: call, WhatsApp, form, email, walk-in;
- how they say they found you (“How did you find us?” is the most useful question you can ask);
- what they wanted;
- whether you sent a quote or reply;
- the outcome: won, lost, no reply, not suitable.
Review it once a week. After a month you will know how many real enquiries the site brings, which ones fit your business and which sources they mention.
Step 2: add website data as a signal
If the owner decides to switch on Google Analytics 4, it can record clicks on your call and WhatsApp links as events. Google describes an event as a specific interaction, and any event can be marked as a key event, which means one that matters to the business. Counting those clicks by page tells you which pages lead people to reach out. It does not tell you whether they became customers.
Compare the two sources. If the site shows 40 WhatsApp clicks in a month and your log shows 12 WhatsApp enquiries, the gap is normal: some people open WhatsApp and do not send.
What must never go into analytics
Google’s rules forbid sending data that identifies a person to Google Analytics. Phone numbers, names, email addresses and the contents of messages are all in that category, and they must stay out of event names, parameters, page addresses and page titles. For WhatsApp links, take extra care: a link can carry a pre-filled message in its address, and an automatic click measurement feature can record the link’s full address. Google’s enhanced measurement documentation says outbound click events include the link address. Turn that automatic collection off, and record only a plain event such as “whatsapp_click” with a generic label.
Consent and privacy decisions come first
Before analytics is switched on, someone needs to decide what to collect, whether to ask visitors for consent and what to say about it. On this website, analytics is off, and it stays off until the owner supplies a real measurement ID and makes those decisions. Nothing is collected until then.
What to do when the numbers disagree
- A drop in clicks with a steady log may mean a tracking fault, so test the buttons on a real phone.
- A rise in clicks with a flat log may be bots, repeated clicks or curiosity.
- A good week in the log with no matching clicks may mean customers found your number elsewhere, such as a listing.
Trust the log first, and use the website data to ask questions.
Ask every caller one question
“How did you find us?” costs nothing. Write the answer down. Over a few months it will teach you more than a dashboard. For setting up the tools later, see measuring enquiries with GA4 and Search Console and GA4 explained for business websites.