

Lead tracking should clearly separate a contact action from an enquiry actually received by the business. Understand that clicking a WhatsApp button, tapping a phone number, and submitting a form are three different actions. Track each one separately. Avoid counting the same enquiry multiple times and follow a clear process to decide if an enquiry is a qualified lead.
Before you add more tracking codes, prepare an event map. It should explain what action took place, where it happened, which tool records it, and what that action actually confirm. This helps the business understand what the tracking numbers mean and avoid making incorrect assumptions.
Define the stages of lead tracking
| Stage | Meaning | Limit |
|---|---|---|
| Contact action | A visitor clicks a contact button or starts filling out a form. | The visitor may not complete the action or send an enquiry. |
| Received enquiry | The business receives the enquiry and adds it to its records. | The enquiry may be unsuitable, irrelevant or a duplicate. |
| Qualified lead | The enquiry meets the business’s agreed requirements and is considered a suitable potential customer. | A qualified lead does not guarantee that a sale will happen. |
| Business outcome | A final result, such as a project being accepted by the business. | The result may happen much later than the first website visit, so the dates and original source may differ. |
Track a form’s confirmed outcome
Clicking the submit button does not always mean that a form has been submitted successfully. Sometimes the form may show an error or ask the visitor to correct missing information. Track successful form submissions separately from submission attempts and errors, wherever possible. Also, check if the submitted details actually reach the correct email inbox or CRM system.
Use a unique record ID to avoid counting the same form submission multiple times when someone tries again or refreshes the page. Decide how to handle duplicate enquiries. However, do not automatically combine every repeated enquiry because the same person may genuinely contact the business more than once.
Treat WhatsApp clicks as intent signals
When someone clicks the WhatsApp button on a website, it shows that they wanted to open WhatsApp. It doesn’t confirm that they actually sent a message. You should record it as a WhatsApp click, unless an approved integration can confirm that a message or conversation was received.
Always keep website click records separate from actual WhatsApp conversations. The sales team can record the enquiry and its outcome using an agreed process. Avoid adding private WhatsApp message details to regular analytics reports.
Separate phone taps from connected calls
When someone clicks on a phone number on a website, it only shows that they tried to make a call. However, it doesn’t confirm that the call was connected, the right person answered, or the caller made a genuine enquiry. If you use a call-tracking software, explain how it counts calls, and what information is available to confirm them.
Wherever possible, you should maintain clear records of answered calls, missed calls, and unsuitable enquiries. This helps the business understand which calls were useful. Before you record calls or share customer’s information, check the legal and privacy requirements that apply to your business and the services being used.
Keep personal data out of ordinary analytics fields
Check website URLs, page titles, and event details to make sure they don’t accidently contain customer’s personal information. So, a form confirmation page should not include a customer’s email address or phone number in its URL. Analytics tools may collect this information and create a privacy risk.
Go through Google Analytics guidelines on avoiding personally identifiable information to know how to prevent personal information from being collected.
Some advertising features allow specific customer information under separate rules and conditions. However, this doesn’t mean you can freely add personal details to regular analytics events.
Connect measurement to the sales process
Plan who will review enquiries and what conditions they will use to decide if a lead is suitable for the business. Keep the original source of each enquiry wherever possible and appropriate. Also, record the dates when an enquiry is received, when it is marked as a qualified lead, and when it becomes a customer. This helps monthly reports show each stage clearly.
Google Analytics recommended events include events related to generating and qualifying leads. Choose event names and tracking methods that match the actual business process. Don’t treat every website visit, button click, or interaction as an important business result.
Test a small set of complete journeys
After taking permission from a business, test different website actions. You can submit a form successfully, enter incorrect details, try submitting the form again, and test contact options on a mobile phone. Check if these actions are recorded correctly in analytics and if the enquiries reach the business team. Write down the tracking problems that are caused by privacy settings, browser restrictions, or missing connections between tools.
Repeat these checks if any changes are made to website forms, consent settings, or the CRM system. Tracking should be checked and maintained regularly, not just installed once and left alone.
Frequently Asked Questions
Can one person create several tracked events?
Yes. A single person can perform several actions, such as visiting a website, clicking the WhatsApp button, and submitting a contact form. Each action can be tracked separately. However, they should not automatically be counted as different leads. One person may generate multiple events but they still represent only one enquiry.
Why do analytics and CRM totals differ?
Analytics and CRM systems may show different numbers because they track different stages of the customer journey, use different date ranges or count enquiries differently. So, before you say that something is wrong, check how each system records enquiries. You should also check if duplicate entries are included and if any information is missing.
Does tracking guarantee more enquiries?
No. Tracking does not automatically bring more enquiries. It helps a business understand how visitors interact with its website and where they may leave. The quality of the offer, website traffic, ease of use, and follow-up process also affects the number of enquiries received.
Define the measurement scope
Share your website forms, contact methods, and lead tracking process with Solutions1313’s conversion optimisation team. Before you start, make an agreement on what actions need to be tracked, who is responsible for protecting customer information, and how the tracking will be checked to make sure it works correctly.