Marketing Qualified Account (MQA): Meaning, Rules, and Limits

A Marketing Qualified Account (MQA) is an organization, not a person, that has met a qualification rule your marketing team defined, so it gets flagged for review, routing, or sales attention. Some teams require fit and engagement together, others accept a predictive score on its own, and some add a time window. The label tells sales which accounts deserve a look. It does not tell them a purchase is coming.

Marketing may combine signals associated with an organization, while sales may evaluate several buying groups and opportunities within that same account. An MQA connects account-level qualification with downstream review, but it does not identify which opportunity is ready to progress.

How a Marketing Qualified Account Works

The account is the unit being labeled

Lead-level stages describe people. An MQA describes the company those people belong to. The 6sense product glossary defines its marketing qualified lead and sales qualified lead entries at the level of individual leads, while its qualified account object belongs to the account. The Demandbase journey stage documentation likewise maps accounts, not contacts, into stages, and MQA is one of those account stages. An account can qualify while none of its contacts would pass a lead score, and a contact can pass a lead score at an account that never qualifies.

Where activity-based signals come from

Organizations do not click links. People do. When a rule draws on activity, the process attaches evidence to a single account record, such as activity from known contacts, anonymous website visits matched to a company, or outside data such as firmographic fit or third-party intent. Other rules rely on fewer or different inputs, and the mechanics differ by platform.

The qualification rule is a local choice

The vendor implementations reviewed here do not share one mandatory MQA qualification rule. In the default Demandbase setup, an account can enter the MQA stage by meeting either a predictive score condition or an engagement condition, so both are not required. The 6sense documentation on qualified accounts lets each customer configure the filter groups that produce its qualified accounts. The Clay glossary entry on MQAs describes several identification strategies built from fit, intent, and engagement. The inputs and the logic change from one example to the next. What stays constant is that someone in the organization decided what "qualified" means, and that decision can be wrong. Wherever the rule runs, whether in an account platform, a CRM workflow, or a marketing automation setup, version it like any other business rule.

MQA vs MQL, SQL, and Opportunity

An MQA is one qualification state used inside account-based marketing (ABM), not the strategy itself. Selecting target accounts, running campaigns to them, and coordinating sales outreach are ABM activities. Deciding that a specific account has crossed a defined threshold is the MQA step. The table separates four labels that are often confused.

These labels can coexist. The Clay entry describes companies using MQL and MQA processes together rather than choosing one. 6sense documents using its own qualified account object, the 6QA, in place of an SQL stage inside its platform, but the 6QA remains one vendor's implementation, not a universal synonym for MQA. Treat any claim that MQAs replace MQLs or SQLs as an organizational choice, not a rule established by the sources reviewed here.

Signals That Can Feed an MQA Rule

Fit, engagement, intent, and prediction answer different questions

Fit asks whether the account resembles the customers you serve well. Engagement asks whether people at the account are interacting with you, for example through website visits or responses to campaigns and content programs. Intent asks whether the account appears to be researching relevant topics elsewhere. A predictive score is a model output whose meaning depends on the model and its data. The 6sense glossary keeps profile fit and intent data as separate entries. A fit signal is not a clock. It says nothing about timing. An intent spike is not a budget either. Combining inputs may add context, but whether the resulting rule performs better must be evaluated against later dispositions and outcomes.

Time windows, stage changes, and persistent flags

Qualification has a time dimension, and products handle it differently. Three mechanisms are easy to blur: a rolling window that only counts recent activity, a stage change that moves an account forward or back, and a flag that stays on for a set period.

• The Demandbase default MQA condition is a Pipeline Predict Score of at least 85 percent or at least 100 Marketing Engagement Points in the past three months, according to its documentation updated June 2, 2026.
• 6sense explains that an account can stay a 6QA for 60 days after certain drops in its buying stage.
• Adobe's engagement score documentation counts buying-group activity inside a 30-day window. That is a buying-group mechanism, not an MQA definition.

These figures describe the named products' documented behavior. They are not industry benchmarks, recommended qualification thresholds, or evidence that the systems improve sales outcomes. Before you trust an MQA count, find out whether the label means qualified now, qualified recently, or qualified at some point and not yet reset.

How many engaged contacts are needed

The sources reviewed here set no universal minimum. Some implementations aggregate activity from several people to avoid relying solely on one person's signals. That is a design choice, not a validated guarantee of better qualification. The Demandbase guidance on customizing journey stages suggests adding a condition based on known contacts and leads, for example a minimum of two. The INFUSE glossary entry on MQA describes ranking accounts with input from multiple leads. Both are configuration choices, not part of the definition.

Account Matching and Data Quality

When an MQA rule uses contact activity or anonymous website visits, those signals must be associated with the correct account before they can be interpreted reliably. Matching errors can distort the resulting qualification.

The Demandbase article on lead-to-account matching lists ways the process can miss a match or produce an ambiguous one, including several accounts sharing the same website, leads without an email address, and companies whose domains have changed. Anonymous identification carries its own limits. In its account identification FAQ, Demandbase states that identification is probabilistic rather than perfect, and it names shared IP addresses, remote work, subsidiaries, and regional coverage gaps among the complications.

Two points follow. First, an anonymous company match tells you which organization a visit probably came from, not which person made it. Second, a parent company and its subsidiaries can blur together, so activity from one business unit may lift the record of another. These documents describe failure modes. They do not report how often each one happens.

What Happens After an Account Qualifies

Sales review is a separate decision

Qualifying an account and accepting it into a sales process are two different events. The Demandbase playbook on MQA dispositioning centers on what happens to an MQA after handoff, with outcomes captured in the CRM. In the Clay example workflow, routing to sales comes after the qualification step, and the route itself is a design choice. A particular owner, sequence, or response time is not part of what makes an account an MQA.

Accepted, recycled, or disqualified

The Demandbase playbook, one vendor's proposed process, groups dispositions into successful, neutral, and unsuccessful outcomes. In that example, a qualified account can move forward toward an opportunity, go back to nurture because the timing is wrong, or be disqualified. A recycled account may qualify again if its configured criteria are met later, and 6sense documents requalification as a configurable behavior of its own object. An MQA that sales declines is not necessarily a broken rule, and an MQA that sales accepts is not yet a deal.

Where MQAs Can Mislead

One busy person is not a buying committee

Consider a hypothetical case. A single analyst at a large company downloads several reports and attends a webinar in the same week. An engagement-only rule could qualify the whole account on that activity alone, even though nobody with budget authority has appeared. Nothing in the label separates that situation from a genuine group evaluation. This is an illustrative scenario, not a measured pattern.

One account can hold several opportunities

In a Forrester blog post, analyst Terry Flaherty argues that an account-level label misrepresents the buyer much as a lead-level label does, because a large account can contain several buying groups pursuing different solutions at different stages. That is an analyst argument, not proof that every MQA program fails. Adobe's buying-group model shows one alternative granularity, since it treats member engagement and role completeness as separate measures. Neither approach defines an MQA. Both show what a single account score can hide.

What the label cannot prove

Being named an MQA does not establish that sales accepted the account, that a budget exists, that the relevant stakeholders are involved, that an opportunity has been created, or that a sale will follow. In the Demandbase example process, neutral and unsuccessful dispositions are expected outcomes, not exceptions. A claim that MQAs convert better than other accounts is a hypothesis to test against your own outcomes.

How to Evaluate and Calibrate an MQA Rule

The guidance below is a recommendation, not an industry standard. Its purpose is to make the rule auditable, so disagreements with sales start from evidence.

Record why each account qualified

Store the rule version, the threshold that applied, the date the rule fired, the account identifier, and the specific condition met. 6sense exposes a qualification reason and configuration details for its 6QAs, the kind of trail that makes review possible. Without that record, nobody can tell whether a bad MQA came from bad data or a bad rule.

Measure accounts and qualification events separately

One account can qualify, lapse, and qualify again. Count unique accounts apart from qualification episodes, and keep sales decisions apart from sales opportunities. Compare cohorts that qualified in the same period under the same rule version, and give each cohort time to reach a disposition. Crediting the campaigns that produced the qualifying activity is a separate question, closer to attribution modeling, and should be kept apart from judging whether the rule picked the right accounts.

Feed sales dispositions back into the rule

Rejection and recycle reasons are the most direct feedback a rule gets. The Demandbase playbook centers its process on capturing what happens to MQAs after handoff, and the vendor's customization guidance suggests reviewing stage definitions on a regular schedule, such as quarterly. If many accounts come back with the same rejection reason, that pattern is worth investigating before the rule runs again. The sources reviewed here establish no cross-vendor acceptance-rate benchmark suitable as a universal target, so judge every change against your own baseline. Teams designing account qualification as part of a wider program can see how Arfadia approaches B2B marketing solutions.

Frequently Asked Questions

What is a Marketing Qualified Account (MQA)?

A Marketing Qualified Account (MQA) is an account that meets a team's chosen qualification criteria, such as fit, engagement, or intent, and is flagged for review, routing, or sales attention. The label applies to the organization, not a single lead, and does not prove buying readiness.

How is an MQA different from an MQL?

An MQL describes one individual lead, while an MQA describes the whole account. An account can qualify while none of its contacts would pass a lead score, and the reverse can also happen. Teams can run both processes side by side instead of replacing one with the other.

Is there a standard MQA threshold or contact minimum?

Not in the sources reviewed for this entry. Each organization configures its own conditions, and the vendor documentation compared here uses different inputs and logic. A product default, such as the default stage rule in Demandbase, applies to that product only and is not a benchmark.

Does an MQA automatically become a sales opportunity?

No. Sales review is a separate decision. In one documented example process, a qualified account can be accepted and move toward an opportunity, be sent back to nurture, or be disqualified. A recycled account may qualify again if its configured criteria are met later.

Is a 6QA the same thing as an MQA?

A 6QA is the qualified account object inside the 6sense platform. It is one vendor's implementation of account qualification, not a universal synonym for MQA, and its behavior, including how long the status lasts, follows that platform's settings.

How should a team evaluate its MQA rule?

Record why each account qualified, count unique accounts separately from qualification events, compare cohorts that qualified under the same rule version, and review the reasons sales gives for each disposition. Judge changes against your own baseline, because the sources reviewed here establish no cross-vendor benchmark to use as a universal target.

Related Terms

• Account-Based Marketing (ABM): the broader strategy for selected accounts, of which an MQA is one qualification state.
• Marketing Automation: software that runs authored rules, including logic that can apply an MQA label.
• Attribution Modeling: assigns credit to touchpoints, a separate question from rule quality.

Sources

• Demandbase, Getting Started with Journey Stages (updated June 2, 2026)
• Demandbase, Best Practices for Customizing Journey Stages (updated June 2, 2026)
• Demandbase, How to build MQA dispositioning for revenue impact (date not shown)
• Demandbase, Understanding Lead to Account Matching (updated June 2, 2026)
• Demandbase, FAQs: Account Identification (updated June 3, 2026)
• 6sense, 6sense Qualified Accounts (6QAs) (updated June 8, 2026)
• 6sense, 6sense Product Glossary (published September 2, 2026)
• Adobe Experience League, Engagement scores (updated October 6, 2026)
• Adobe Experience League, Completeness scores (concept only)
• Forrester, Terry Flaherty, Why Marketing Qualified Accounts Are Not The Answer (April 14, 2022)
• Clay, Marketing Qualified Account (date not shown)
• INFUSE, What is Marketing Qualified Account (MQA)? (updated July 28, 2026)