Lead tracking should distinguish a contact action from an enquiry that the business actually received. A form submission, WhatsApp-button tap and phone-link tap represent different events. Define them clearly, avoid duplicate counting and connect genuine enquiries to a consistent qualification process.
Start with an event map before installing more tags. The map should explain what happened, where it happened, which system records it and what the event does not prove.
Define the stages of lead tracking
| Stage | Meaning | Limit |
|---|---|---|
| Contact action | A visitor taps a contact control or begins a form. | The person may not complete the action. |
| Received enquiry | The business receives and records the request. | The request may be unsuitable or duplicated. |
| Qualified lead | The request meets the business’s agreed criteria. | Qualification does not mean a sale occurred. |
| Business outcome | A defined later result, such as an accepted project. | Its timing and attribution may differ from the first visit. |
Track a form’s confirmed outcome
A submit-button click can happen even when validation fails. Where the implementation allows it, record the confirmed successful submission separately from attempts and errors. Then check that the business receives the record in the intended inbox or CRM.
Use a unique internal record identifier to prevent the same submission being counted repeatedly during retries or page refreshes. Decide how duplicate enquiries from the same person will be handled; repeated contact can also be legitimate, so do not merge records blindly.
Treat WhatsApp clicks as intent signals
Opening WhatsApp does not prove that a message was sent. Label the website event as a WhatsApp click unless a supported, authorised integration provides stronger evidence of a received conversation.
Keep the website event separate from the conversation record. A sales team can record the actual enquiry and its outcome using an agreed process. Avoid copying private message content into general analytics events.
Separate phone taps from connected calls
A tap on a telephone link shows an action on the website. It does not establish that the caller connected, reached the right team or made a relevant enquiry. If you use call tracking, document the provider’s counting rules and what evidence is available.
Assign a consistent status to answered, missed and unsuitable calls where the business can reliably record them. Call recording or sharing customer information needs an appropriate legal and privacy review for the actual arrangement.
Keep personal data out of ordinary analytics fields
Review URLs, page titles and event parameters for accidental personal information. A form confirmation URL should not expose a customer’s email or phone number to tools that collect the URL.
Google Analytics guidance on avoiding personally identifiable information explains this policy boundary. Advertising features that support specific user-provided data have their own requirements; they are not permission to send personal information through arbitrary analytics events.
Connect measurement to the sales process
Agree who qualifies an enquiry and what criteria they apply. Keep the original source information where it is available and appropriate. Also preserve the dates of receipt, qualification and outcome so reports can distinguish those stages.
Google Analytics recommended events include lead-generation and qualification concepts. Use event names and implementations that accurately reflect your workflow rather than marking every interaction as an important business result.
Test a small set of complete journeys
With the business’s permission, test successful submissions, validation failures, repeated attempts and mobile contact actions. Confirm what appears in analytics and what reaches the team. Record any gaps caused by consent choices, browser restrictions or unavailable integrations.
Recheck after changes to forms, consent tools or the CRM. Reliable measurement needs maintenance as well as initial installation.
Common questions
Can one person create several tracked events?
Yes. A person can visit, tap WhatsApp and submit a form. Events should not automatically be reported as separate unique leads.
Why do analytics and CRM totals differ?
They may measure different stages, periods or people. Review definitions, duplicate handling and missing data before assuming one system is wrong.
Does tracking guarantee more enquiries?
No. It helps the business evaluate the journey. The offer, traffic, usability and follow-up still matter.
Define the measurement scope
Share your forms, contact channels and lead-status process with Solutions1313’s conversion optimisation team. Agree on event definitions, privacy responsibilities and a controlled verification plan.
