Auditing which actions changed a contact's score

To explain a contact's score change, identify the exact score property and time under review, then compare its history with the scoring rules and underlying contact data. A movement does not necessarily mean the contact took a new action: older activity can lose points through score decay, a group limit can stop further points, and a rule edit can change the result.

Find the score history in HubSpot

Record the contact, score property, period and decision being investigated. A HubSpot combined score stores three values: Total score value, Fit score value and Engagement score value. A threshold property labels the contact from A (high fit) to C (low fit) and 1 (high engagement) to 3 (low engagement). Check which value moved, and use the value recorded at the decision time where available.

In HubSpot, users with Lead Scoring view permission and an eligible Marketing Hub subscription can open score history in two ways. Add the score property as a column on an index page view and click the score value, or open the contact record's Lead Score card and click See score history.

The right panel shows a Score trend graph by month and a Score history chart of the events that caused the score to change. Set the Last [x] days dropdown menu to cover the whole period under review before treating an entry as missing. The card's availability also depends on the record-view configuration.

Score Change Events in HubSpot

Match each movement to the action and rule

The actions that change an engagement score are the event rules in the score. HubSpot's own example scores email opens, email clicks, page views and ad interactions in a marketing group, and demo requests, sales form submissions and booked meetings in a sales group. Compare each history entry with the source event on the contact record and with the rule in force.

In that example, a click on a demo page or pricing ad earns 15 points, an email open earns two, and the marketing group is capped at 40 points. A contact who keeps opening emails can therefore stop gaining points once the cap is reached. If an event appears twice, determine whether two source actions occurred or one action produced duplicate records.

Rules can also limit repeats: a contact may submit a form worth one point five times, but a rule limited to two points counts only the first two. Score decay reduces points based on how long ago the scored event occurred; HubSpot's example applies 50% decay every three months. A falling score without new activity can reflect decay rather than a negative action.

To check the rule in force, open the score under Marketing > Lead Scoring and click Collapse all to see every rule at a high level. A rule edit can alter a score without new contact activity, so keep a dated record of each edit and compare it with the event time before describing a score increase as fresh interest.

Score Rules and Point Limits in Marketing vs Sales Groups

HubSpot Lead Scoring Key Metrics

State what the evidence supports

If the score crossed a threshold, inspect the downstream decision separately. In HubSpot's example, a workflow enrols contacts whose engagement score threshold property is within High (70–100) and routes them to sales once. A score history chart does not establish that this hand-off occurred or was later reversed. Record the observed movement, supported cause, remaining discrepancy and operational consequence.

Where the source event or applicable rule cannot be established, leave the cause unresolved and assign it for investigation. Keep personal details in the audit note to what the reviewer needs.

Auditing a Contact's Lead Score Change