Remove from Flow Based on Value Changes - Secondary Campaign?

[nhabischWings]

Hey all!

Working on a campaign that basically flows like:

Lead has Pre-Approval: Add to Program (Data Value Change from False to True)

Send Email 1

Wait

Send Email 2

Remove from Flow

Simple - but my question is, they can be also be removed from the flow at any point based on a different data value change (say True to False)

I'm assuming the best solution is to make two campaigns within the program:

Campaign 1 - The initial insertion data change + email flow

Campaign 2 - Basically an exiting campaign that if they're a member of Campaign 1 and meet  the exiting criteria (Data Value Change from True to False)

Would this work?

[SanfordWhiteman · Accepted solution]

Depends. If you only care about the value at the time they exist from the Wait, you can simply have the conditional Remove from Flow run directly before the Wait.

More complex/timely reaction to the Data Value Changes would require your separate SC.

[nhabischWings]

Thank you!

Yeah, the separate SC is probably the way to go as it needs to be timely in that the data would change through the API.

Thank you for your help!

[SanfordWhiteman]

To be clear, even if the data changes via API, you could still wait for the Wait to be over and then remove them before anything else happens. They aren’t going to be doing anything destructive during the flow with the Wait.

However, if the field might, say flip between true and false multiple times, you do want to trigger on Data Value Changes.