Lead-to-MQL conversion rate
Lead-to-MQL conversion rate is the percentage of captured leads that meet a marketing-qualified-lead (MQL) bar — typically a scoring or fit threshold marketing applies before passing a lead toward sales. It measures top-of-funnel quality. Because the MQL definition is set internally (fit criteria, scoring rules), the rate is an organization-specific convention, not a standardized metric.
What this means
Lead-to-MQL rate = number of leads that became MQLs ÷ total leads, over a period. A 'lead' is any captured contact (a form fill, a download, an inquiry); an MQL is a lead that meets marketing's qualification bar — often a lead score crossing a threshold, plus fit criteria such as company size or role. The rate is the first conversion step in a lead-gen funnel.
Why it is a convention
There is no external standard for what counts as an MQL — each organization defines its own scoring model and fit rules, and frameworks from marketing-automation vendors differ. As a result, lead-to-MQL rates are comparable only within one definition; benchmarking against another company's rate compares incompatible bars. The rate is also gameable in both directions: loosening the MQL definition raises it without improving real quality. Read it alongside MQL-to-SQL rate to see whether 'qualified' leads actually convert downstream.
This page is educational and not legal advice.
- Leads that became MQLs ÷ total leads, in a period
- MQL bar is set internally — scoring plus fit criteria
- Not comparable across companies with different bars
How it appears in analytics and logs
A low lead-to-MQL rate means much of the captured volume does not meet the quality bar — a targeting or source problem. A very high rate may mean the MQL bar is set too low to be meaningful.
Diagnostic use case
Measure how much of raw lead volume clears the marketing-qualified bar, to judge lead quality separately from lead quantity.
What WebmasterID can help detect
WebmasterID measures first-party acquisition and form/CTA events, helping ground the lead-source side of qualification without cross-site tracking.
Common mistakes
- Benchmarking the rate against other companies' MQL bars.
- Loosening the MQL definition to inflate the rate.
- Reading it without the downstream MQL-to-SQL rate.
Privacy and accuracy notes
The rate aggregates lead and MQL counts and needs no third-party identifiers. Lead records should be handled per applicable privacy rules; this page is educational, not legal advice.
Related pages
- MQL-to-SQL conversion rate
MQL-to-SQL conversion rate is the percentage of marketing-qualified leads (MQLs) that sales accepts and promotes to sales-qualified leads (SQLs). It measures alignment at the marketing-to-sales handoff: how often marketing's 'qualified' leads meet sales' bar. Because both MQL and SQL are defined internally, the rate is an organization-specific convention rather than a standardized figure.
- Cost per lead (CPL)
Cost per lead (CPL) is marketing spend divided by the number of leads generated in a period. It measures the cost of capturing a contact — a form fill, a download, an inquiry — before any qualification or sale. It sits earlier in the funnel than cost per acquisition (CPA), which counts paying customers, and it says nothing about lead quality, so it must be read with downstream conversion rates.
- Lead velocity rate (LVR)
Lead velocity rate (LVR) is the percentage growth in qualified leads from one month to the next. It is a forward-looking pipeline indicator: because today's qualified leads become tomorrow's revenue, a rising LVR signals future growth ahead of bookings. It is a go-to-market convention that depends on a consistent definition of 'qualified lead' to be meaningful month over month.
- CTA tracking
Measure first-party lead-capture events.
Sources and verification notes
- Google — [GA4] Key events (conversions)Background on marking lead/conversion events; the MQL bar itself is an internal convention.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.