Before touching weights, write down what your best-closing customers look like (e.g. revenue band, company size, industry, urgency) and reverse engineer scores.

Your scored questions and their points should mirror that profile, so a high lead score literally means "looks like our best customers."

Lead Scoring is the feature; the number is a lead score.

Only add points to questions that genuinely separate good leads from bad.

Budget or revenue usually predicts a deal far better than a nice-to-know field, so those deserve the most influence.

If a question doesn't change how likely you are to close, leave it unscored. Extra scored questions just dilute the ones that matter.

Within each question, give the best answers the most points (up to 100) and weak-fit options 0.

A better answer should always be worth more, that ranking is what makes the score meaningful.

Points say how good a lead's answer is; weight says how much that question matters relative to the others.

Don't guess from the weights. Watch the Influence column, which shows each question's true share and always totals 100%.

Adjust until the split matches your ICP (e.g. revenue carrying the most influence).

A score only pays off when something acts on it. Route your highest scorers to your best closers, and use disqualification to keep low-fit leads off the calendar entirely.

Build tiers by stacking conditions so priority engagement is automatic:

Don't hard-code bands on day one. Turn scoring on, watch how real leads score for a week, and see where your actual closers fall before you set "disqualify under X" or "route over Y."

Lead scoring is iterative. Make sure to revisit your points, weights, and thresholds as you learn which scores actually convert.

Turn scoring on for a single event, confirm the scores and bands behave as expected using the preview, then expand once you trust the model.

Form questions capture explicit fit; a HubSpot score can add behavioral or engagement context (e.g. an activity or engagement score).

Blending explicit fit with a behavioral signal is exactly what strong lead-scoring models do. It catches leads who look right and are actually engaged.

Set the HubSpot Max value to the field's real ceiling so the signal scales correctly.

No. Scores are visible only to you inside the event. Leads filling out the form never see any points.

Answer points say how good a lead's answer is. A better answer option is worth more points (e.g. "$50k+ revenue" scores higher than "$0–10k").

Weight says how much that whole question matters compared to your other questions, regardless of which answer the lead picks. Points vary per lead; weight is the same for every lead.

You don't set it directly. Because questions are single-select, Max points shows the highest points value among that question's answer option, the most the question can contribute. It updates automatically as you edit option points.

No. Points don't need to sum to any particular total, and options can be left at 0.

Each individual option can be worth 0 to 100 points. Assign them however your qualification criteria see fit.

The system normalizes everything to a 0–100 score at the end.

Because influence is driven by max points × weight, not weight alone.

Two questions both at weight 100 will differ in influence if their max points differ (e.g. one topping out at 60 points, another at 55).

The Influence column always shows the true share, and totals 100% across your scored items.

Single-select questions that have point values on their options and are enabled in the Lead Scoring panel.

Unscored questions are ignored, not counted as zero.

That question is removed from the calculation on both sides, so the score is based only on what they did answer.

Skipping a question doesn't push the score down to zero.

Most likely someone edited the point values on a shared question's options.

Option points are shared across every event that uses that question. The per-event lever is weight, not points.

Balance the Influence column: for example, set your four questions to weight 25 each and HubSpot to 100, and HubSpot's influence reaches ~50%.

The weight range goes up to 1000 so you can raise one component instead of lowering the rest.

The HubSpot component is simply removed from the calculation and the score is based on the remaining questions.

The lead is never blocked or held up by a missing or slow HubSpot lookup.

Check that your Max value reflects the field's real ceiling:

Note that a HubSpot value of 0 currently counts as a genuine zero (a real low score).

If many new leads sit at 0 because they're unscored in HubSpot, weight HubSpot down relative to your questions, or leave it out until those contacts carry a meaningful value.

Not with the current version - its on our to do list. Currently you can add one external score field per event.

If an active Conditional Routing or Disqualification condition uses Lead Score, you'll be prevented, from turning scoring off until those conditions are removed, so no rule is left silently broken.