Automation Builds
Part of Lead scoring implementation
Translating an agreed scoring model into platform rules
Map approved scoring signals to exact properties, events, filters and limits, then check that platform logic preserves the model.
Translate an agreed scoring model one rule at a time. For each approved signal, identify its exact record, property or event, filter, point value and limit. Before enabling the score, record any difference the platform cannot resolve.
Make the mapping explicit
Agreed item / Configuration to confirm
- Scored entity
- Object and any association used
- Fit signal
- Property, operator, accepted values and blank treatment
- Behavioural signal
- Event, source, filter and timeframe
- Point effect
- Add or subtract, amount and applicable limit
- Repeat treatment
- Each occurrence, frequency band or capped contribution
- Output
- Score property, component value, grade or threshold label
For example, an agreed signal called “recent demo interest” needs a defined action and period. A submission of a named request form and a visit to any page containing “demo” are different signals. Whoever owns the model must decide which meaning was approved.
Check how rules combine
A model requiring serviceable region and target company size must represent both conditions as required. Otherwise its meaning changes.
HubSpot scores are based on criteria set for event and property rules in score groups. Multiple groups can add up to the total score.
Check a record meeting only one condition. If the approved combination cannot be expressed directly in the score rules, record the limitation and ask the scoring model's owner to decide.
For event rules, verify the selected event action matches the approved signal. Check that the configured points match the model.
Do not assume other controls alter how events accumulate unless verified in the platform documentation.
Customer Insights – Journeys scores leads using demographic attributes and interactions. Do not assume a custom event is available as a scoring interaction unless verified. Fields protected by field-level security cannot be used in its scoring conditions.
Key Platform Constraints in Lead Scoring
- HubSpot Score Groups
- Multiple groups can sum to total score
- Customer Insights – Journeys
- Uses demographics and interactions; custom events not guaranteed
- Field-Level Security
- Protected fields cannot be used in scoring conditions
Check associations and outputs
If an approved signal comes from a related record, verify the platform rule can reference the intended data. Confirm the scored record matches the model. Record any unresolved association difference and refer it to the model owner to settle.
Compare each configured rule with its approved mapping. Use cases that isolate a single property, a single event, both conditions, a blank, an old event and an excluded associated record. Record the score-property name, model version and any approved exception. If a rule cannot be reproduced, return the difference to the model owner so they can decide.
