Agree what each stage means
A visitor reading an article, clicking WhatsApp, submitting an enquiry and becoming a sales opportunity has crossed four different boundaries. Combining them into one conversion number makes the report easier to inflate and harder to use. Write the definitions with the person who actually handles enquiries before configuring events.
| Stage | Observable evidence | What it does not prove |
|---|---|---|
| Content engagement | Article view or reading interaction | Buying intent |
| Contact intent | A contact, telephone or messaging link click | A message was sent or call answered |
| Enquiry received | The receiving system confirms acceptance | The enquiry fits the business |
| Qualified lead | A reviewed enquiry meets defined criteria | A sale will close |
| Won project | The agreed commercial completion signal | Revenue from every earlier touchpoint |
Use criteria that support a real sales decision
For a software project, useful qualification dimensions might include service fit, a defined problem, a reachable contact and a plausible next step. Budget and timing can be useful when the business actually uses them to decide how to respond. Avoid collecting detailed personal information merely because a dashboard supports extra fields.
Record why an enquiry is disqualified, using a small controlled set of reasons such as unrelated service, spam or no actionable request. A low lead count with strong fit can be more valuable than many irrelevant submissions. Keep the criteria stable long enough to compare periods, and annotate changes when the definition evolves.
Connect measurement to actual application behavior
For a form, the success signal should come after the receiving system accepts the request. Browser validation passing is not enough. A mailto link opening a draft does not confirm delivery. If the site has no reliable success signal, report contact intent honestly while the delivery workflow is improved.
Google provides recommended Analytics events for lead-generation workflows. Choose an event whose meaning fits the observed action; do not label every CTA click as a generated lead. Keep a separate internal record of qualification outcomes in the system the sales team maintains.
Test an accepted request, a validation error, a network failure and a repeated submission. Confirm that each successful action is counted once, and failed attempts do not create success events. Use clearly identified test records and a controlled receiving destination so the test does not trigger an unintended customer communication.
Worked example: a campaign with many contact clicks
Imagine an illustrative campaign produces 100 visits, 12 contact-link clicks, four received enquiries and one qualified opportunity. Reporting 12 leads would obscure where the journey breaks down. The team should investigate whether people abandon the form, choose another contact method, encounter an error or discover that the service is unsuitable.
Use the same time window and be explicit about attribution limitations. Visitors may return on another device, contact the company offline or decline analytics. Analytics and CRM counts will not always match exactly. Investigate large discrepancies without forcing separate systems to produce an artificially identical total.
Continue with form-success measurement, duplicate-event prevention and CRM outcome reporting. Treat the dashboard as evidence for decisions, not a scoreboard of increasingly generous definitions.
A practical starting point
Work through these checks in order. Use the results to decide what needs to change in your own workflow.
- Agree the criteria for a relevant enquiry with sales.
- Separate raw submissions, accepted leads and opportunities.
- Document who updates each stage and when.
A student requesting an internship should not count as the same business outcome as a buyer requesting software development.
A mistake to avoid
Do not optimize campaigns solely toward the easiest action to generate.
How to check progress
Track lead acceptance and opportunity creation alongside submission volume.
Your action checklist
Use this checklist while reviewing your own setup. Checkmarks are temporary and stay in this open page.
Further reading
Official background resources for this topic. The workflow above is general guidance, not a guarantee of a particular result.
AI-assisted editorial content. Examples are illustrative, not client case studies. Read our editorial policy or report a correction.