Score decay with "last updated" filter | Community
Skip to main content
Level 2
July 17, 2023
Solved

Score decay with "last updated" filter

  • July 17, 2023
  • 1 reply
  • 2449 views

Hello Everybody,

 

I'm in the process of setting up a scoring model. And I am trying to set up the score decay.

 

What I want to do is to subtract X points if the record has not been updated in the past Y weeks.

 

For that I am using an "Updated At" field but I am unsure what operator to use as some of the options are not too descriptive (to me at least). See below:

 

Any suggestions on which option can do this for me?

 

Thanks in advance!

Zoltán

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 Darshil_Shah1

Well, that's not a filter, you're using the field "Updated At" as a flow step condition. You set the condition as: if the person is "Updated At in past Y weeks" Do Nothing, and in the Default Choice, update their Behavior Score by subtracting as many points as you like.

 

Also, instead of using the "Updated At" field for scoring, I'd rather advise using meaningful person interactions to score (positively/negatively) people. E.g., for score decay, you could consider: if a person hasn't submitted a form in the past X weeks, hasn't visited your website in the past X weeks, or has Unsubscribed/Opted-Out, etc.

 

The "Updated At" field would get updated for any updates on the person record, and these updates need not be person interactions. They could very well be operational updates (e.g., add to a list, system field updates, etc.). Even Opt-out, Unsubscribed are also counted as updates. So the campaign you're trying to build, a person who recently Unsubscribed, or a person who was added to an operational list (not due to any of their interactions/actions) won't flow through the flow, and hence, their score won't be decayed, even though it makes sense to decay their score.

 

1 reply

Darshil_Shah1
Community Advisor and Adobe Champion
Darshil_Shah1Community Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
July 17, 2023

Well, that's not a filter, you're using the field "Updated At" as a flow step condition. You set the condition as: if the person is "Updated At in past Y weeks" Do Nothing, and in the Default Choice, update their Behavior Score by subtracting as many points as you like.

 

Also, instead of using the "Updated At" field for scoring, I'd rather advise using meaningful person interactions to score (positively/negatively) people. E.g., for score decay, you could consider: if a person hasn't submitted a form in the past X weeks, hasn't visited your website in the past X weeks, or has Unsubscribed/Opted-Out, etc.

 

The "Updated At" field would get updated for any updates on the person record, and these updates need not be person interactions. They could very well be operational updates (e.g., add to a list, system field updates, etc.). Even Opt-out, Unsubscribed are also counted as updates. So the campaign you're trying to build, a person who recently Unsubscribed, or a person who was added to an operational list (not due to any of their interactions/actions) won't flow through the flow, and hence, their score won't be decayed, even though it makes sense to decay their score.

 

ZoltanAuthor
Level 2
July 17, 2023

Hi Darshil,

 

Having the minus score for the default is the way to go actually, thanks!

 

And thanks for the tip, that makes more sense indeed!

I think I will try out that approach, see if I can cover everything I need, and get back to this thread.

 

Will keep this topic open.

ZoltanAuthor
Level 2
July 17, 2023

I looked at the approach to cover all main client activities for score decay and came up with the below setup.

It is by no means perfect - i'm still quite new to Marketo - but I think it would more or less do what I intend:

 

Does this makes sense?

 

Thanks!