Give each event an honest definition
A page view, a chat opening, a contact click and a saved enquiry describe different actions. We define the events before implementing them so the report does not give the same meaning to every interaction.
For a website lead form, the important confirmation is that the request was accepted by the intended system. A click on the submit button is only an attempt. A duplicate retry should not inflate the lead total, and a failed save should leave the visitor with a useful way to try again.
Connect the sources that answer different questions
Search Console can help explain search discovery and indexing. Analytics can describe measured website behaviour. The lead system records enquiries and can support a later review of qualification or outcomes. These systems should inform each other without being treated as interchangeable.
We verify the correct property, domain and event setup, then test the route from the public page to a saved record. Existing accounts and ownership should be understood before creating new properties or replacing an established measurement setup.
- Confirm the correct Search Console and Analytics properties.
- Define meaningful contact and lead events.
- Retain appropriate source, page and service context.
- Verify the saved enquiry before reporting success.
Respect visitor choices and keep reports appropriate
Measurement should follow the site’s stated choices and configuration. Optional analytics consent and browser blocking can affect what appears in Analytics, so its total may differ from the lead system even when both are working as designed.
Names, email addresses, phone numbers and free-form enquiry messages should not be sent into ordinary Analytics events. We use appropriately scoped event context and keep the contact record in the system intended to handle it. A useful dashboard does not need to expose the full enquiry.
Close the loop with the people handling leads
The website can confirm receipt, but the business determines whether a request is suitable and what happened afterwards. A simple lead-status process can make the reporting more useful than a complex dashboard that never receives sales feedback.
We review discrepancies and missing context before drawing conclusions. If enquiries are being saved but not attributed, source handling may need attention. If events appear without corresponding requests, the trigger may be too early. The purpose of measurement is to support a reliable next decision.
Sources & further reading
Official references used for the local and platform guidance on this page.