AI search, SEO & online discovery
Practical coverage from Dubai

Saved
Measurement

How to Track WhatsApp Enquiries from Search Content

Summarize with AI
Using a smartphone indoors; illustrative photograph.
Photo by https://kaboompics.com/ / PexelsIllustrative photography
In this article 7 sections

A customer lands on a Dubai service page from search, taps the WhatsApp button and opens a chat. The business has recorded a click. It has an enquiry only if a message arrives and meets its intake definition. A member of staff may then need to establish whether the work fits the business before calling it a qualified lead. Each step has a different record and can produce a different count.

Measure the website interaction in analytics and the actual requests in the business inbox or enquiry system. Carry a short page reference into the chat where it helps staff identify the route. Keep evidence of that route separate from the acquisition source that brought the visitor to the website. This gives you useful information about search content even when the journey cannot be joined from end to end.

Decide which part of the journey you need to measure

Start with the content decision. If you want to know whether visitors see and use the contact option, measure sessions with a WhatsApp link click on the relevant pages. If you want to know what work customers request after seeing a particular page, look for incoming enquiries with reliable page evidence. If you want to evaluate commercial results, follow those enquiries through a qualification rule. Keep those questions separate in the report.

Give each metric a unit. A click event records an interaction. A session with a click counts the session once even if the visitor taps several times. A conversation can contain several messages and extend beyond the reporting period. A distinct enquiry represents a customer request under your intake rule. A single conversation may contain two unrelated requests, while one request can also appear in more than one thread or contact channel.

Define what makes an enquiry new and what qualifies it. A service business might accept a new request once the customer describes the item or work needed. It might qualify the request when the job is within its service area, scope and current capacity. A status of pending is useful when staff need photos or a service address before deciding. The reporting cutoff determines how much of the cohort has reached that decision.

Measure the website handoff at the click

For a conventional outbound link, Google Analytics enhanced measurement can record an outbound click and populate dimensions including link domain, link ID and link URL. Links to domains configured for cross-domain measurement are excluded from that automatic outbound event. Check your own implementation. A button that routes through a same-domain redirect or opens an app using different code may need separate instrumentation. GA4 enhanced measurement documentation

For a standard link, inspect the actual event from a test click. Record the content page or approved page ID, link placement and destination class. An event name such as whatsapp_click can be useful if your team needs one consistent event across different button implementations. If automatic outbound tracking and a dedicated event both fire, choose one event definition for the KPI. Test a page with multiple buttons and verify whether one deliberate click is counted once under that definition.

Read the result with session acquisition if your question is about search. The website can show how many sessions classified as organic search included a WhatsApp click. It may also show assistant sessions under a separate acquisition category. These figures describe measured sessions on your site. A person who starts a chat directly from another surface may never create that session. The inbox can contain real enquiries that website analytics cannot see. GA4 Traffic acquisition report

The official Shoe Doctor DXB Instagram example below illustrates a separate discovery touchpoint. A public work example may interest someone before they open a service page or contact the business directly. The publication establishes that the brand showed the work. Any link between that post, a website session and an incoming request needs separate evidence.

Give incoming messages a useful page reference

WhatsApp's click-to-chat documentation describes links that open a chat and can populate the message field with text. The text appears in the composer. The customer still controls whether to send or edit it. A short page reference in a generic starter message can help an intake team identify a route when the reference arrives in the message. It should remain understandable to the customer. WhatsApp click-to-chat documentation

For example, a page about a repair service could offer the message “I'd like to ask about a repair. Page ref REPAIR.” Use a stable marker that identifies the page or button variant rather than embedding a search query or customer details. If the same page has an English and Arabic version, decide whether the references should distinguish them. Keep a lookup table with the page, language, marker, and dates in use. Markers can survive after you retire a page because customers can save or share links.

A reference in a message supports a content or link-route classification under your rules. It does not establish whether the visitor reached that link through Google, an AI assistant, an email or a saved bookmark. You can ask where the customer first found the business and record their reply separately. Where your team has an approved method to reconcile a measured session and a specific enquiry, give that linkage a separate status and retain its evidence. Avoid pairing rows solely because their timestamps are close.

Check the information that leaves the page. GA4's automatic click event can include the destination URL, which can contain the prefilled message. Keep the message generic and inspect the outbound event payload for unexpected data. Customer-provided text, names and contact details belong in the approved intake system. A sanitized event with a page code and button placement can cover the click measurement without sending conversation content. Google Analytics personal information guidance

Log received requests and qualify them in the inbox

Start from incoming messages in the intended inbox or approved enquiry system. Mark the first message for each new customer request, connect follow-up messages to the existing record and classify staff tests or unrelated messages outside the new enquiry count. If an intake team handles several WhatsApp numbers, keep the inbox or branch with the record. A transfer should preserve the enquiry reference so both teams can see which request they are working on.

Use separate fields for source evidence and qualification. A useful source record shows whether a page reference arrived, whether the customer stated a discovery source, whether an eligible measurement link was verified, and whether the origin remains unknown. A qualification record shows the outcome, decision date and reason. Staff can qualify an enquiry even if its source is missing. They can also know exactly which page prompted a request and decide the work is outside their scope.

When a customer sends several photos after the first message, count the photos as follow-up evidence rather than new leads. When an existing customer asks about a different repair, apply the new-request rule consistently. If someone started with a web form and continued in WhatsApp, retain both contact events and link them to one enquiry where the match is reliable. This supports an accurate sales total and still shows the work each channel handled.

Reconcile the stages without dividing unrelated totals

The following figures are constructed. A group of search content pages recorded forty-eight WhatsApp click events across thirty-nine website sessions. The team's WhatsApp inbox separately received twenty-one incoming threads requiring triage. In this fixture, three were staff tests or unrelated contacts, and each of the remaining threads contained one new enquiry. The website and inbox observations share a reporting window. They do not share a verified record-by-record connection.

Record Count What supports it
Website WhatsApp click events 48 Measured outbound interaction
Website sessions with a WhatsApp click 39 Distinct measured sessions with at least one click
Incoming threads reviewed 21 Inbox triage records
New WhatsApp enquiries 18 Accepted after excluding three test or unrelated threads
New enquiries with a page reference 6 Reference received in the message
Discovery source stated, with no page reference 5 Customer response only
Neither page reference nor stated source 7 No usable evidence of either kind
Qualified at cutoff 8 Staff qualification outcome across all eighteen
Pending at cutoff 4 Qualification decision still open
Closed outside qualification 6 Staff disposition across all eighteen

The team can say that six of eighteen new enquiries included a page reference. If three of those six qualified, it can report three qualified enquiries among six with page references, alongside the overall eight of eighteen. The five customers who stated a source without a page reference have a different kind of evidence. Neither those responses nor the page reference count can supply an assistant-specific conversion rate unless the relevant source and denominator are established.

Dividing eighteen enquiries by thirty-nine sessions would imply that the inbox requests came from those measured click sessions. Some people may have copied the number or messaged from another channel, and some clickers may never have sent a message. A defensible click-through measure can use website sessions with a click divided by eligible website sessions. A defensible qualification measure can use qualified WhatsApp enquiries divided by new enquiries in the same cohort, with pending cases shown. A click-to-enquiry measure needs a verified link and an explicit eligible population.

Check the handoff on the routes customers use

Test the button from a desktop and a mobile route used by customers, where you have access and authorization. Check that the intended business number opens, the page reference appears in the composer, and the outbound event behaves as expected. In a permitted test inbox, confirm how the intake record looks when a tester sends the suggested text, edits it, or starts a chat without a marker. Include an abandoned click in the check so the team can verify that the website event is separate from the inbox result.

Review the page-code lookup when a page changes or a WhatsApp number moves. A link that reaches the wrong inbox can create customer friction even when the event still fires. A copied code shared between pages can also make the enquiry breakdown ambiguous. Record the date a code was introduced and which button it identifies. Retain earlier mappings for interpreting messages received from saved links.

For recurring reports, decide how to handle late qualification. An enquiry received at the end of the month can qualify after the reporting cutoff. Either publish a dated snapshot and update it consistently, or report the original enquiry cohort after a fixed follow-up period. Keep the receipt and qualification dates separate so the team can reconstruct either view.

Put the numbers next to the content decision

A page with many measured WhatsApp clicks and few enquiries carrying its reference might need a handoff check. Review whether the message text is easy to use, whether the link reaches the correct number, and whether staff record references consistently. The aggregate gap is a prompt to investigate. It cannot tell you which visitors abandoned the chat. A page with few clicks but several qualified reference-bearing enquiries may still support important customer needs. Review the individual requests before changing the contact option.

The existing AI Visibility referral-to-enquiry guide covers the broader process across forms, phone and WhatsApp. Use that process for the overall contact report. In the WhatsApp section, preserve the click definition, the inbox count, the source coverage and the qualification cutoff so the reader can see which part of the journey supports each number. AI Visibility referral-to-enquiry guide

WhatsApp enquiry measurement record

Keep the page and link identifiers, click event definition, inbox scope, new enquiry rule, source evidence categories, qualification criteria and reporting cutoff. Show the number of measured clicks and click sessions beside the received and qualified enquiries. Keep the denominators and linkage coverage visible whenever a report compares the stages.

AI Visibility is published by Lunasol, which offers GEO and AEO services. The measurement ledger is a constructed example. About AI Visibility

You’ve reached the end of this article. Read as plain text

Search the blog

Summarize with AI

Choose your assistant. Copy the article and summary request, then paste it into a new chat.

The full article is included, so your assistant can read it without opening this website. Nothing is submitted automatically.

View or copy the summary requestOpen assistant

Summaries are generated by your chosen service and may miss details. Its account requirements and terms apply.