Dynamics Community Forum Thread Details

Lead Scoring not working as expected

Hello,

We set up Lead and Opportunity scoring in all of our environments a couple of weeks ago. Scores are working as expected in our lower environments but not production.

The widget says "No Score Yet" like it does as soon as you turn on scoring, but like I said its been a couple of weeks. We have thousands of records and none have a score.

Is there a way to edit the configuration of the model? I only see a way to select different fields once its published. The model has performance stats and everything looks correct. Any ideas? Also confirmed all related processes are on.

Hello there!

there are a few things that could be causing this issue:

Ensure that you have properly configured the lead scoring model and that it's been activated. This includes setting the weightage of the attributes, selecting the records you want to score, and making sure that the scoring model is set to "Active".
Verify that you have set the scoring criteria for each attribute correctly. Make sure that the criteria you've set for each attribute are correct and that the attribute values being scored match the criteria.
Make sure that the scoring rules are running as expected. You can check the lead scoring log to confirm if the rules are running and if they're resulting in a score
Check if the leads are matching the defined criteria, if leads are not meeting the criteria, they will not get scored.
It's possible that the leads are not being scored because there is no data in the attributes used for scoring. Make sure that the attributes used for scoring have data in them for the leads you expect to be scored.
In case if you are using real-time scoring, check the real-time workflow's status, and make sure that it's set to "Active"
In case if you have recently migrated the leads or imported them, the leads might not have been scored. You'll need to manually run the scoring for these leads

It's possible that a combination of these issues is causing the problem, and it may require some troubleshooting to identify the specific issue and correct it.

Quick Links