What does quiz lead quality mean?
Quiz lead quality is the observed suitability and progress of a captured lead for a declared business process. Define the process, offer, market, state owner, and observation window before calculating a rate. Keep the quiz result, score, routing rule, human qualification decision, and customer outcome as separate fields so each can be audited and changed without rewriting history.
Google Analytics recommends distinct lead-generation events for generate_lead, qualify_lead, disqualify_lead, working_lead, close_convert_lead, and close_unconvert_lead. Those names are a useful reporting vocabulary, but the CRM or native contact record should remain the operational source of truth for ownership, status, reason codes, and later outcomes.
Related: Choose a qualification action boundary · Define denominator-safe quiz metrics
Sources: Google Analytics, Recommended events
Use a quality outcome ladder
Do not collapse different states into one good-lead flag. A lead can fit the market but be unready, ready but unreachable, or qualified but lost for a later reason. Use a versioned ladder with evidence for every transition.
| State | Stable definition | Required evidence |
|---|---|---|
| Captured | A valid completion created a contactable record | completion ID, person ID, capture time |
| Accepted | The record met declared intake rules | rule version, route, reason |
| Working | A representative or workflow began the next action | owner, action time |
| Qualified | A human or governed rule confirmed fit and readiness | qualification version, reason |
| Converted | The declared customer outcome occurred | outcome ID, time, value when appropriate |
| Closed unconverted | The opportunity ended without conversion | reason code, close time |
| Unresolved | The observation window ended without a terminal state | last status, owner, last action time |
Calculate cohort-safe quality rates
Select a cohort by capture date and allow the same mature observation window for every member. Useful transitions include accepted divided by captured, working divided by accepted, qualified divided by worked, converted divided by qualified, and closed unconverted divided by worked. Report the numerator, denominator, count, window, and unresolved total together.
For an illustrative 30-day cohort, suppose 120 leads were captured, 90 accepted, 72 worked, 36 qualified, 9 converted, 18 closed unconverted, and 45 remained unresolved. Qualified per worked is 36 divided by 72, or 50%. Converted per qualified is 9 divided by 36, or 25%. The unresolved 45 stay visible; recoding them as losses merely to finalize the report would change the question instead of answering it.
| Rate | Numerator | Denominator | Interpretation guardrail |
|---|---|---|---|
| Acceptance | accepted | captured | Intake policy, not customer value |
| Work start | working | accepted | Follow-up capacity affects the result |
| Qualification | qualified | worked | Depends on the governed definition |
| Conversion | converted | qualified | Requires a declared customer outcome |
| Unresolved share | unresolved at window end | captured | Do not silently drop missing states |
Sources: Google Analytics, Funnel exploration
Compare score bands without circular evidence
Freeze score bands before examining outcomes. Compare each band with the same observation window and show counts beside rates. Preserve disqualification and loss reasons so a high score cannot hide systematic mismatch. When thresholds change, assign a new rule version rather than rewriting historical scores.
Treat apparent lift as association until a suitable experimental or causal design supports more. Traffic source, seasonality, seller behavior, offer changes, and missing follow-up can all create differences between bands. NIST's experimental-design guidance begins with explicit objectives, variables, and design selection; a post-hoc score-band table does not supply those controls by itself.
Related: Design a controlled quiz experiment
Audit missing and human states
Require explicit reason codes for rejected, disqualified, closed unconverted, duplicate, test, and unreachable records. Keep a queue for missing owners and stale statuses. A missing status is not neutral: it weakens every downstream rate and can reveal an operational failure rather than low lead quality.
Collect only the data needed for the defined decision. Avoid copying sensitive answers or speculative inferences into broad analytics or sales fields. The ICO says personal data should be adequate, relevant, and limited to what is necessary and marks this guidance as under review following the Data (Use and Access) Act.
Related: Apply the data-minimisation checklist
Sources: ICO, Data minimisation principle
Lead-quality reporting checklist
Block publication of a quality claim until the cohort, states, evidence, and denominators are reproducible.
- Quality states have written definitions and owners.
- Quiz result, score, qualification, route, and human status remain separate.
- Cohorts use one capture date rule and one mature observation window.
- Every rate names its numerator, denominator, and count.
- Unresolved records and reason codes appear beside rates.
- Score and routing rule versions are preserved historically.
- Duplicate and test records are excluded by declared rules.
- Sensitive data is minimized and access controlled.
- Associations are not described as causal results.
What this method cannot prove
This method improves measurement consistency; it does not prove that the quiz itself is valid or predictive. Small cohorts can be unstable, downstream outcomes can be missing or shaped by follow-up capacity, and revenue may occur outside the selected window.
It does not replace statistical review, sales-process governance, privacy assessment, or legal advice. The worked numbers are synthetic and are not a benchmark for any product, industry, or campaign.
Evidence
How to reproduce the method
A versioned seven-state outcome ladder, cohort-safe transition table, synthetic 30-day worked example, score-band interpretation method, unresolved-record audit, and release checklist, verified against current Google Analytics, NIST, and ICO primary guidance on October 9, 2026.
Limitation
Where this conclusion stops
The method standardizes downstream measurement but does not validate the quiz, establish causality, eliminate missing or follow-up-biased outcomes, or provide a universal quality benchmark.
Sources and verification
What this guide relies on
- Google Analytics, Recommended events
- Google Analytics, Funnel exploration
- NIST, Choosing an experimental design
- ICO, Data minimisation principle
- The Lead Quiz Review editorial methodology
Sources and method checked October 9, 2026. External standards are linked to their primary publishers. Request a factual correction.