Require evidence of an inquiry, not merely interest
Choose meaningful inquiry actions before evaluating whether website traffic supports the business. Counting every button click as a lead inflates performance without showing that someone requested help.
A lead-producing session needs a documented definition linking measured activity to a genuine inquiry event. A button click, long visit or download may be useful behavior without meeting that standard. Keep the stages separate.
A worked example
A hypothetical visitor clicks a contact button three times but never submits the form. Another submits successfully after two sessions. Counting all contact clicks as lead-producing sessions overstates known inquiry activity and says nothing about unique new leads.
How to apply it
- Choose the inquiry events that qualify and test their success conditions.
- Separate session-level outcomes from deduplicated person-level records.
- Document cases where consent or an external tool prevents a reliable session link.
What the result can establish
A measured session count remains a measurement result, not a complete census of all prospects. Reconcile with supported source records where possible and preserve unmatched cases. Do not fill gaps by assuming every engaged visit produced a lead.
Reference: Google Analytics: recommended events.
Supporting documentation
Google Analytics: recommended eventsGoogle Analytics: engagement and bounce rateGoogle Analytics: attribution overview