Clicks, enquiries and qualified opportunities are different metrics
A click shows an interaction, an accepted enquiry shows confirmed receipt and a qualified opportunity shows assessed commercial fit.
AI-assisted practical guide · Editorial approach
The useful starting point
A click shows an interaction, an accepted enquiry shows confirmed receipt and a qualified opportunity shows assessed commercial fit. Define each separately. Combining them into one lead total can obscure failures in the form, receiving process or offer relevance.
Understand the decision
Map the states from page visit to agreed next step. Identify which system proves each state and how records are deduplicated. A mailto click does not prove an email was sent; a submit attempt does not prove storage. Ask the receiving team to define qualification rather than inferring it only from a marketing event.
A practical approach
Define each event and business state before implementing tracking. Distinguish page visits, contact clicks, form attempts, accepted enquiries and qualified opportunities. Match reports to these definitions. Test whether an interruption or retry creates duplicate events. Collect only the information needed for the agreed measurement purpose; contact details and free-text enquiry content should not be copied into general analytics events.
- Define every event and commercial stage.
- Identify the source of truth for each.
- Deduplicate retries and repeated interactions.
- Report transitions rather than one blended total.
Illustrative example
A consultancy could record a contact-page visit, a form start and a durable acceptance as distinct events. Its team would later assess scope fit. A visitor who opens email instead would remain a contact interaction unless a receiving record confirms the enquiry.
A mistake to avoid
Do not claim that every button interaction created a lead. The metric's name should reflect the evidence behind it.
What to review
Compare state counts for the same period and scope, investigate gaps and record unavailable stages without filling them with assumptions.
Turn the guide into a working brief
Write a measurement dictionary containing event names, trigger conditions, exclusions, owners and known gaps. Compare the analytics report with the receiving system for the same period and document differences rather than forcing the numbers to match. Use small experiments with a written hypothesis and one primary decision. Report uncertainty, missing consent and unavailable data plainly so the team does not mistake a partial view for complete attribution.
Common questions
What should I prepare before asking for help?
Start with this checklist: Define every event and commercial stage. Identify the source of truth for each. Deduplicate retries and repeated interactions. Report transitions rather than one blended total. Add your business context, existing materials and the decision you need to make. A useful initial brief can include uncertainty; you do not need to invent answers before discussing scope.
How should I judge whether the work helped?
Compare state counts for the same period and scope, investigate gaps and record unavailable stages without filling them with assumptions. Keep the observation period and definitions visible. Use the responsible team's evidence alongside the website journey; do not attribute every change in results to one asset or article.
Sources & scope
AI-assisted practical guide. Examples are illustrative; business-specific facts and sector claims need the responsible owner’s approval.
- W3C WAI: Forms Tutorial
Reference for accessible labels, instructions and feedback. Original business examples are illustrative, not research findings or verified client results.
Use this guide to start your brief.
Share your business context, existing materials and what is still unclear. The guide title will be included so the conversation starts with the right problem.
Prefer email? Send a brief with this guide’s context.Related guides
A measurement plan before redesigning a website
A measurement plan defines the problem, intended improvement, observable events and commercial review before a redesign begins.
Read the guide →Campaign attribution when the data is incomplete
Attribution estimates which touchpoints are associated with outcomes under a particular model and available data.
Read the guide →Tracking enquiry events without collecting private messages
Enquiry analytics should describe the stage of the interaction using a small approved event vocabulary.
Read the guide →