Traffic-to-lead conversion: formula and how to improve it
Traffic→lead conversion shows what share of visitors or sessions turns into valid leads. The metric reflects traffic relevance, offer strength, landing page/form quality, and the speed of handling inquiries.
What the Metric Measures
The ability of traffic and pages to generate sales opportunities. It allows you to compare channels, audiences, and landing pages and to identify bottlenecks (CTA, form, speed, trust).
Calculation
- CRtraffic→lead, % = (Number of valid unique leads / Number of sessions or unique visitors) × 100
- CRclick→lead, % = Leads / Clicks on CTA/landing page × 100
- Form Completion, % = Form submissions / Form starts × 100
- Quality: MQL/SQL and Lead→Sale, %
- CAC ≈ CPL / (Lead→Sale)
Agree on attribution (7/28 days, click/view), cross-channel deduplication, accounting for calls and offline leads, and anti-fraud.
Calculation example
In a month the website had 20,000 visitors and 360 left an enquiry or called. Conversion = 360 / 20,000 × 100 = 1.8%. If search ads convert at 3.2% and social media at 0.6%, channels should be judged separately, not by the average.
Data Sources
Web analytics/MMP, CRM/billing, website forms/chat, call tracking, ad platforms (UTM), heatmaps/session recordings, speed metrics (Core Web Vitals).
Interpretation
- Rising CR — a more relevant audience, a stronger offer/UX, a simpler form, a faster page
- Low CR — mismatched expectations, a weak CTA, form friction, slow loading, mobile version issues
- Evaluate together with MQL/SQL and Time-to-First-Contact
Useful Breakdowns
- Channels / campaigns / creatives / keywords
- Audiences, devices/browsers, geo/language
- Entry pages and landing pages
- New vs returning users; time of day/days of the week
- Lead type: form / call / chat
Dashboard Visualizations
- Funnel Visit→CTA click→Form start→Lead with percentages
- Trend of CR traffic→lead and Form Completion
- Heatmap of drop-offs by form question
- A/B comparison of landing pages and CTAs
- Conversion map by channel/audience
- Plan/actual with thresholds
How to Set Goals
Take a historical baseline by channel/device and set targets for CR and Form Completion together with a minimum MQL/SQL Rate. Define a response SLA, page speed thresholds, and an A/B testing plan (offer, headline, CTA, form, trust).
Common Mistakes
- Mixing sessions and users, no deduplication
- Spam/bots counted as leads
- Different attribution windows; call tracking/offline not accounted for
- Ignoring mobile issues and page speed
- Focusing only on "quantity" without quality and handling speed
Questions for Discussion
- What will raise CR faster: a shorter form or a stronger offer/CTA?
- Where is the main drop-off in the funnel, and why?
- What is the response speed, and how does it affect Lead→Sale?
- Which channels have high CR but low quality, and vice versa?