Lead Scoring over time | Community
Skip to main content
E
euanblair
New Participant
October 18, 2022
Question

Lead Scoring over time

  • October 18, 2022
  • 2 replies
  • 2243 views

Hi there, I've been using Marketo for just under a year and started to explore updating our basic lead scoring model.

 

I'm struggling with adding a time-based restriction to flag leads that reach the score we set for an MQL - in this case, 20. 

 

What logic/settings do I use to only flag someone who has

 

1. Reached a score of 20 

AND

2. Has scored more than 8 points in the past 7 days

 

Is that doable? 

Thanks in advance!

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

David_Gallaghe2
David_Gallaghe2
New Participant
October 18, 2022

This may have been addressed in a previous post. There the commenters recommended the use of a separate weekly scoring field that would need to be changed with each score change... read more here:

https://nation.marketo.com/t5/product-discussions/score-is-changed-trigger/td-p/302330

 

 

That said, if you are only trying to see if a person who has reached 20 also has at least 8 points in the past week... you could use data change filters to get at that scenario and validate those two specific thresholds using constraints on both the DVC Trigger and DVC Filter new value + at least combined with the previous value + less than. Then on the filter tuck in a timeframe, and boom, there you go 😄

    E
    euanblairAuthor
    New Participant
    October 18, 2022

    Thanks David_Gallaghe2 and  Balkar_Singh,

     

    I'll give these a try to see what comes back.

     

    Shame you can't easily use a > for Greater than in Score Change instead of a fixed increase! 

     

     

    Balkar_Singh
    Balkar_Singh
    Community Manager
    October 18, 2022

    I think so, would suggest to test this though. This might only qualify people where score was changed by +8 at once though.

     

     

      Terms & ConditionsAccessibility statement

      Loading footer...