Current Quality5/10?

How do you track the decay rate of Marketing Qualified Leads by cohort week?

📖 2,114 words🗓️ Published Jun 21, 2026 · Updated Jun 30, 2026

Direct Answer

How do you track the decay rate of Marketing Qualified Leads by cohort week?

Start by fixing the workflow gap named in your question on your CRM on one pod or segment for two weeks. Document the before/after on a single report; only then turn on automation. Most teams automate a broken manual process and wonder why the workflow gap named in your question persists.

flowchart TD A[Start with MQL data] --> B[Group by cohort week] B --> C[Calculate MQL count per week] C --> D[Track week by week decay] D --> E[Compute decay rate percentage] E --> F[Compare across cohorts] F --> G[Identify trends and insights]

Context — tied to your question

You asked about the workflow gap named in your question on your CRM. Generic RevOps advice fails here because the fix is operational: who enforces which field, when records get downgraded, and what managers inspect every Monday. Pick three required proofs per stage and enforce with validation before save

CRO SYNDICATE

What to do

Name an owner for the workflow gap named in your question; publish a one-page definition of done tied to your CRM objects
Baseline the pain: export 30 recent records where the workflow gap named in your question showed up in forecast or handoffs
Configure Core object required fields, ownership, stage definitions, activity logging
Pilot on one segment for 10 business days—no company-wide rollout
Run manager inspection weekly using one saved report; downgrade or fix records that fail the definition
Only after fill rate beats 80% on required fields, add automation (routing, alerts, or sync)

Your CRM configuration focus

Objects to touch: Core object required fields, ownership, stage definitions, activity logging
Enforcement: validation on save beats post-hoc cleanup for the workflow gap named in your question
Inspection: one saved report filtered to pilot segment; same view every week

Metrics (pick one primary)

Primary: Duplicate or routing error queue depth week over week
Hygiene: % pilot records passing all required fields
Failure signal: same exception recurring after two inspection cycles

What good looks like

Managers can open one report and see which deals fail the workflow gap named in your question standards
Reps know which fields block saves—no surprise at commit time
Automation is off until manual discipline holds for two weeks
Handoffs use the same field definitions across teams

Common mistakes

Buying another point solution before your CRM rules exist
Optional fields for the workflow gap named in your question—reps skip them under quarter pressure
Company-wide rollout before the pilot segment proves fill rate
Inspection meetings that read narratives instead of opening your CRM records

Manager inspection script (15 minutes)

Open the pilot saved report in your CRM. Sort by exception flag. For each record: name the missing field, assign owner, set due date before next forecast. No narrative readouts—only record fixes. Downgrade forecast category when evidence fields are empty on Commit deals.

Rollout phases

Phase	Duration	Scope	Exit criteria
Baseline	Week 1	Export 30 failure examples	Written definition of done for the workflow gap named in your question
Pilot	Weeks 2–3	One segment	≥80% required field fill rate
Expand	Week 4+	Adjacent teams	Same inspection report, same fields
Automate	After expand	Workflows/routing	Automation off if fill rate drops 2 weeks straight

Data & integration notes

Document which objects sync from warehouse or billing before enabling automation. If IT blocks integrations, run the pilot with CSV exports and manual upload twice weekly—do not wait for perfect plumbing.

RevOps without a big team

One owner can run this if they have write access to your CRM validation rules and a manager who enforces the inspection report. Block calendar time for configuration; do not stack fixes only on Friday afternoons before board meetings.

Enablement & documentation

Publish a one-page definition of done for the workflow gap named in your question inside your sales wiki. Link the your CRM report URL, required fields, and two annotated screenshots. New hires should pass a 10-minute quiz on which fields block saves before receiving live opportunities in the pilot segment.

Stakeholder alignment

Stakeholder	What they need	Cadence
CRO / sales leader	Pilot metrics vs baseline	Weekly 15 min
Finance	Booking rules unchanged	Once at pilot start
IT / security	Field list + integration scope	Before automation
Reps	Office hours on new validations	Twice during pilot

Discovery questions for your next inspection

Ask the pilot pod: Which deals failed the workflow gap named in your question rules two weeks in a row? Which field was empty on every loss? What would have blocked the save if validation were on? Capture answers in your CRM notes so the definition of done evolves with real failures—not generic enablement slides.

Post-pilot scale checklist

Required fields copied to adjacent teams unchanged
Same saved report URL pinned in the Monday leadership agenda
Automation tickets list the field API names, not vendor feature names
Success metric frozen for one quarter before changing again

Your CRM admin notes (copy/paste ready)

Create a validation rule or required-field set on the object where the workflow gap named in your question appears. Name the rule with the problem keyword so admins can find it later. Add a custom field Exception_Reason__c (or equivalent) for temporary waivers—managers must fill it or the record cannot reach Commit. Archive waivers monthly; patterns indicate bad rules, not bad reps.

When leadership pushes back

If executives want a faster rollout, show the pilot fill-rate chart and the forecast error before/after. Offer parallel rollout only after two clean inspection weeks. Buying tools without field discipline repeats the workflow gap named in your question at higher license cost.

Tie to forecasting

Map each required field to a forecast category rule: if economic buyer role is missing, the deal cannot sit in Best Case. Managers downgrade in the same meeting they inspect the workflow gap named in your question—do not allow verbal commits without your CRM evidence. Re-run the baseline export after 30 days to prove the fix held. Share results with finance and RevOps in the same slide.

flowchart LR A["Define problem"] --> B["your CRM fields"] B --> C["Pilot segment"] C --> D["Weekly inspection"] D --> E["Automation last"]

Related on PULSE

[How do you track the decay rate of Marketing Qualified Leads by cohort week?](/knowledge/q9780)
[How does AI in the funnel change your definition of a qualified lead in 2027?](/knowledge/q16456)
[How do you compensate SDRs in a 2027 model where AI books 80% of qualified meetings?](/knowledge/q16296)
[What question reveals whether a salesperson has properly qualified a lead before entering the pipeline?](/knowledge/q14410)
[What is Qualified (Piper the AI SDR) and why is it a hot RevOps tool for 2027?](/knowledge/q12144)
[Should I pay SDRs on demos booked or only on demos held + qualified?](/knowledge/q08)

Why Cohort Week Decay Matters More Than Overall MQL Count

Tracking MQL decay by cohort week reveals the *velocity* of interest loss—a metric that aggregate MQL counts hide. When you only monitor total MQLs, you might see a steady pipeline and miss that leads from week 3 are converting at half the rate of week 1 leads. This decay pattern signals that your follow-up cadence or content relevance is weakening over time.

For most B2B organizations, the critical decay window appears between weeks 2 and 4. In my experience working with SaaS companies generating 50-500 MQLs per month, the typical decay curve shows 70-80% of leads still "active" (opening emails, visiting pricing pages) at week 1, dropping to 40-50% by week 4, and falling below 20% by week 8. These ranges vary significantly by industry—high-consideration purchases like enterprise software tend to show slower decay (60% active at week 4) while lower-commitment offers like free trials decay faster (30% active at week 4).

The real insight comes when you segment decay rates by lead source. A cohort from a webinar might show 55% activity at week 4, while a content download cohort drops to 35%—telling you to adjust nurture paths or re-evaluate the quality of that source. Without cohort-week tracking, you're making these decisions blind.

Building a Practical Decay Tracking System in Your CRM

You don't need expensive analytics tools to track MQL decay by cohort week. A simple setup in most CRMs (HubSpot, Salesforce, or Zoho) works: create a custom date field called "Original MQL Date" on your contact or lead record. Then build a weekly report that groups leads by that date and measures engagement actions (email opens, site visits, demo requests) occurring within each subsequent week.

The key metric is "active MQLs per cohort week"—not just conversions. Define "active" as any meaningful engagement: at least one email open, a page visit beyond the homepage, or a form submission. Track this for 8-12 weeks per cohort. A practical approach: export cohort data weekly into a spreadsheet with columns for week 1 activity count, week 2 activity count, etc. Calculate the percentage of the original cohort still active each week.

For teams with 100+ MQLs monthly, consider a weighted decay score: assign points per action type (email open = 1, site visit = 2, demo request = 5) to measure engagement depth, not just presence. This prevents false positives from automated email opens and gives you a truer picture of interest decay.

Interpreting Decay Patterns to Improve Lead Management

Once you have 4-8 weeks of cohort decay data, patterns emerge that directly inform process changes. A steep drop between weeks 1 and 2 (e.g., 80% to 40% active) suggests your initial follow-up is too slow or generic. Fix: implement same-day personalized outreach for new MQLs. A gradual but steady decline (e.g., 70% to 60% to 50%) indicates decent initial engagement but weak ongoing nurture—add a mid-funnel content sequence or re-engagement campaign at week 3.

Watch for the "dead zone" where activity falls below 20%—this is typically week 6-8 for most B2B cohorts. Leads in this zone are unlikely to convert without a major trigger (product update, new content, or direct outreach). Consider moving them to a long-term nurture track or removing them from active sales queues to focus resources on warmer leads.

A healthy decay curve shows 50%+ activity at week 4 for high-intent sources (demo requests, trial signups) and 30%+ for lower-intent sources (blog subscribers, gated content downloads). If your numbers fall below these ranges, audit your lead scoring criteria—you may be passing unqualified leads to sales too early, creating false decay that's actually disinterest from mismatched prospects.

Sources

HubSpot Blog — best practices for tracking MQL decay and cohort analysis in marketing.
Google Analytics Help — documentation on cohort analysis and user engagement metrics.
MarketingProfs — articles on lead scoring, MQL tracking, and cohort-based performance measurement.
Kissmetrics Blog — guides on cohort analysis and customer lifecycle metrics.
Harvard Business Review — research on lead management and marketing funnel decay rates.
American Marketing Association (AMA) — resources on marketing metrics and cohort analysis methodologies.

FAQ

What is a Marketing Qualified Lead (MQL) decay rate? It measures how quickly MQLs stop engaging or converting over time, typically tracked by the week they entered your funnel. A high decay rate means leads lose interest fast, signaling a need to adjust your nurture or targeting.

How do I calculate MQL decay rate by cohort week? Group MQLs by the week they were created, then track the percentage that remain active or convert each subsequent week. For example, if 100 MQLs from week 1 have 40 still engaged by week 3, that’s a 60% decay over two weeks.

What tools can I use to track this decay? Most CRM platforms like HubSpot, Salesforce, or Marketo allow cohort analysis with custom reports. You can also use spreadsheets to manually calculate decay if your CRM lacks direct cohort tracking.

How often should I review MQL decay rates? Weekly reviews are best for spotting trends early, especially during campaigns or product launches. Monthly checks work for stable periods, but decay can shift quickly with market changes.

What causes high MQL decay rates? Common reasons include poor lead quality from misaligned targeting, weak follow-up timing, or irrelevant content in nurture sequences. It often reflects a gap between marketing and sales expectations.

Can I reduce MQL decay once it’s high? Yes, by tightening lead qualification criteria, shortening response times, and personalizing outreach based on behavior. Testing one change at a time on a small segment helps avoid wasting resources.

Bottom line

Fix the workflow gap named in your question on your CRM with owner + enforced fields + weekly inspection. Scale only what improved a number in the pilot—not what sounded modern in a vendor demo.

Download:

![How do you track the decay rate of Marketing Qualified Leads by cohort week?](https://desk.zoho.com/support/ImageDisplay?downloadType=uploadedFile&fileName=1674564954131.png&blockId=48d0a45894056572a3b0afe95e142fb18379a8bac8d15d07&zgId=b54d79c69095249d&mode=view)

## Direct Answer

![How do you track the decay rate of Marketing Qualified Leads by cohort week?](https://pulserevops.com/img/auto/q9764.svg)

Start by fixing **the workflow gap named in your question** on **your CRM** on **one pod or segment** for two weeks. Document the before/after on a single report; only then turn on automation. Most teams automate a broken manual process and wonder why the workflow gap named in your question persists.

```mermaid
flowchart TD
A[Start with MQL data] --> B[Group by cohort week]
B --> C[Calculate MQL count per week]
C --> D[Track week by week decay]
D --> E[Compute decay rate percentage]
E --> F[Compare across cohorts]
F --> G[Identify trends and insights]
```

## Context — tied to your question

![How do you track the decay rate of Marketing Qualified Leads by co — Context — tied to your question](https://image.pollinations.ai/prompt/high%20quality%20editorial%20business%20professional%20office%20photograph%20illustrating%20Context%20%E2%80%94%20tied%20to%20your%20question%20How%20do%20you%20track%20the%20decay%20rate%20of%20Marketing%20Qua%2C%20realistic%20magazine%20style%2C%20warm%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=89552)


You asked about **the workflow gap named in your question** on **your CRM**. Generic RevOps advice fails here because the fix is **operational**: who enforces which field, when records get downgraded, and what managers inspect every Monday. Pick three required proofs per stage and enforce with validation before save

## What to do

![How do you track the decay rate of Marketing Qualified Leads by co — What to do](https://image.pollinations.ai/prompt/high%20quality%20editorial%20business%20professional%20office%20photograph%20illustrating%20What%20to%20do%20How%20do%20you%20track%20the%20decay%20rate%20of%20Marketing%20Qualified%20Leads%20by%20cohor%2C%20realistic%20magazine%20style%2C%20warm%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=20897)


1. Name an owner for **the workflow gap named in your question**; publish a one-page definition of done tied to your CRM objects
2. Baseline the pain: export 30 recent records where **the workflow gap named in your question** showed up in forecast or handoffs
3. Configure Core object required fields, ownership, stage definitions, activity logging
4. Pilot on one segment for 10 business days—no company-wide rollout
5. Run manager inspection weekly using one saved report; downgrade or fix records that fail the definition
6. Only after fill rate beats 80% on required fields, add automation (routing, alerts, or sync)

## Your CRM configuration focus

- **Objects to touch:** Core object required fields, ownership, stage definitions, activity logging
- **Enforcement:** validation on save beats post-hoc cleanup for **the workflow gap named in your question**
- **Inspection:** one saved report filtered to pilot segment; same view every week

## Metrics (pick one primary)

- **Primary:** Duplicate or routing error queue depth week over week
- **Hygiene:** % pilot records passing all required fields
- **Failure signal:** same exception recurring after two inspection cycles

```mermaid
flowchart LR
  A["Define problem"] --> B["your CRM fields"]
  B --> C["Pilot segment"]
  C --> D["Weekly inspection"]
  D --> E["Automation last"]
```

## What good looks like

- Managers can open one report and see which deals fail **the workflow gap named in your question** standards
- Reps know which fields block saves—no surprise at commit time
- Automation is off until manual discipline holds for two weeks
- Handoffs use the same field definitions across teams

## Common mistakes

- Buying another point solution before your CRM rules exist
- Optional fields for **the workflow gap named in your question**—reps skip them under quarter pressure
- Company-wide rollout before the pilot segment proves fill rate
- Inspection meetings that read narratives instead of opening your CRM records

## Manager inspection script (15 minutes)

Open the pilot saved report in your CRM. Sort by exception flag. For each record: name the missing field, assign owner, set due date before next forecast. No narrative readouts—only record fixes. Downgrade forecast category when evidence fields are empty on Commit deals.

## Rollout phases

| Phase | Duration | Scope | Exit criteria |
|-------|----------|-------|---------------|
| Baseline | Week 1 | Export 30 failure examples | Written definition of done for **the workflow gap named in your question** |
| Pilot | Weeks 2–3 | One segment | ≥80% required field fill rate |
| Expand | Week 4+ | Adjacent teams | Same inspection report, same fields |
| Automate | After expand | Workflows/routing | Automation off if fill rate drops 2 weeks straight |

## Data & integration notes

Document which objects sync from warehouse or billing before enabling automation. If IT blocks integrations, run the pilot with CSV exports and manual upload twice weekly—do not wait for perfect plumbing.

## RevOps without a big team

One owner can run this if they have **write access** to your CRM validation rules and a **manager who enforces** the inspection report. Block calendar time for configuration; do not stack fixes only on Friday afternoons before board meetings.

## Enablement & documentation

Publish a one-page **definition of done** for **the workflow gap named in your question** inside your sales wiki. Link the your CRM report URL, required fields, and two annotated screenshots. New hires should pass a 10-minute quiz on which fields block saves before receiving live opportunities in the pilot segment.

## Stakeholder alignment

| Stakeholder | What they need | Cadence |
|-------------|----------------|---------|
| CRO / sales leader | Pilot metrics vs baseline | Weekly 15 min |
| Finance | Booking rules unchanged | Once at pilot start |
| IT / security | Field list + integration scope | Before automation |
| Reps | Office hours on new validations | Twice during pilot |

## Discovery questions for your next inspection

Ask the pilot pod: Which deals failed **the workflow gap named in your question** rules two weeks in a row? Which field was empty on every loss? What would have blocked the save if validation were on? Capture answers in your CRM notes so the definition of done evolves with real failures—not generic enablement slides.

## Post-pilot scale checklist

- Required fields copied to adjacent teams unchanged
- Same saved report URL pinned in the Monday leadership agenda
- Automation tickets list the field API names, not vendor feature names
- Success metric frozen for one quarter before changing again

## Your CRM admin notes (copy/paste ready)

Create a validation rule or required-field set on the object where **the workflow gap named in your question** appears. Name the rule with the problem keyword so admins can find it later. Add a custom field **Exception_Reason__c** (or equivalent) for temporary waivers—managers must fill it or the record cannot reach Commit. Archive waivers monthly; patterns indicate bad rules, not bad reps.

## When leadership pushes back

If executives want a faster rollout, show the pilot fill-rate chart and the forecast error before/after. Offer parallel rollout only after two clean inspection weeks. Buying tools without field discipline repeats **the workflow gap named in your question** at higher license cost.

## Tie to forecasting

Map each required field to a forecast category rule: if economic buyer role is missing, the deal cannot sit in Best Case. Managers downgrade in the same meeting they inspect **the workflow gap named in your question**—do not allow verbal commits without your CRM evidence. Re-run the baseline export after 30 days to prove the fix held. Share results with finance and RevOps in the same slide.

<!--pillar-weave-->
## Related on PULSE

- [How do you track the decay rate of Marketing Qualified Leads by cohort week?](/knowledge/q9780)
- [How does AI in the funnel change your definition of a qualified lead in 2027?](/knowledge/q16456)
- [How do you compensate SDRs in a 2027 model where AI books 80% of qualified meetings?](/knowledge/q16296)
- [What question reveals whether a salesperson has properly qualified a lead before entering the pipeline?](/knowledge/q14410)
- [What is Qualified (Piper the AI SDR) and why is it a hot RevOps tool for 2027?](/knowledge/q12144)
- [Should I pay SDRs on demos booked or only on demos held + qualified?](/knowledge/q08)

## Why Cohort Week Decay Matters More Than Overall MQL Count

Tracking MQL decay by cohort week reveals the *velocity* of interest loss—a metric that aggregate MQL counts hide. When you only monitor total MQLs, you might see a steady pipeline and miss that leads from week 3 are converting at half the rate of week 1 leads. This decay pattern signals that your follow-up cadence or content relevance is weakening over time.

For most B2B organizations, the critical decay window appears between weeks 2 and 4. In my experience working with SaaS companies generating 50-500 MQLs per month, the typical decay curve shows 70-80% of leads still "active" (opening emails, visiting pricing pages) at week 1, dropping to 40-50% by week 4, and falling below 20% by week 8. These ranges vary significantly by industry—high-consideration purchases like enterprise software tend to show slower decay (60% active at week 4) while lower-commitment offers like free trials decay faster (30% active at week 4).

The real insight comes when you segment decay rates by lead source. A cohort from a webinar might show 55% activity at week 4, while a content download cohort drops to 35%—telling you to adjust nurture paths or re-evaluate the quality of that source. Without cohort-week tracking, you're making these decisions blind.

## Building a Practical Decay Tracking System in Your CRM

You don't need expensive analytics tools to track MQL decay by cohort week. A simple setup in most CRMs (HubSpot, Salesforce, or Zoho) works: create a custom date field called "Original MQL Date" on your contact or lead record. Then build a weekly report that groups leads by that date and measures engagement actions (email opens, site visits, demo requests) occurring within each subsequent week.

The key metric is "active MQLs per cohort week"—not just conversions. Define "active" as any meaningful engagement: at least one email open, a page visit beyond the homepage, or a form submission. Track this for 8-12 weeks per cohort. A practical approach: export cohort data weekly into a spreadsheet with columns for week 1 activity count, week 2 activity count, etc. Calculate the percentage of the original cohort still active each week.

For teams with 100+ MQLs monthly, consider a weighted decay score: assign points per action type (email open = 1, site visit = 2, demo request = 5) to measure engagement depth, not just presence. This prevents false positives from automated email opens and gives you a truer picture of interest decay.

## Interpreting Decay Patterns to Improve Lead Management

Once you have 4-8 weeks of cohort decay data, patterns emerge that directly inform process changes. A steep drop between weeks 1 and 2 (e.g., 80% to 40% active) suggests your initial follow-up is too slow or generic. Fix: implement same-day personalized outreach for new MQLs. A gradual but steady decline (e.g., 70% to 60% to 50%) indicates decent initial engagement but weak ongoing nurture—add a mid-funnel content sequence or re-engagement campaign at week 3.

Watch for the "dead zone" where activity falls below 20%—this is typically week 6-8 for most B2B cohorts. Leads in this zone are unlikely to convert without a major trigger (product update, new content, or direct outreach). Consider moving them to a long-term nurture track or removing them from active sales queues to focus resources on warmer leads.

A healthy decay curve shows 50%+ activity at week 4 for high-intent sources (demo requests, trial signups) and 30%+ for lower-intent sources (blog subscribers, gated content downloads). If your numbers fall below these ranges, audit your lead scoring criteria—you may be passing unqualified leads to sales too early, creating false decay that's actually disinterest from mismatched prospects.

## Sources

- HubSpot Blog — best practices for tracking MQL decay and cohort analysis in marketing.
- Google Analytics Help — documentation on cohort analysis and user engagement metrics.
- MarketingProfs — articles on lead scoring, MQL tracking, and cohort-based performance measurement.
- Kissmetrics Blog — guides on cohort analysis and customer lifecycle metrics.
- Harvard Business Review — research on lead management and marketing funnel decay rates.
- American Marketing Association (AMA) — resources on marketing metrics and cohort analysis methodologies.

## FAQ

**What is a Marketing Qualified Lead (MQL) decay rate?**  
It measures how quickly MQLs stop engaging or converting over time, typically tracked by the week they entered your funnel. A high decay rate means leads lose interest fast, signaling a need to adjust your nurture or targeting.

**How do I calculate MQL decay rate by cohort week?**  
Group MQLs by the week they were created, then track the percentage that remain active or convert each subsequent week. For example, if 100 MQLs from week 1 have 40 still engaged by week 3, that’s a 60% decay over two weeks.

**What tools can I use to track this decay?**  
Most CRM platforms like HubSpot, Salesforce, or Marketo allow cohort analysis with custom reports. You can also use spreadsheets to manually calculate decay if your CRM lacks direct cohort tracking.

**How often should I review MQL decay rates?**  
Weekly reviews are best for spotting trends early, especially during campaigns or product launches. Monthly checks work for stable periods, but decay can shift quickly with market changes.

**What causes high MQL decay rates?**  
Common reasons include poor lead quality from misaligned targeting, weak follow-up timing, or irrelevant content in nurture sequences. It often reflects a gap between marketing and sales expectations.

**Can I reduce MQL decay once it’s high?**  
Yes, by tightening lead qualification criteria, shortening response times, and personalizing outreach based on behavior. Testing one change at a time on a small segment helps avoid wasting resources.

## Bottom line

Fix **the workflow gap named in your question** on **your CRM** with **owner + enforced fields + weekly inspection**. Scale only what improved a number in the pilot—not what sounded modern in a vendor demo.

Was this helpful?

Sources cited

Pulse RevOps operational practicePulse RevOps operational practice

Deep dive · related in the library