When setting up demo scoring, when do you use Data Value Changes and Lead is Created? | Community
Skip to main content
A
Anonymous
March 13, 2015
Solved

When setting up demo scoring, when do you use Data Value Changes and Lead is Created?

  • March 13, 2015
  • 2 replies
  • 1095 views
I'm noticing that some demo score campaigns have this at the top of the smart list, and some don't.

Data Value Changes
Lead is Created

Can you explain when to use this and when not to? I'd assume that you'd use it for all since you only need demo score to be scored when the lead is created or when the data value changes. But it's not on some of my demo score campaigns, nor the Marketo program library import example.

Don't have: 



Have:

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Josh_Hill13
Hi Christine,

There are different ways to handle this.

Option 1: Batch System where we assume the title does not change. 
This is the most likely scenario, however, we risk missing people who update titles through promotion or being more honest with us. Your first screenshot is this. We run this job daily and if the lead matches our ideal criteria, it gets scored.

Option 2: Triggered when the lead is created OR when the lead updates the title.
The issue here is that while we catch the person's title (if it matches our filters), we can end up double scoring someone. Let's say they match on Manager and get +5. Then they change their title and get Director for +10. Now they have +15!

Option 3: Demographic Rescoring System
I don't see this often enough. It is a little tricky to setup:
  • Demographic Change Trigger - any time someone modifies key values OR is created, then we 
  • Clear the Demo Score and lower the Lead Score={{lead.behavior score}}
  • Request other Campaigns for the fields we care about:
  • Job Title - if a match, it updates Demo score appropriate
  • Industry -if a match, it updates Demo score appropriate
  • etc
this way we can rebuild the score each time someone updates their info. Works pretty well.

2 replies

Josh_Hill13
Josh_Hill13Accepted solution
Level 10
March 14, 2015
Hi Christine,

There are different ways to handle this.

Option 1: Batch System where we assume the title does not change. 
This is the most likely scenario, however, we risk missing people who update titles through promotion or being more honest with us. Your first screenshot is this. We run this job daily and if the lead matches our ideal criteria, it gets scored.

Option 2: Triggered when the lead is created OR when the lead updates the title.
The issue here is that while we catch the person's title (if it matches our filters), we can end up double scoring someone. Let's say they match on Manager and get +5. Then they change their title and get Director for +10. Now they have +15!

Option 3: Demographic Rescoring System
I don't see this often enough. It is a little tricky to setup:
  • Demographic Change Trigger - any time someone modifies key values OR is created, then we 
  • Clear the Demo Score and lower the Lead Score={{lead.behavior score}}
  • Request other Campaigns for the fields we care about:
  • Job Title - if a match, it updates Demo score appropriate
  • Industry -if a match, it updates Demo score appropriate
  • etc
this way we can rebuild the score each time someone updates their info. Works pretty well.
A
Anonymous
March 16, 2015
Josh, thanks for this clear explanation. Option 2 - I was wondering about the double-scoring! I suppose Option 1 is not a huge deal - as you said , this is the most common scenario.

I'll revisit Option 3 again when I've got more lead scoring exp under my belt. Makes sense tho!
Terms & ConditionsAccessibility statement

Loading footer...