Hi guys,
how do I set up a smart campaign to trigger on a lead score change when someone goes above increments of +100?
so someone with 95 doesn't trigger anything, but as soon as they score +5 or +10 or anything greater that would trigger the Smart campaign. and the same again when they hit 200...etc
At the moment I have 'change is +100' - but I think that is only triggering when someone scores 100 in a single action - which isn't what I really want at all...
Hello Michael,
You could trigger off a Data Value Change, Attribute = [Score of your choice], New Value - greater than - 100
Ok thanks Roxann - but that only works for the first instance...i.e. greater than 100. it wouldn't work for greater than 200, for example.
I'm struggling with how other people trigger the leads into their CRM. i can see ho wto build up a lead score and there's a lot of information out there about that. But what triggers are people using to push the lead into the CRM for Sales? I was working on the ethos of a lead scoring +10, +15, +100 etc, building up the score over time and when it hits increments of 100 then it is pushed to Sales - so the same lead coild be pushed more than once - as their score builds over time from 100, to 200, to 300 - as they interact with emails, download, attend webinars etc - but I can't figure out how to trigger the lead to go to Salesforce each time it hits that 100 point threshold...
New Score between 101 and 200, run through once, individual SCs for each 100-block. Or one SC with triggers for each 100-block, Add Choice for list membership/progression status/etc. to skip increments that don't bump them up to the next block.
ok - but I have leads with scores of 500, 800, 1000 etc - there is no real limit yet as to how high a score could go. so the above would have to be multiple trigger elements with the ranges built it. it's a solution that would work, I'm just curious as to whether my approach is wrong, and whether there is a better methodology that the tool actually supports easily...
I'm not aware of any built-in support for numeric milestones like you describe (as opposed to defining the milestones yourself in SCs) but maybe someone has a more elegant idea.