A WhatsApp button click tells you that someone tried to open a conversation. It does not prove they sent a message, wanted the advertised property or met your agency's qualification criteria. Report those steps separately. For a UAE real estate agency, the useful chain is click, received enquiry, qualified requirement and an agreed next appointment.
The practical difficulty is joining the website's evidence to the team's conversation records. Start by writing down what each system can actually observe. Label any gap instead of filling it with an assumption.
Agree on five events before building a dashboard
Your definitions should allow two colleagues to classify the same conversation the same way. Keep the click count available, but give it a name that describes the action.
| Your event | Count it when | Do not count it when |
|---|---|---|
| WhatsApp click | The website records activation of its WhatsApp link | Someone only views the contact section |
| Received enquiry | A genuine incoming property message is recorded | The link opens without a sent message |
| Qualified requirement | An agent confirms the agency can serve the stated need | A person sends “price?” without enough context |
| Appointment booked | Both parties agree a relevant appointment | An agent proposes a slot without acceptance |
| Appointment completed | The team records that the meeting happened | Its calendar time has merely passed |
For qualification, an illustrative ready-property rule could require the transaction type, target area, budget range and intended timing, followed by an agent's confirmation that suitable stock exists. Add a reason when a requirement cannot be served. This is an operating definition, not a claim about how every UAE agency should qualify buyers.
Off-plan investor conversations may progress to a project consultation rather than a unit viewing. Give that appointment its own type. Do not penalise it for failing to produce an impossible viewing of an unfinished unit.
![]()
Keep website events outside the conversation count
A website event can record the page and button that initiated the handover. Useful fields include campaign reference, listing reference and button position. Distinguish the main property button from a generic footer contact link.
Test the behaviour on mobile and desktop. Open the link, cancel before sending, then send a test enquiry. The first action should produce a click event without a received-enquiry event. Confirm that one button activation is not being recorded by two different tags.
Use a clearly marked test property or test record so staff do not follow up with the tester as a buyer. Exclude those records from production reporting, while retaining enough evidence to confirm the test passed.
Keep contact details and message text out of ordinary Analytics event parameters and URLs. Google's guidance specifically addresses personal information in URLs, campaign fields and event data. A campaign label such as marina-ready-apartments is useful; a buyer's phone number in that label is not appropriate. Google Analytics guidance on personally identifiable information.
Choose an attribution method you can explain
A shared inbox or CRM integration should record the incoming message and its source evidence when available. Ask the implementer to demonstrate that evidence on your actual enquiry route. The existence of a WhatsApp integration alone does not prove campaign attribution works.
For a website-to-WhatsApp handover, a prefilled message can contain a property or campaign reference: “I would like details for property MAR-204.” Keep the reference impersonal. Prospects can edit or remove the text, and they can return later through a different route. Use it as supporting evidence with an explicit “unknown source” option.
Store the original source alongside later touchpoints. If an existing buyer enquires about another unit, preserve both enquiries under the contact record. Decide whether the campaign report counts distinct buyers, enquiries or opportunities, then print that unit in its heading.
Direct ads that open WhatsApp are a different route from ads that visit your website first. Their platform reporting and available referral data need separate verification. Do not expect your website click tag to observe a journey that never reached the website.
Where staff use an inbox without a suitable integration, a manual source field and a short daily reconciliation can establish a baseline. Report its limitations honestly. “Source confirmed from message reference” carries more meaning than automatically calling every unexplained enquiry “organic”.
Qualification belongs to a recorded decision
Give each qualification decision a timestamp, a responsible agent and the facts supporting it. Allow correction when the requirement changes, while retaining the previous value in the history.
Google Analytics documents separate recommended events for lead generation and qualification, including generate_lead and qualify_lead. These names provide useful distinctions, but the events require implementation; Analytics does not infer an agent's judgement from a WhatsApp click. Google Analytics recommended events.
Decide whether your reporting counts the first qualification per opportunity or every transition. The first qualification is usually easier to interpret for acquisition reporting. Moving an opportunity backwards and forwards should not manufacture several new qualified buyers.
If you later send downstream outcomes to an advertising platform, maintain a separate integration specification. It must cover approved identifiers, consent requirements, event timestamps, deduplication and rejected uploads. Keeping your internal CRM count accurate is a prerequisite, not evidence that platform matching has succeeded.
Read the ratios with their missing evidence attached
Here is a hypothetical weekly cohort after its appointments have had time to occur. It is a teaching example, not a benchmark.
The site recorded 150 WhatsApp clicks. Staff recorded 72 received enquiries, of which 50 had a reliable reference connecting them to that website cohort. Twenty of those 50 became qualified opportunities; eight completed an appointment.
The example assumes each matched enquiry represents one distinct opportunity. On that basis, 20 / 50 = 40% qualified. You cannot confidently report that 72 of the 150 clicks became enquiries: 22 conversations have no reliable connection to the measured clicks. Some may come from saved contacts or other sources. The 150 clicks may also include repeat activations by the same person, so that count is not a count of unique prospects.
Show the matched subset and unknown-source total beside each other. A rise in unknowns can make a campaign appear weaker without any change in buyer behaviour. Conversely, a high match rate does not prove that the chosen attribution rule describes the whole buying journey.
Keep click reporting by click date and cohort outcomes by original enquiry date. Otherwise this week's clicks may be compared with appointments from last month's leads. State the observation cutoff so pending appointments remain visible.
Run a reconciliation that catches ordinary mistakes
At the end of a reporting period, trace a small selection of incoming conversations into the CRM. Include repeat contacts, a message without a reference and a buyer who changed their property requirement.
Check that each received enquiry has an owner. Check that qualified records have the required evidence. Find at least one completed appointment in both the calendar and the opportunity history. Investigate discrepancies before changing the campaign budget.
Review the campaign's conversion settings with the person managing bids. Google's primary and secondary actions serve different reporting and bidding roles, with custom goals creating an exception to the usual secondary-action rule. Google Ads conversion settings.
For implementation, our CRM and automation service can connect the reporting specification to the team's workflow. If the verified numbers still show enquiries stopping before appointments, use the viewing diagnosis to locate the loss. The next discussion should concern a known stage and a visible record.
PUT IT TO WORK
Make your property lead report auditable
Define the events and CRM records your agency needs to connect enquiries with qualified opportunities and appointments.
Discuss your agency’s workflow Explore the service

