Define the events before installing tags
We agree what counts as a completed enquiry, which supporting actions are useful and what information belongs in the lead system. A form start, chat opening and accepted submission should have different meanings.
We measure a completed enquiry when the request has been accepted, then keep supporting actions such as form starts separate. That gives the report a clearer connection to the opportunities your team can follow up.
Connect the enquiry to its context
A useful lead record can include the selected service, target city, landing page and campaign information when available and appropriate. That helps your team respond and helps you evaluate which marketing deserves further investment.
- Separate accepted leads from button clicks and form starts.
- Preserve source context without placing personal details in analytics.
- Review duplicate submissions and obvious test traffic.
- Confirm that a successful submission reaches the intended destination.
Use each system for the question it answers
Search Console helps investigate search visibility and discovery. Website analytics helps explain measured visits and actions. Your lead system records the people who contacted you and the result of the conversation.
Those systems have different boundaries. We reconcile the story they tell rather than assume that every total must match exactly.
Turn reporting into a next step
A useful review names the priority service, shows where the customer journey is weak and recommends a specific action. More unsuitable enquiries may call for better qualification. Strong enquiries from a page may justify improving or expanding that subject.
Sources & further reading
Official references used for the local and platform guidance on this page.