Reporting and lead quality · ASRR Tech
Measure organic leads: from search visit to qualified enquiry and order
Measure search traffic, enquiries, qualification and sales as separate steps. Use this plan with definitions, a worked funnel and checks for duplicate leads, demonstrations and missing source information.
Updated · 4 min read · ASRR Tech
Start with the business outcome
Search traffic is useful when it produces suitable enquiries. A visit, form submission and order are different events. Define a lead and qualified lead before reporting.
A working definition might be a unique genuine request about your offering with enough information for follow-up. Qualification adds agreed criteria such as product fit, service area and a concrete need. Keep “unknown” when information is missing rather than automatically disqualifying.
This is a measurement plan to configure, not a claim of achieved results or automatically available Alpha tracking.
Connect three sources without treating them as identical
| Source | Useful information | Unsupported conclusion |
|---|---|---|
| Search Console | Impressions, clicks, queries and pages | Which individual searcher became a customer |
| Webanalytics | Visits, landing pages and measured events | That every submission is a genuine opportunity |
| CRM | Qualification, appointments, offers and outcomes | That an unknown source was organic |
Search Console reports search performance through its own dimensions and filters. Use it for visibility and page investigation, not customer identity.
Google Analytics separates first-user, session and event scopes. Decide which perspective you report. A first visit from Google and a later enquiry from email can both be accurate but answer different questions.
Preserve source information with the enquiry
A useful record includes enquiry ID, received date, landing page where reliably known, source/medium, campaign information when present, request type, qualification and outcome. Preserve the original source alongside later interactions.
Connect appointments and opportunities through a stable enquiry reference. Do not send names, phone numbers or free-text intake content as analytics parameters. Keep identifying customer information in its designated environment.
Visitors can decline cookies, return on another device or call directly. Retain “source unknown”. Self-reported “how did you find us?” is additional information, not the same as a technically measured source.
A fictional funnel with explicit denominators
Suppose a defined set of organic landing sessions produces 2,000 visits and 60 unique requests. Eighteen qualify, twelve book demonstrations, eight attend and three become orders.
| Metric | Calculation | Result |
|---|---|---|
| Enquiry rate | 60 / 2,000 | 3% |
| Qualification rate | 18 / 60 | 30% |
| Booking from qualified | 12 / 18 | 66.7% |
| Attendance from bookings | 8 / 12 | 66.7% |
| Order from attended demos | 3 / 8 | 37.5% |
These invented figures explain the method, not benchmarks. Use the same population and an explicit observation date. Last month's enquiry may become this month's order. Counting only activities occurring this month differs from measuring eventual conversion of that enquiry cohort.
Avoid four measurement mistakes
Booking equals attendance. Keep booked, cancelled, rescheduled, no-show and completed distinct. A rescheduled demonstration is not another unique lead.
Submission attempts equal leads. Deduplicate technical repetition and exclude spam or internal tests explicitly. Retain enough evidence to review the selection.
Branded equals nonbranded demand. Describe a Search Console query filter for brand variants. Do not claim complete coverage: some query data is omitted and reports may use different boundaries.
Small percentages establish a trend. Two orders from four demos is 50%; three is 75%. One outcome causes a large change. Show counts and examine records before dismissing a channel.
Make content decisions using quality
Compare landing pages by suitable requests and next steps, not clicks alone. A low-traffic guide may attract highly relevant enquiries. High traffic with unsuitable questions may call for clearer titles, audience or explanation.
Maintain a short weekly table: page, traffic, unique requests, qualification, completed conversations, known outcomes and one improvement. Trace surprising totals to individual records.
Measurement acceptance checklist
Test an organic route, campaign visit, direct request, repeated submission and rescheduled demo. Verify source, enquiry reference and eventual outcome. Reconcile sample totals against underlying records.
Continue with capturing lead details and pipeline amounts. Useful measurement makes knowledge, gaps and supported decisions explicit.
Sources and editorial approach
Sources consulted on 12 October 2026. Inline references support the stated facts. ASRR compiled the workflows, matrices and fictional examples for this explanation. Example prices and outcomes are not customer results, prices or benchmarks. Other vendors’ documentation does not establish availability in Alpha.