Measurement & contact journeys
From a contact click to a qualified enquiry
A clear call button is part of a usable website. Its click does not, by itself, answer the business question: did a suitable enquiry arrive? I treat measurement as a sequence that starts with an interface action and continues through enquiry receipt, review and follow-up.
Give each stage a definition
A phone click means someone selected the calling link. A WhatsApp click means someone opened the messaging destination; they may send a message or leave first. A received enquiry requires a business record. Qualification then requires criteria appropriate to the service, location and delivery capacity.
I keep those definitions consistent between reporting and the follow-up system. Two actions from one person are not automatically two customers. An assigned conversion value is not booked revenue. A shared definition is more useful than an impressive number the team cannot interpret.
Read improvements and declines together
The Tawod study compares two complete 14-day periods: 10–23 September and 24 September–7 October 2026. Sessions increased from 946 to 1,334 and key events from 289 to 325. At the same time, the engaged-session rate fell from 60.25% to 54.42%, and the session key-event rate fell from 23.68% to 18.07%.
That combination directs attention to acquisition sources, landing pages and service selection, followed by the quality of enquiries received. The comparison describes what happened. It does not isolate design from advertising, SEO or changes in the audience between periods.
Keep the metric's actual meaning
The Sama Scan study records call-button clicks increasing from 18 to 118 across equal 32-day periods: 25 July–25 August and 26 August–26 September 2026. I report them as call-button clicks. Profile views, direction requests and website clicks remain separate measures.
Those figures do not establish completed calls or medical bookings. Nor can they be attributed to a post published after the comparison period ended. The source date and the metric's limits belong with the result whenever it is shared.
Instrument intent with a small, clear event set
On my website, phone, WhatsApp and email events are collected after analytics consent. The event records interaction type, placement and page, with an allowlist for parameter values. Contact remains available when analytics is declined. Message content, visitor names and phone numbers are excluded from event parameters.
A profile download or credential visit receives an event describing that interest, separate from contact actions. I also review repeated clicks and returning to the page so that measurement does not obstruct the action the visitor came to complete.
Close the loop with follow-up
My review starts with two questions: did opportunities to make contact increase, and could the team move suitable enquiries forward? Recording source, status and known disqualification reasons helps connect reporting with operations. Comparisons use complete periods and a consistent timezone, bringing content, bidding and interface decisions closer to the business reality.