web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Customer Insights - Journeys forum
Suggested answer

Lead Scoring Model not working as intended

(0) ShareShare
ReportReport
Posted on by 84

Hi, 

I have set up two Lead Scoring Models: Behavioral and Demographic. However when I want to validate the Lead Scoring model, I encounter two issues.

1. Both models keep scoring leads that are closed even though I added a condition to only score leads with Lead Status = Open. Plus, I see a ton of duplicates scored with identical scores.

Lead_2D00_Scoring_2D00_Condition.PNG

I don't undersLead_2D00_Scoring_2D00_Behavioral_2D00_Model.png_2D00_640x480.png_2D00_640x480.pngtand anymore what I'm doing wrong. Should I submit a ticket? Has anyone seen a similar issue? 

Categories:
I have the same question (0)
  • Haig Liu Profile Picture
    Microsoft Employee on at
    RE: Lead Scoring Model not working as intended

    Hi Yulya Toporochan,

    I mean if the two conditions are unrelated as in image2, then it is not enough to restrict only the first condition, and the second condition will still apply to all leads.

    If nobody met the condition the lead score tab will show "No data available".

  • Yulya Toporochan Profile Picture
    84 on at
    RE: Lead Scoring Model not working as intended

    Hi, I understand that the conditions work with AND operators. However, I set up the model so it provides scores to only leads that have XYZ AND status "Open lead". When I look at the results and leads that are being scored, the majority has status "Disqualified". The system is ignoring the field I'm using. However, I rebuilt the model and published it again. Now, I don't see any data "No data available" in the lead scoring tab. Does it mean that nobody met the condition?

  • Suggested answer
    Haig Liu Profile Picture
    Microsoft Employee on at
    RE: Lead Scoring Model not working as intended

    1.All conditions belonging to the same parent are combined using an AND operator, which means that all sibling conditions must evaluate to TRUE for the attached action to be triggered:

    10.26.1.png

    But two conditions belonging to different parents use the or operator, which means that any condition that evaluates to TRUE can trigger an additional action:

    10.26.2.png

    2.Please check if there are many leads with the same name:

    10.26.3.png

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Community Spotlight of the Month

Kudos to Mohamed Amine Mahmoudi!

Blog subscriptions now enabled!

Follow your favorite blogs

TechTalk: How Dataverse and Microsoft Fabric powers ...

Explore the latest advancements in data export and integration within ...

Leaderboard > Customer Insights - Journeys

Featured topics

Product updates

Dynamics 365 release plans