Marketing Qualified Lead (MQL): Definition, Criteria, and Examples

A marketing qualified lead (MQL) is a person or account that meets a company’s agreed criteria for a defined marketing or sales follow-up step. There is no universal MQL threshold that applies to every business. The label is useful only when marketing and sales can explain what evidence qualifies a record and what happens next.

What an MQL should mean

An MQL typically indicates that the record fits the audience the business can serve and has shown enough relevant evidence for a specific next action. That action might be a sales review, a tailored education path, or further qualification. It does not automatically mean the buyer is ready for a meeting, has an approved budget, or is evaluating a purchase.

Separate market fit from engagement. Industry, geography, company size, use case, and role may help determine fit. A direct product request, an event interaction, or repeated engagement may provide context about interest. The team should state which combinations matter and whether a particular high-intent request bypasses a general score threshold.

Set observable MQL criteria

Build criteria from the organization’s real customer profile and sales process. For each field or signal, write its source, freshness, reliability, and what decision it can support. Define disqualifiers, unknown cases, duplicates, and records that should not be contacted. Missing data should not silently count as proof of poor fit or strong intent.

A score can help prioritize records for review if its components stay transparent. The guide to building a B2B lead scoring model explains how to separate fit, engagement, negative signals, and validation against outcomes. A score is an input to the rule, not a substitute for an agreed definition.

MQL vs. SQL

An MQL has met marketing’s defined threshold for its next step. A sales qualified lead (SQL) has been reviewed against the sales team’s acceptance criteria and is suitable for active sales follow-up under that process. Some organizations use different stages or terms, but each transition should have an owner, observable evidence, and a recorded result.

Use the MQL vs. SQL handoff guide to align definitions, response expectations, and return reasons. A direct request for a conversation may warrant prompt routing even if the person has not accumulated a prescribed number of marketing interactions.

Example MQL decisions

In a hypothetical B2B service company, a relevant operations leader downloads an introductory guide but has not described an active project. The person may fit the target profile, while the interaction supports continued education rather than immediate sales outreach. Another person from a suitable account requests a scoped discussion and identifies a current problem; that direct request may meet the sales-review criteria.

A third record may submit a form from a region the company cannot serve. Even if the activity score is high, it should not qualify for a sales handoff. These examples show why fit, request type, timing, contact preferences, and delivery scope matter alongside engagement.

Design the handoff and feedback loop

Define who receives an MQL, what context accompanies it, how quickly it is reviewed, and which statuses can be returned. Useful return reasons include timing, no fit, insufficient information, duplicate, unable to contact, active opportunity, and no permission. A broad “rejected” value hides different fixes and should not combine them.

Keep the original source and earlier campaign context when a record changes status. Record the date, owner, reason, and later outcome so teams can compare cohorts. If sales repeatedly returns a particular segment, inspect examples and ask whether the criteria, data, routing, or follow-up process is responsible.

Measure MQL quality rather than volume alone

Track the number of MQLs with a stable definition, the share accepted by sales, time to review, return reasons, opportunity progression, and eventual customer outcomes where the cohort has matured. Compare like periods and segments. A high acceptance rate may still reflect a narrow process that misses valid demand, while a high volume can overwhelm sales capacity.

• Use a written definition that can be applied to real examples.
• Keep MQL, SQL, opportunity, and customer outcomes distinct.
• Record exceptions and the reason for each returned record.
• Review qualification rules when the market, offer, or sales capacity changes.

An MQL is an operating definition, not a universal buyer state. When the criteria are clear, the handoff is timely, and outcomes feed back into the process, the label helps marketing and sales coordinate without exaggerating what a marketing interaction proves.