Lead scoring fields and setting a cap on score

[stephdemandgen]

I'm looking to update some lead scoring in an instance I recently inherited (no in house mops team).  Two questions to the brain trust here:

1. It appears that in every behavior score flow, there's a step to add to demographic score AND one to add to person score (same number of points). I thought that Person Score = Behaviour Score + Demographic Score was automatically calculated so I'm wondering why it would be set up like that?

2. What are best practices around capping lead score? Seems like a good idea for degradation to function properly, but would appreciate some advice on what to do/what to consider. 

[SanfordWhiteman · Accepted solution]

---

1. It appears that in every behavior score flow, there's a step to add to demographic score AND one to add to person score (same number of points). I thought that Person Score = Behaviour Score + Demographic Score was automatically calculated so I'm wondering why it would be set up like that?

---

No, it’s not automatically calculated. You select the components of/contributors to the Person Score.

---

2. What are best practices around capping lead score?

---

Simply put: check the score (using Add Choice or comparable filter) before incrementing it.

[Ruchi_Lapran1]

It depends on the frequency at which you are scoring. Some people score behavior and demographic at "every time" cadence which may inflate the total lead score. Keeping a cap is a good idea where the scoring threshold is low but the frequency of scoring is high.

One point worth considering is when you are capping your lead score, make sure you plan to cap the behavior and demographic scores in parallel otherwise, you may find behavior scores going higher than the total lead score.