Exit conditions in Spur are conditions that stop a flow as soon as those are met. Here is an example to help you understand these better:
Spur's Abandoned Checkout Flow:
This flow has multiple messages, but we don't want to send a message to people who have placed on order, after receiving just one message.
So we have added an "Order Placed" exit condition to prevent further messages from going if an order is placed.
Similarly, we don't want to spam people with Abandoned Cart messages, which is why we have limited the flow to be sent only once in a 24 hour period.
You can see and edit exit conditions by clicking on the Starting Trigger of the flow.
To add an exit condition, simply click the button below the trigger that says "+Exit Condition".
You can add upto 10 exit conditions to a flow.
Explanation of All Available Exit Conditions
Which Exit Conditions are available to you depend on the trigger and whether you have a Shopify, WooCommerce or Custom Store. If you don't see an exit condition listed below in your flow, they simply might not be available for that trigger/store.
Has been in this flow
Prevents a flow from triggering if it has already been triggered for a number in the last x amount of time, where x is the time defined when setting up the Exit Condition.
Useful for preventing spam and making sure a message is not sent multiple times.
Belongs to a Segment
Prevents a flow from triggering if the contact belongs to a particular segment(s).
Useful for preventing a message from going to an audience you wouldn't want to send it to.
Customer Has responded
Prevents a flow from triggering if the person on the other end responds.
Useful in cases where a flow would send multiple messages, but you wouldn't want to send further messages if the person on the other end has something to say.
Order Placed
Prevents a flow from continuing if the person on the other end has placed an order since the flow initially started.
Useful in cases where you might be prompting a contact to place an order and don't want to bother them once they have already placed it.
Checkout started
Prevents a flow from continuing if the person on the other end has started checkout since the flow initially started.
Useful in cases where you might be prompting a contact to start checkout and don't want to bother them once they have already started it.
Order Fulfilled
Prevents a flow from starting/continuing if the order that triggers this flow is fulfilled.
Useful in cases where you wouldn't want to send certain messages after an order is fulfilled.
Order Contains All These Tags
Prevents a flow from starting/continuing if the order that triggers this flow contains certain tags.
Do note, ALL the tags added to the field need to be present to stop the flow, meaning if one tag is there and others aren't, the flow will continue.
Useful in cases where you'd like to prevent a flow from continuing when a tag is added to the order, whether as part of the flow or as part of some other external action.
Order Cancelled
Prevents a flow from starting/continuing if the order that triggers this flow is cancelled.
Useful in cases where you'd like to stop a flow if the order is cancelled, like preventing cross-sell messages after an order.