Targeting the Right Abandoned Checkouts
2 possible cases:
My abandoned checkout is triggered by a Shopify trigger
In this case, you can use the conditions described below with no extra step.
My abandoned checkout is triggered by a webhook
To condition the checkout in WAX, you need to make sure the condition data (number of orders, cart amount, etc.) is passed through the JSON body.
By default, the abandoned checkout flow triggers for all abandonments, with no distinction. If you want to exclude certain profiles (VIP customers, large carts, customers already followed up by email...), it's up to you to add that logic.
To do this, insert a Conditional Split node right after the flow's trigger.
This node automatically creates two paths:
Yes → the contact meets the defined condition
No → the contact doesn't meet it
It's this No branch that lets you handle "hasn't done something" cases (e.g.: hasn't opened a message in the last 30 days, hasn't already bought this product, etc.).
The 4 Types of Available Conditions
The Conditional Split offers four families of criteria. Each answers a different question:
1. Tags: "Does this contact have this tag?"
Is included→ the contact has the tagIs excluded→ the contact doesn't have the tag
Only tags created before the customer's order are picked up, not ones created afterward.
2. Properties about someone: "What do we know about this contact?"
These are the attributes stored on the contact record, for example orders_count (number of orders) or total_spent (total amount spent) — exact names to use in WAX.
Available operators:
Greater than,Less than,Equals,Does not equal,Is null,Is not null.
3. What someone has done: "What has this contact done?"
These are the events associated with the contact, filterable by date: is before, is after, is in the last, is at least.
👉 To target those who haven't done something, don't look for a negative operator here: simply use the No branch of the Conditional Split.
4. Flow variables: "What does this specific cart contain?"
Unlike the three previous types, this filter doesn't apply to the contact but to the current checkout: cart amount, product/variant IDs, checkout tags.
This is the only category that lets you filter on the content of the abandoned checkout itself; it's only available within the flow's context.
Combining Several Conditions in a Conditional Split Node
The combination logic follows a simple rule:
Action | Logic applied |
Several rows in the same block | OR |
Adding a new block | AND |
Concrete example: if you want to target contacts who have a checkout > €100 AND who don't have the "VIP" tag, you need to create two separate blocks, not two rows in the same block.