I am trying to create a Smart Campaign that triggers an email send if a field value increases.
I see that there are constraints that I can add that are based off of the new value and previous value but it looks like I can only compare those with a static number. I don't care what the value is or how much it has gone up, I only care that it has increased.
Has anyone found a way to make this work?
Hello Liz,
Could you provide an example? If it's a very manageable value increase like "2" to "6" then you can create separate smart campaigns that would trigger "new value is 6" and "previous value is not 7, 8, 9, or 10". So in this example, you know that it was an increase since the previous value was less than 6.
Then you would create another smart campaign for "new value is 7" and "previous value is not 8, 9, or 10" and so on.
What we're trying to do is similar to a bank account but we're only dealing in whole numbers. The numbers can range from 0 to thousands so using multiple campaigns isn't really an option.
Using the bank example, we want to send an email out whenever a deposit is made. A withdrawal would change the value but we don't want an email to be sent out.
Okay, so multiple smart campaigns won't work in this case. I know this is not the conventional way, but maybe you could create custom lead scoring for the bank deposit numbers? However, even the "score is changed" trigger doesn't include the constraint of just an increase or decrease. Perhaps an idea should be created.
Yes, the Data Value Changes will allow you to compare the New vs. Old values with standard operators.
But there is not an ability to say any Increase is ok.
But if you had fields watching Last Balance vs. Current Balance and it populates Increased Balance field, then you could do something like
if Increased Balance is Greater than 0, then do something.
But you would need to have SFDC or the other system doing the math...maybe you could get a Marketo Formula field to work here too. Try it.
Hi Josh,
I do not think Marketo formula fields can do some math, unfortunately.
-Greg
You can make it a score and vote here, since there is not simple solution here.
Yet, there is a solution that will require assistance from Marketo:
Tested, it works.
-Greg
Thanks for all of the suggestions. I voted on all of the linked ideas, I think they will be really helpful in the future.
I ended up finding an object that we had created in Salesforce that stamps whether the transaction was a deposit or withdrawl and used that as a filter with the data value change trigger.