- GA4 can count WhatsApp taps, phone-link taps and form submits. It cannot see what happens inside a chat or on a call, or visits that a consent banner hides.
- An enquiry log kept by your team, compared with Search Console clicks over the same dates, fills most of the gap.
- Report trends and ranges, not rupee-exact attribution, and write the caveats in plain words for the business owner.
- A one-page monthly template below covers the numbers, the gaps and the next actions.
An Indian service business often gets most of its enquiries by WhatsApp message or phone call. The owner opens a report, sees “12 form submissions” for the month, knows that is far fewer than the real enquiries, and concludes that SEO is not working. The work is fine. The report is incomplete, and nobody told the owner where the gaps are.
This post is about the report itself: what analytics can and cannot count, how to combine it with your own records, and how to present the result honestly. We assume you already capture clicks in some form. If not, start with our GA4 setup guide, and for the capture tactics themselves see how to calculate SEO ROI, which has a section on offline leads. This post does not repeat them. The opposite problem, counting too much, is in the post on duplicate and false conversions.
What analytics can and cannot measure
Be exact about this with your client or boss, because the whole report depends on it.
| What happened | Can GA4 see it? | Note |
|---|---|---|
| Visitor taps a WhatsApp button | Yes, if you set up the event | Counts the tap, not whether a message was sent |
| Visitor taps a phone number (tel: link) | Yes, if you set up the event | Counts the tap, not whether the call connected |
| Form submission | Yes, if tracked correctly | Best signal, but check it matches your inbox |
| Conversation inside WhatsApp | No | It happens in another app |
| Someone taps Call on your Google Business Profile | No | The profile’s Performance view shows call and direction taps |
| Someone dials the number from a printed card or a saved contact | No | Only your enquiry log catches it |
| Visitor who declined analytics consent | Partly or not at all | Depends on your consent setup; with Google’s consent mode some activity may be modeled, not counted |
| Visitor who blocks scripts | No | A small, unknowable share of traffic |
A tap on a WhatsApp button is a signal of intent, not an enquiry. Some people tap and never send anything. Others never tap because they copy the number and paste it later. Treat these events as a trend indicator, not a headcount.
On our own site we marked WhatsApp “click to chat” and contact-link clicks as key events in GA4, raised event-data retention from the default 2 months to 14 months, and set the reporting currency to INR. Note what the retention setting does: it controls how far back Explorations can query event-level data. Standard reports keep their aggregated history either way, so it does not rescue year-on-year standard reports, but it does let you build a year-long exploration of enquiry events by landing page. The one-time setup is small; the discipline of reporting around its limits is the real work.
Step 1: keep an enquiry log
The most useful measurement tool is a simple sheet that your team fills in by hand or from your CRM. One row per enquiry:
- Date and time of the enquiry.
- Channel it arrived by: WhatsApp, call, form, email, walk-in.
- Landing page or service the person asked about.
- Source as the customer describes it (“found you on Google”, “friend told me”, “saw your Instagram”).
- Status: new, quote sent, won, lost, not relevant.
- Value if won.
The “how did you find us?” question is crude, but it catches things analytics never sees. Ask it in the first WhatsApp reply or at the end of every call, and write the answer down the same day. Without a person doing this, the log degrades within a month.
Step 2: line up Search Console against the log
Google Search Console reports clicks from Google Search to your pages, and it counts them without needing a cookie, so it is not affected by consent banners. That makes it a useful second witness. For each month, put these numbers side by side for the same dates:
- Search Console clicks to the pages that matter (service and location pages), filtered to the country you serve.
- GA4 sessions from organic search to those same pages.
- Tracked actions in GA4: WhatsApp taps, call taps, form submits.
- Calls, direction requests and website clicks from your Google Business Profile’s Performance view. Add UTM tags to the profile’s website link so those visits show up separately in GA4 instead of blending into organic search.
- Enquiries in your log that mention Google or search.
- Won jobs from those enquiries.
Do not expect the numbers to match. Expect them to move together. If Search Console clicks to your Andheri service page rose for three months, tapped contacts rose and the log shows more “found on Google” answers, you have a coherent story even though no single figure is exact. If clicks rose and enquiries fell, you have a real question to investigate: ranking for the wrong queries, a broken contact button or a slower response time. For help with Search Console itself, see Google’s Search Console help.
Step 3: report direction, not false precision
When tracking is incomplete, a report that says “SEO generated Rs 4,37,912 this month” is making a claim nobody can defend. Direction and ranges hold up better.
- Use trends. “Organic clicks to service pages up for the third month in a row; tracked contact taps up in line.”
- Use ranges. “Between 18 and 25 enquiries likely came through search, based on the log and a reasonable share of unlabeled ones.”
- Compare like with like. Same pages, same date range, same filters every month.
- Name the proxy. Say plainly that WhatsApp taps are a proxy for enquiries.
This approach also protects you. Rupee-exact attribution claimed in a good month becomes a problem in a bad one. If you want to estimate return anyway, the SEO ROI calculator lets you state your assumptions openly.
Step 4: write the caveats so an owner can read them
Business owners skim reports. Put the limits in a short box near the top, in plain words, rather than burying them in a footnote. A paragraph like this works:
What this report does not capture: conversations inside WhatsApp, phone calls dialed from printed material or saved contacts, and visitors who declined cookies. Calls from our Google Business Profile are shown separately and are taps, not answered calls. We use our enquiry log to estimate these. Figures are directional and compared month on month.
One-page monthly report template
- Headline (two lines): what changed this month and what we did about it.
- Visibility: Search Console clicks and impressions for priority pages, with the previous month and the same month last year if available.
- Traffic quality: organic sessions and engaged sessions on those pages from GA4.
- Tracked actions: WhatsApp taps, call taps, form submits, each versus last month, plus Business Profile call and direction taps on a separate line.
- Enquiry log summary: total enquiries, how many mention search, how many were relevant, how many were won.
- Known gaps: the caveat box above, edited to this month’s situation.
- Next actions: three items with an owner and a date.
Common mistakes
- Presenting taps as leads. A tap is a click. Keep the word “enquiry” for something a person sent.
- Changing definitions mid-year. If you add a new event, note the date, or the trend line will lie.
- Relying on the last click only. Someone may search, leave, return through a branded search and then call. Your log is the only place that journey appears.
- Ignoring response time. Missed WhatsApp messages look like an SEO failure in the numbers.
If your tracking setup itself needs work, our GA4 and Google Tag Manager setup service covers events, consent and testing.
Frequently asked questions
Can GA4 track WhatsApp clicks and phone calls?
GA4 can record taps on a WhatsApp link or a tel: phone link as events, once you set them up, usually through Google Tag Manager. It counts the tap, not whether a message was sent or a call connected, so use these events as a trend signal alongside an enquiry log.
Why do my GA4 numbers not match my real enquiries?
Because many enquiries happen outside the website: chats, calls from printed cards, Google Maps dials. Consent banners and script blockers also hide some visits. GA4 shows part of the picture, so compare it against your own log over the same dates and report trends.
How do I show SEO results if tracking is incomplete?
Combine three sources: Search Console clicks, GA4 tracked actions and a manual enquiry log. Show them side by side for the same period, report the direction of each, state the gaps plainly and avoid claiming exact revenue from SEO. Consistent month-on-month comparison matters more than any single number.
Should I ask customers how they found us?
Yes. It is imperfect, but it captures word of mouth, Google Maps and search visits that analytics misses. Ask in the first reply or at the end of a call, record the answer the same day, and treat it as a rough indicator rather than exact attribution.
Get tracking you can explain to your owner
We set up GA4 events, Tag Manager and a reporting routine that is honest about what it can and cannot count.
See GA4 and GTM setup →