In this guide
- Start with the business outcome
- Separate primary conversions from useful signals
- Use one event for one meaning
- Do not optimise campaigns for accidental actions
- Preserve privacy while measuring intent
- Connect marketing data to lead quality
- A practical conversion map
- Name the event after the evidence
- A simple reporting example
- Common questions
A campaign cannot be judged properly if the business has not agreed on what a meaningful result looks like. “More traffic” is not a conversion. Neither is a scroll, a button hover or a long session. Those signals can help diagnose behaviour, but they should not be allowed to replace the business action you are actually trying to create.
Track the actions that represent real progress toward revenue or service delivery, then keep diagnostic engagement events separate from primary conversions.

Start with the business outcome
Write the outcome in language the sales or operations team understands: a qualified enquiry, a booked consultation, a submitted quotation request, a verified phone call, a completed checkout, or a paid subscription.
Then work backwards to the website action that proves the outcome happened. This prevents the analytics setup from being driven by whatever events are easiest to track.
Separate primary conversions from useful signals
A WhatsApp click may be valuable, but it is not the same as a completed project enquiry. A form start is useful, but it is not the same as a submitted form. Create a hierarchy.
For UVs Digital Hub, for example, an assistant-to-WhatsApp hand-off or a prepared contact enquiry is stronger than simply opening the assistant. We still track the earlier actions because they explain the journey, but we would not value them equally.
Use one event for one meaning
Avoid using the same event name for several different actions. If “lead” sometimes means a phone click and sometimes means a completed form, reporting becomes difficult to interpret.
Google Ads supports separate conversion actions for different valuable behaviours, and website click actions can be measured explicitly. That lets you compare campaign performance without pretending every interaction has the same value.
Do not optimise campaigns for accidental actions
If a conversion fires when the page loads, when a visitor opens a chat widget or when a button is visible, an ad platform can learn from people who never actually enquired. The campaign may appear to improve while the sales team sees no change.
Where possible, fire the conversion at the moment the meaningful action occurs: after a confirmed submission, or at the separate contact action you actually measured. A prepared message or opened phone link needs its own label; it is not proof that the business received an enquiry.
Preserve privacy while measuring intent
Do not send names, email addresses, phone numbers or private message text as ordinary analytics event parameters. Track the action and context needed for measurement instead—such as service category, source page or event type.
In the retained UVs website code, the selected event parameters are designed so that the website can measure WhatsApp clicks, assistant use, audit starts and contact actions without intentionally sending the visitor’s enquiry text into Google Analytics.
Connect marketing data to lead quality
The most useful review happens when analytics and the sales process use a shared definition of quality. If ten enquiries arrive but eight are irrelevant, the campaign should not be celebrated purely for volume.
Add a simple feedback loop: which enquiries became qualified opportunities, quotations or customers? Even if that feedback is initially manual, it helps the marketing team understand which traffic sources create useful demand.
A practical conversion map
For a service business, a simple map might be: ad click → landing page → service-page engagement → enquiry start → qualified hand-off → sales follow-up → quotation → won/lost. Not every stage belongs in Google Analytics, but the map helps decide what should be measured where.
Keep the top of the funnel diagnostic and the bottom of the funnel commercial. That makes reporting much harder to manipulate accidentally.
The retained UVs website code contains handlers for contact interactions, assistant actions and website-audit use. Code inspection confirms the intended event design, not that GA4 received each event on a live deployment. Check consent behaviour and the actual analytics payload before accepting the measurement setup.
Name the event after the evidence
| Observed action | What it proves | What it does not prove |
|---|---|---|
| WhatsApp link clicked | A contact hand-off was attempted | A message was sent or received |
| Message draft prepared | The visitor has a draft ready to send | A new lead reached the business |
| Submission confirmed | The defined form success condition occurred | The enquiry is qualified or a sale is won |
Google recommends generate_lead for a lead-generation action. Choose an implementation trigger that reflects the event you actually confirmed, and keep qualification or revenue outcomes separate. See Google’s event reference and its guidance on avoiding personally identifiable information.
A simple reporting example
Suppose a fictional campaign records eight contact clicks, three received enquiries and one sales-qualified opportunity. Report those as three separate counts. Calling all eight clicks “qualified leads” would obscure the stage that needs attention. These invented figures illustrate definitions only; they are not UVs or client results.

Common questions
Should every button click be a conversion?
No. Track important diagnostic clicks as events if useful, but reserve key conversions for actions that represent meaningful business progress.
Can WhatsApp clicks be tracked?
Yes. A website can record the click as an event. You should still distinguish the click from a qualified conversation or completed sale.
Can GA4 events be used in Google Ads?
Eligible GA4 key events can be imported into Google Ads after the properties/accounts are linked and the event setup has propagated.
