Separate discovery, contact activity and receipt
Search impressions and clicks describe discovery. Page views and chat openings describe website activity. A phone-link click records an attempt to contact the business. A saved enquiry records a request received by the intended system. These are related stages, but they should not share one undifferentiated conversion label.
For a lead form, identify the response that confirms acceptance. Triggering a lead event when someone presses submit can count invalid fields, failed requests and repeated attempts. The measurement should follow the successful outcome the event name claims to represent.
Connect enough context to make the record useful
Useful context can include the landing page, source information, service selected and city or project area when relevant. Retain it through the contact journey where appropriate, so the business can understand what prompted the enquiry.
Keep the personal contact record in the system designed to handle it. Names, email addresses, phone numbers and free-form messages should not be sent into ordinary Analytics event parameters. The reporting context should be sufficient for analysis without copying the full customer conversation into a dashboard.
- Define when a request counts as saved.
- Keep form attempts and contact clicks separate.
- Avoid counting duplicate retries as new leads.
- Preserve relevant service and source context.
- Exclude personal contact details from routine Analytics events.
Understand why systems can disagree
Analytics and the lead system can show different totals because they record different parts of the journey. Visitor consent, browser blocking, duplicates and incomplete source information can also affect the comparison. A discrepancy deserves investigation, but it does not automatically mean that one system has failed.
An illustrative check is to follow one labelled test enquiry: confirm the submitted details, the saved record, the visitor’s success message and the event behaviour under the configured analytics choice. That verifies a concrete path before more reports are built around it.
Add the business’s assessment of quality
The website cannot decide whether a request became a good customer without follow-up evidence. Ask the team to use a simple, consistent status process for suitability and later outcomes. A small amount of reliable feedback can make the content and campaign review much more useful.
Then compare the pages and services that generate suitable requests. If a page draws the wrong work, clarify scope or targeting. If relevant visitors do not enquire, review the offer and contact route. The purpose of the report is to guide a decision, not merely show that a tracking script is installed.
Sources & further reading
Official references used for the local and platform guidance on this page.