My team has a triggered abandonment program to send consecutive emails. To do so, we use a Smart Campaign triggered on Person is Created. Meanwhile, there is a Smart List that captures people who have "abandonment" per our definition. The smart campaign flow steps uses Member of Smart List to send the emails with wait steps between emails sends (e.g. if Member of Smart List, then send the email). The idea is that, if the person converts, they are no longer in the smart list, and thus should not get any future emails. However, we are noticing that people who are in the Smart List only get the first email and none any afterwards. Why is this?
Can you send a screenshot of your smart list config and your smart campaign config please? It is a bit hard to know what is going on.
For the campaign, can we see both smartlist and flow.
Cheers
Jo
Here is the flow in question
How are you proving to yourself that people are still in the Abandonment Qualifiers2 smart list at the point they hit step 4?
Also, what is step 1?
Can you also show how the smart list is populated please?
Also, apologies for missing some of your question. Step 1 in the Flow is a wait step, specifically Wait: Duration 1 hour. There are four totals emails with four wait steps sandwiched between: wait, send, wait, send, wait, send, wait, send
To prove the assumption is that Smart Lists inherently remove people who no longer meet the criteria in the Smart List. So, if the lead that entered in the Smart Campaign Flow is not longer in the Smart List, then by then will not proceed to the other step by the time the wait time has run down.
Here is the Smart List that is the qualifier in the Smart List
We use mostly custom fields but generally having the Logic set to ALL makes it rather black and white.
have you checked to see if the people only receiving a single email have either unsubscribed, or have an invalid email?
Cheers
Jo
I have checked. Generally, the people run through the program and only receive the first email. I have not seen a trend of invalid or bounces.
To prove the assumption is that Smart Lists inherently remove people who no longer meet the criteria in the Smart List.
Not so much an assumption as the definition of a Smart List. The "smart" part is the automatic dis/qualification of people as they match/unmatch filters.
The question is simply whether they're members of the uncached Smart List at the time you think the flow step should be skipped.
Yes, I completely agree. So as far as your concerned, this logic using Smart Lists should work?
Yes. The logic should work.
The question is, are they still in the smart list when they hit the second email send. Check the activity history for a record, and see if any of the data points you are using have changed for that person.
Given you said you were using 'all' as your filter criteria (which is the equivalent of a series of Boolean ANDs), only one value would need to change to drop someone out of the list.