Rule-based lead scoring assigns values to recorded attributes or actions to help prioritise review. Read the rules and evidence behind a score before treating it as a reason to act.
Read the ingredients before the total
HubSpot’s scoring documentation distinguishes fit scores based on record properties from engagement scores based on interactions. Its combined scores use both.
Keep those meanings visible when reviewing a result. A record’s business attributes and its website activity answer different questions. If a project requirement is missing, leave it marked unknown rather than treating the missing information as proof that the person is a poor prospect.
A fictional rule review
Consider a fictional photography studio’s record with repeated portfolio visits and an unknown project requirement. It appears high on the team’s review list. These are invented inputs, not an actual CRM result.
| Rule under review | Evidence needed | What remains unknown |
|---|---|---|
| Project type matches the chosen service. | Current project brief. | Buying authority. |
| Portfolio page viewed. | Recorded visit and date. | Reason for the visit. |
Read the configuration with the score
HubSpot permits frequency or time-frame filters on event rules and optional maximums for score groups.
Check whether repeat visits contribute again and which event dates qualify.
Save those settings with the rule version being reviewed. Before changing a contribution, establish what the rule is intended to represent. A repeat visit could deserve another look at the record, while the project requirement still needs its own evidence. Keep that unanswered question visible alongside the priority.
Separate a rule check from an outcome review
HubSpot’s test and preview features help check whether points are assigned properly.
That is a configuration check. Assessing whether a priority is useful requires a separate review of what happened next. Trace representative records through the rules before using their scores for routing, and record discrepancies between the expected contribution and the result.
Where outcome records are available, compare the priority assigned with later results, including enquiries that did and did not become customers. Retain who was included and what outcome was recorded. If records are incomplete, explain the gap rather than adjusting every rule to fit the few wins you can see.
Investigate an unexpected priority
Start with the contributions behind an unexpectedly high result. Check the recorded inputs against the rule and distinguish an event-recording problem from a deliberate weighting choice. If the score follows the configured rules but the priority is unhelpful, review the rule’s purpose and evidence before changing it.
Define what happens after prioritisation
Write down what your team does with the score. Selecting a record for review and accepting a lead for sales follow-up are different decisions. State who checks the missing information; a priority label should not silently stand in for that decision.
Pipeline explains the supported stage and next action in an opportunity record. Use Conversion Funnel for ordered event counts and their denominators.
Sources
HubSpot supplies the product-specific scoring examples. The studio record and review instructions are editorial illustrations, not tested settings or evidence of improved sales.