Use a "score was changed" filter with a "not score was changed" one:
Set the lead so that they cannot enter it more than once or more than once a day.
Run is every hour. I used a 24-26 hours interval to make sure that you do not miss any lead even if the campaign starts a few minutes late.
Thanks Greg. This makes sense and i think that would work.
I was intrigued that I could define a trigger like this, but from a technical / backend perspective it doesn't make a lot of sense to be able to trigger on events in the past:
Does this just not work in general?
I'm an engineer and I've been reviewing our campaigns set up by marketing in the past few days. I saw that we use smart campaigns in the way I've described to send a small number of drip emails.
Are we missing out by not using engagement programs? It feels like the programs offer some flexibility of cadence, pausing, and periodic scheduling at a given time, however it seems like most of this is possible with a smart campaign - maybe with a little more work. On the flip side, it seems like a potential downside of engagement programs is the fixed schedule. If I trigger a smart campaign from an event the user did, I can email them again around the time of their activity - a time that individual might like to shop at. I don't think you can do this in an engagement program.
Does that understanding seem right?
Thanks for your help!
1 of 1 people found this helpful
In fact, by design, a trigger cannot be in the past, it has to fire immediately, or it is no longer a trigger
With regards to EP's vs regular campaigns this is a completely different topic, and you should probably open it in a different post to maximize the answers you will get.
Basically, you get it right. another advantage of EP streams, is that it is very easy to add/remove content without to have to take a risk with wait steps and doing tricky things to control whether or not a lead has already received a content.
Can you actually run this every hour? When trying to set this up, I saw you could only schedule daily at most.
We could make 24 separate campaigns, but then exclusion wouldn't work (and that would suck).
Why can't you just use a daily batch or hourly as Greg suggests?
Score Was Changed: Lead Score Change=+1 in Past 24 hours
btw, Data Value Changes is a better trigger, even for Lead Score in most cases.
Greg's suggestion was good. I think trying to trigger on stuff in the past just doesn't work and really shouldn't be an option. The thought of "triggering" based on past things doesn't make much architectural sense anyways.
Curious why is data value changes a better trigger? For us, the limitation is that we automatically decrease the lead score that I'm watching to track recency. We need to ensure that only positive changes kick campaigns off. We'd really like to say trigger on positive score change, but we currently only increment by +1 so change = +1 works fine for now.
Also if you have any tips or insight about my engagement question above I'd love to hear it. It's more thinking, now that I know how to do what I was trying to do, am I actually using the right tool for the job?