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
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}/draftreplaces the whole draft and can only override outputs that already exist. A published score has no draft:GET …/scores/{id}/draftreturns 404DRAFT_NOT_FOUND.Measured- An event criterion built by API as
MULTIofCONDITIONALs scores but the score editor shows "We couldn't load your criterion"; the editor-compatible form is oneeventCalculatorsentry per criterion withrecordCalculation: {type: MATCH, property, matchRules: [...]}.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 - Both lead scoring versions exist:
/marketing/lead-scoring/2026-09-beta/scoresand.../2027-03-beta/scoresare routed (an unknown version is 404), and both refuse a public app with 403 "isn't available for public use". Which one a portal with the beta opt-in answers on is unmeasured; Spriggit uses 2027-03-beta.Corrected
Spriggit uses these facts when it plans changes. See something out of date? Email [email protected]