Skip to content

HubSpot recalculates a lead score about 0.5 to 8 minutes after the scored event, and up to about 8 minutes after the score is republished.

Measured

Checked

Checked October 16, 2026 on a HubSpot developer test account

Area

Tags

lead-scoring, lag, latency, recalculation

More facts from this area

A score criterion counting events on associated records uses {type: ASSOCIATION_UE, associatedObjectTypeId, associationSpec, inverseAssociationSpec, rollupType: SUM, associationFilters: {propertyFilters: [...]}, recordCalculation: {type: MULTI_UE, eventCalculators: [...]}}.Measured
PUT …/scores/{id}/draft replaces the whole draft and can only override outputs that already exist. A published score has no draft: GET …/scores/{id}/draft returns 404 DRAFT_NOT_FOUND.Measured
An event criterion built by API as MULTI of CONDITIONALs scores but the score editor shows "We couldn't load your criterion"; the editor-compatible form is one eventCalculators entry per criterion with recordCalculation: {type: MATCH, property, matchRules: [...]}.Measured
A lead score property rule must be a top-level MULTI of CONDITIONAL calculators whose whereCondition is a COMPOSITE AND of SINGLE conditions. A bare CONDITIONAL or MATCH at the top returns INVALID_TOP_LEVEL_CALCULATOR_TYPE.Measured
HubSpot appends a numeric suffix to a lead score's output property names (for example <name>_total_<number>), so the names must be read back after the score is created.Measured

Spriggit uses these facts when it plans changes. See something out of date? Email [email protected]