Im wondering what the best practise is for the logic for excluding people from entering browse, cart and checkout abandonment flows.
these are pretty standard profile filters for browse ab
added to cart zero times since starting this flow
checkout started zero times since starting this flow
has not been in this flow in the last 30 days
has not placed order in the last 30 days
has not placed order since starting this flow
But my question is, should you use “and” logic or “or” logic
different people seem to suggest different things…. but it seems to me it should be “or” logic….
any advice would be most appreciated.
Thanks
Best answer by nomanabdullah256
When it comes to excluding people from browse, cart, and checkout abandonment flows in Klaviyo, the logic you choose—whether "and" or "or"—can greatly affect how your exclusions work.
Here’s how it breaks down:
Using "AND" logic: All conditions must be met for someone to be excluded. For example, if you use “AND” between all your filters, a profile will only be excluded if they have added to cart zero times, started checkout zero times, haven’t been in the flow for 30 days, and haven’t placed an order, all at the same time. This can result in fewer people being excluded since every condition must apply simultaneously.
Using "OR" logic: A person will be excluded if any one of the conditions is met. This typically casts a wider net, so a customer will be excluded even if they meet just one of your exclusion criteria (e.g., they’ve added to cart but haven’t placed an order or they’ve been in the flow in the last 30 days).
Given your exclusions:
Added to cart zero times
Checkout started zero times
Not been in flow in the last 30 days
Has not placed an order
It seems like you're aiming to exclude people based on multiple, independent actions. "OR" logic would be the best approach because if a user meets any of these conditions, it’s reasonable to exclude them to prevent redundant messaging.
For exclusion logic in abandonment flows, “OR” is generally the better choice because you want to make sure people are excluded as soon as they meet any single exclusion criteria, rather than needing to match all criteria at once. This helps avoid sending irrelevant emails and improves the overall customer experience.
When it comes to excluding people from browse, cart, and checkout abandonment flows in Klaviyo, the logic you choose—whether "and" or "or"—can greatly affect how your exclusions work.
Here’s how it breaks down:
Using "AND" logic: All conditions must be met for someone to be excluded. For example, if you use “AND” between all your filters, a profile will only be excluded if they have added to cart zero times, started checkout zero times, haven’t been in the flow for 30 days, and haven’t placed an order, all at the same time. This can result in fewer people being excluded since every condition must apply simultaneously.
Using "OR" logic: A person will be excluded if any one of the conditions is met. This typically casts a wider net, so a customer will be excluded even if they meet just one of your exclusion criteria (e.g., they’ve added to cart but haven’t placed an order or they’ve been in the flow in the last 30 days).
Given your exclusions:
Added to cart zero times
Checkout started zero times
Not been in flow in the last 30 days
Has not placed an order
It seems like you're aiming to exclude people based on multiple, independent actions. "OR" logic would be the best approach because if a user meets any of these conditions, it’s reasonable to exclude them to prevent redundant messaging.
For exclusion logic in abandonment flows, “OR” is generally the better choice because you want to make sure people are excluded as soon as they meet any single exclusion criteria, rather than needing to match all criteria at once. This helps avoid sending irrelevant emails and improves the overall customer experience.