How Does HubSpot Measure Recency and Frequency in Scoring?
HubSpot measures recency by evaluating actions inside defined time windows (for example, “visited pricing page in the last 14 days”), and measures frequency by scoring how often a meaningful action repeats within a window (for example, “3+ high-intent visits in 7 days”). Paired with timeframe rules and decay, scoring stays anchored to what matters most: current intent, not historical noise. :contentReference[oaicite:2]{index=2}
If scoring does not account for time, it over-prioritizes stale engagement and inflates “hot lead” volume. Recency and frequency solve that by turning scoring into a time-sensitive signal system: recent actions matter more, repeated high-intent actions matter even more, and old activity fades so Sales effort follows real buying momentum. HubSpot supports this approach through lead scoring criteria and configuration options designed to evaluate records based on properties and actions and then surface those scores for segmentation, workflows, and reporting. :contentReference[oaicite:3]{index=3}
What “Recency” and “Frequency” Actually Control
A Practical HubSpot Playbook for Recency + Frequency Scoring
Use this sequence to turn scoring into a reliable “signal clock” that reflects real buying motion and prevents stale engagement from skewing prioritization.
Define → Window → Frequency → Decay → Cap → Route → Validate
- Define “high-intent” actions: Identify behaviors that correlate to buying motion (pricing visits, demo requests, comparison pages, solution depth, key conversions).
- Set the recency window per signal type: Use shorter windows for fast signals (7–14 days) and longer windows for slower signals (30–90 days), based on sales cycle reality. :contentReference[oaicite:10]{index=10}
- Apply frequency ranges where repetition matters: Score repeated behaviors (e.g., “3+ high-intent actions in 7 days”) to capture momentum without rewarding one-off curiosity. :contentReference[oaicite:11]{index=11}
- Configure decay to match your cycle: Reduce scores when activity stops so “hot” cools naturally and routing does not get stuck on old interest. :contentReference[oaicite:12]{index=12}
- Set caps and group limits: Prevent one channel or one behavior from dominating the score (for example, cap page views so conversion actions still matter). :contentReference[oaicite:13]{index=13}
- Route using thresholds plus context: Trigger actions only when score thresholds align with minimum eligibility (good fit, valid association, non-suppressed cohort).
- Validate with a score-to-outcome scorecard: Compare meeting rate and stage progression by score band. Retire noisy rules and refine windows until higher bands consistently outperform. :contentReference[oaicite:14]{index=14}
Recency + Frequency Scoring Maturity Matrix
| Dimension | Stage 1 — Static Scoring | Stage 2 — Time-Windowed | Stage 3 — Time-Sensitive & Governed |
|---|---|---|---|
| Recency | Lifetime points accumulate; “hot” never cools. | Some actions scored only in the last X days. | Windows set per signal type and tuned to cycle time. |
| Frequency | One action counts the same as many. | Some repetition considered informally. | Frequency ranges reflect momentum (e.g., 2–5+ events in a window). |
| Decay | No decay; stale engagement dominates. | Manual resets or periodic cleanups. | Automated decay aligns scoring to active demand. :contentReference[oaicite:15]{index=15} |
| Caps | One channel can inflate scoring. | Basic limits exist. | Group limits protect score diversity and integrity. |
| Outcomes | Success measured by volume (MQL count). | Some meeting reporting exists. | Score bands tuned to meetings and progression outcomes. :contentReference[oaicite:16]{index=16} |
Frequently Asked Questions
What does “recency” mean in lead scoring?
Recency means actions count only if they happened within a defined time window (for example, “visited a key page less than 30 days ago”), keeping scores aligned to current intent. :contentReference[oaicite:17]{index=17}
What does “frequency” mean in lead scoring?
Frequency measures how often an action repeats within a window (for example, multiple high-intent visits in one week) to identify momentum and reduce one-off noise. :contentReference[oaicite:18]{index=18}
How do you choose the right time windows?
Base windows on observed cycle time: faster motions use shorter windows (7–14 days), slower motions use longer windows (30–90 days), then tune based on meeting and stage progression outcomes. :contentReference[oaicite:19]{index=19}
How do you prevent scoring from being “gamed” by repeated activity?
Use caps and frequency ranges so repeat actions contribute predictably rather than endlessly. Pair with suppression for internal traffic and low-quality cohorts so the model stays stable at scale.
Turn Scoring into a Time-Sensitive Signal Engine
Apply recency windows, frequency ranges, and decay so HubSpot scoring reflects real momentum, routes the right leads, and keeps pipeline reporting trustworthy.