HubSpot lead scoring points decay is usually raised as a missing feature: scores go up when a lead engages, and teams assume nothing ever brings the number back down once that lead goes quiet. Checking HubSpot’s own documentation directly shows that assumption is only half right. The current Lead Scoring tool has a native decay toggle, with a documented percentage-per-period mechanic, but it only reduces engagement and combined scores, never fit scores, and it does not touch segment membership criteria at all. The teams who still need to build decay by hand are usually running an older setup, or working without the plan the native tool requires, and that hand-built route runs into a second, less obvious gap: HubSpot’s own workflow documentation stops short of describing what happens when two separate workflows write to the same score property.
HubSpot Lead Scoring Points Decay: Does Native Decay Exist?
Yes, for the current version of the tool. Per HubSpot’s own documentation on building lead scores: “To set up score decay, which automatically reduces a score based on how long ago a scored event occurred, toggle the Decay scores switch on. Select the percentage to reduce the score by, and the period of time that must pass to reduce the score.” That is a native, built-in control sitting directly inside the scoring rule editor, not a workaround, and it is available to any account on “Marketing Hub Professional, Enterprise” or “Sales Hub Professional, Enterprise”, per the plan availability HubSpot’s own documentation states at the top of that same page.
The confusion many teams run into comes from an older mechanism that this keyword still gets associated with: custom score properties, and the legacy default “HubSpot score” contact property they used to power. Checked live this session, three separate legacy documentation URLs that once explained how to create and edit a custom score property all now redirect straight into the current tool’s own page: the old properties path, the old crm-setup path, and the old contacts path each resolve to the same destination as the page quoted above. No separate, currently live HubSpot documentation page describing a standalone decay feature for a custom score property was found. Per HubSpot’s own documentation on default contact properties, the legacy field itself confirms the same consolidation: “HubSpot score: the number that shows qualification of contacts to sales readiness based on the criteria set in HubSpot’s lead scoring tool. This is automatically set by HubSpot.” The old property name still exists, but the scoring logic and the decay behind it now belong to the tool described in this article, not to a separate, older system.
How Score Decay Actually Reduces Points
Per HubSpot’s own documentation on the lead scoring tool, decay is set per rule, not once for the whole score: “For engagement or combined score event groups, you can turn on score decay, which automatically reduces an individual event’s score based on how long ago a scored event occurred. Score decay intervals can be set to every 1, 3, 6, or 12 months, with each month equal to 30 days. Score decay is independent to each event, follows linear logic, and decayed scores aggregate to the overall score value.”
The same page works through the arithmetic directly: “For example, a rule gives 10 points when a specific form is filled out. If this event’s decay is set to 50% every month, then one month after the form was filled out, the 10 points from that event will be cut in half and the event now contributes 5 points to the score. The decay is based on the original event score value (i.e. 10 points). In this example, 30 days later, the form submission contributes 0 points to the score.” That last line is worth reading twice: the reduction is measured against the original 10 points each period, not against whatever points happen to remain, which is what HubSpot’s own documentation means by decay following “linear logic” rather than a compounding percentage.
Decay is not limited to reshaping new activity either. HubSpot’s own documentation states plainly: “Score decay also applies to historical data. For example, if a rule adds 2 points for a CTA click with 100% decay in 3 months, if the CTA click happened 4 months ago, the contact won’t get 2 points.” Turning decay on for a rule retroactively re-evaluates events that already happened, which matters for a team switching decay on for the first time against a score property that has been quietly climbing for months.
What Decays and What Doesn’t
The decay toggle is not a whole-score setting, and HubSpot’s own documentation is specific about where it does and does not apply. The distinction runs along the same line the tool already draws between how a lead score gets built in the first place: engagement criteria are timestamped events, fit criteria are static property values, and only the timestamped side has anything for a percentage-per-period reduction to act on.
| Score element | Does decay apply | What HubSpot’s own documentation states |
|---|---|---|
| Engagement score group | Yes | “For engagement or combined score event groups, you can turn on score decay” |
| Combined score group | Yes, on the engagement rules within it | Combined scores qualify records “based on engagement criteria and fit criteria”; decay is documented for the engagement side of that pairing |
| Fit only score group | Not documented | Fit scores qualify records “based on their demographic information through property values, such as their age, job title, company size, or annual revenue”, with no decay toggle described for this group type |
| Segment membership criteria | No, explicitly | “Score decay is not supported for segment membership criteria. This is because segment membership is based on a binary condition (is or is not a member), while decay is based on a timestamp.” |
The segment exclusion comes with a documented workaround rather than a dead end. HubSpot’s own documentation continues: “To implement decay for segment memberships, include date/time-based filters in your segment criteria (e.g., include contacts in a segment if they submitted a form within the past 30 days).” That is a different mechanism doing a similar job, a rolling date filter rather than a percentage reduction, and it needs to be built and maintained separately from any decay a related score property already has switched on.
Building Decay Yourself: Legacy Scores and the Same Property Risk
Native decay is gated to specific plans and specific tools. A team on a plan below Marketing Hub or Sales Hub Professional, or one still scoring leads on a plain number property that predates the current tool, does not get the Decay scores toggle at all, and is left building the same outcome with a scheduled, re-enrollable workflow: check a last-activity date property, and if enough time has passed, subtract points.
That approach has to coexist with whatever workflow is already adding points for positive activity, and this is where HubSpot’s own documentation gets thinner. HubSpot’s own documentation on re-enrollment triggers states a clear rule, but it is scoped to a single workflow re-triggering itself: “A record won’t re-enroll in a workflow while it’s already enrolled. Re-enrollment can only happen after the record is manually unenrolled from or has exited the workflow.” That protects a decay workflow from looping on its own property change, since a re-enrollment trigger set to the score property will not fire the same workflow again mid-run.
It says nothing about a second, separate workflow. Checked directly on HubSpot’s own workflows FAQ, no statement describes what happens when two different workflows, one adding points on engagement, one subtracting points on a schedule, both write to the same score property around the same time. The FAQ does document a related but different risk, timing rather than ordering: “When a large number of records enroll in a workflow or execute an action at the same time, the workflow may be throttled. When a workflow is throttled, actions will not execute immediately, but in a queue as records are processed. Heavy simultaneous processing can cause actions or property changes to take time to process.” That confirms actions can be delayed under load. It does not confirm which of two workflows’ writes lands last on a record both are touching at once, and HubSpot’s own documentation does not state that anywhere this session’s checks reached.
Where Teams Get This Wrong
The first common mistake is treating decay as a feature HubSpot lead scoring simply does not have, based on older articles, forum threads, or a previous setup that predates the current Lead Scoring tool. HubSpot’s own documentation confirms a native decay toggle exists today, gated to Marketing Hub or Sales Hub Professional and Enterprise, and checking the current tool before building a workaround saves the workaround entirely.
The second common mistake is assuming decay quietly applies everywhere a score exists. HubSpot’s own documentation scopes decay to engagement and combined score groups only, states plainly that segment membership criteria do not support it, and offers no documented decay toggle for fit only groups, since fit is built from static property values rather than timestamped events.
The third common mistake is assuming decay compounds against whatever points a rule currently contributes, rather than against the rule’s original value. HubSpot’s own worked example states the reduction is “based on the original event score value”, following linear logic rather than a shrinking percentage of a shrinking number, which changes how quickly a given rule actually reaches zero.
The fourth common mistake is running a hand-built decay workflow against the same score property as a positive-scoring workflow without checking what HubSpot’s documentation does and does not promise. The documented protection only covers a workflow re-enrolling into itself. Nothing in HubSpot’s own workflow documentation states how two separate workflows are ordered when both write to the same property, so that ordering has to be tested and controlled deliberately, not assumed safe by default.
Related Reading
For the CRM foundation a scoring system runs on top of, see HubSpot Consultancy. For the workflow layer a hand-built decay rule depends on, see HubSpot Workflow Version Control and Rollback Guide. For the wider discipline scoring sits inside, see RevOps Consultancy.
Go deeper: AI Bias in SaaS Lead Scoring · Automate HubSpot Lead Scoring with n8n and Clearbit · n8n Consultancy
Frequently Asked Questions
Does HubSpot lead scoring points decay actually exist as a native feature?
Yes, in the current Lead Scoring tool. HubSpot’s own documentation describes a Decay scores toggle on each rule, letting a team choose a percentage reduction and a period of 1, 3, 6, or 12 months. It is available on Marketing Hub or Sales Hub Professional and Enterprise plans, and does not exist as a separate feature on the older custom score property mechanism.
Does score decay apply to fit scores as well as engagement scores?
No. HubSpot’s own documentation states decay applies to engagement or combined score event groups, and fit scores are built from static property values such as job title, company size, or industry rather than timestamped events. No decay toggle is documented for a fit only score group, since there is no elapsed time for a percentage reduction to act against.
Can a segment’s membership criteria decay over time in HubSpot?
Not through the scoring decay toggle. HubSpot’s own documentation states score decay is not supported for segment membership criteria, since membership is a binary in or out condition rather than a timestamp. The documented workaround is a date or time based filter inside the segment’s own criteria, built and maintained separately from any score decay.
Do the older custom score properties in HubSpot still support decay?
No standalone decay feature for them was found in HubSpot’s current documentation. The URLs that used to explain custom score properties now redirect to the current Lead Scoring tool’s page, and the legacy HubSpot score contact property is documented as being set by that same tool, not by a separate mechanism with its own decay rules.
Is it safe to run two workflows that both change the same HubSpot score property?
HubSpot’s own documentation only confirms that a single workflow cannot re-enroll into itself while already enrolled. It does not state how two separate workflows, such as a positive scoring workflow and a hand-built decay workflow, are ordered when both write to the same property at a similar time, so that behaviour needs testing rather than assuming it is documented and safe.