Know this before using "Remove from Flow" step targeting an Executable campaign

Welcome to the first email edition of Purple Me Up! I never expected to have so many of you join me here in such a short time (this is literally a dream come true). Thank you so much again for all the support! 🙏

Without further ado, let’s get into today’s piece!

Executable campaigns are awesome, and I use them all the time for cases where there’s a need for synchronous execution of flow steps in the parent campaign, i.e., the steps in the child campaign must complete before the next steps defined in the parent campaign.

Did you know that the “Remove from Flow” step, when run for a person in an executable campaign, removes the person from both executable and executor campaigns?

Check the below setup:

An executable campaign with a “Remove from Flow” step:

An executor or parent campaign that executes the above campaign using the “Execute Campaign” flow step:

Now, when I ran a person through the above executor campaign, they got into the executable campaign’s flow as expected* and got added to the “Test List” per step 1 in the executable campaign, but as soon as the person ran through the “Remove from Flow” step to get removed from the executable campaign, they got removed from the executor (parent) campaign as well. 🤯

Since the person got removed from both campaigns, subsequent flow steps, i.e., “Change Country to USA” and “Change Person Score to +30” in the executable and executor campaigns respectively, never ran for this person.

Check out the activity log of the person below:

*Please note that the smart list and qualification rules of both campaigns were set so this person could flow through them

This is one of those things that a lot of people tend to overlook or are just unaware of (even though it’s mentioned in the product documentation), which could clearly cause unnecessary MOPs fires.

That’s it for the first edition! Make sure to check out my other posts on Purple Me Up for more amazing gotchas and tips.