All Smart Campaign Flow Steps (with one exception) have the option to add a choice.
This condition – which is built by one filter, one operator and one or more values – is pretty flexible. Can be something like the screenshot above. If the first name of the email recipient is “Michael” they receive Michael’s Version, and if not, they receive the default version.
In the filter you can have any database field or activity data like “Was Sent Email” or Custom Objects/Activities and lots more. Very useful. But you can only use simple choices, not complex ones like e.g.
First Name = Michael AND was sent any email in past x days.
But you can help yourself with Smart Lists which contain these complex filters.
Let’s say for example that you want to build a choice on empty states, but only for the United States and not Canadian empty states. Build a Smart List like this:
… and use it with the “Member of Smart List” filter in your Flow Step Choice:
You might think that this complexity might impact processing speed of this flow step, but actually I have never seen it fail. Even when my Smart Lists contained a substantial number of filters. Give it a try!
If you read this article from the start you might wonder: Which Flow Step does not allow a choice? It’s the Wait.