An exit condition is an event which defines when the contact should leave the automation flow.
For example, the exit condition could be the contact making an order, or visiting your site.
Exit conditions only apply after the segment stage of your flow - not during the entry wait (if set).
The customer must have fulfilled the exit condition (e.g. placed an order, made a visit, abandoned a basket) after entering the flow - events that occurred before this won't trigger an exit.
Set an exit condition
Select the cog icon to configure your exit condition:
The exit options are:
| Exit condition | Filter condition |
| Order | Contact has placed an order. |
|
Contact has placed their last order. This is any order that occurs while the contact is still in the campaign. | |
| Contact has placed their nth order (e.g. second order). | |
| Contact has placed an order which includes a product. | |
| Contact has placed an order which includes a product with an attribute. | |
| Contact has placed an order with grand total. | |
| Contact has placed an order using a coupon code. | |
|
Contact has placed an order via a channel.
Note: Order channels (e.g. online store, mobile app, in store, phone) must be defined in your API call.
| |
| Visit | Contact has viewed a product. |
| Contact has viewed a product with an attribute. | |
| Contact has visited for a time period (in seconds). | |
| Contact has visited from a source. | |
| Contact has visited a store. | |
| Abandoned Basket | Contact has abandoned a basket. |
| Contact has abandoned a basket with includes a product with an attribute. | |
| Contact has a basket in a store. |
To set up your campaign so that contacts exit after they’ve made an order, select Order > Contact has placed an order
Select Save to finalise.
If you select more than one exit condition, Ometria checks that both conditions have been fulfilled - i.e. uses AND logic, not OR logic.
Comments
0 comments
Article is closed for comments.