How to set up a conditional split by purchase count in Klaviyo

A conditional split sends people down different paths based on a condition. To split by purchase count in Klaviyo, add a conditional split to a flow, use the profile property for number of orders, set one branch for first-time buyers and another for repeat buyers, and test each path with a dummy profile.

Have this ready.

• A flow where the paths should differ, such as post-purchase or welcome
• Order data syncing so the order count is accurate
• A clear idea of what each group should see
• A test profile for each branch

Steps.

1. 1. Decide the groups

   Choose the cutoffs, for example one order, two to three orders and four or more. Keep the number of branches small.

2. 2. Add the split at the right point

   Place the conditional split after the trigger or after the first delay, so it checks the order count at a sensible moment.

3. 3. Set the first condition

   Choose the order count property or placed order metric and set the first branch to people with exactly one order.

4. 4. Add the next condition

   Use a second split on the no side to separate repeat buyers from loyal ones, or use a different rule for each.

5. 5. Write different content per branch

   First-time buyers need reassurance and product help. Repeat buyers can see newer items or a loyalty mention. Do not copy one message three times.

6. 6. Handle the timing of the count

   Remember the count may or may not include the order that triggered the flow. Test with real orders to see which side a new buyer lands on.

7. 7. Test every branch

   Create or edit test profiles with different order counts, trigger the flow and confirm each lands in the intended path.

Common pitfalls.

• Assuming the triggering order is or is not counted without testing.
• Creating many branches with near identical content.
• Leaving the else branch empty so some people get nothing.
• Changing cutoffs later without checking live profiles in the flow.

Check it worked.

• Each branch has distinct content
• Every possible profile lands somewhere
• Triggering order counting is understood
• Test profiles cover every branch
• Flow status is live

Klaviyo changes its interface from time to time, so treat the steps as the order of work and match the names to what you see on screen.

Rather have this done for you? See our email flows & automation service or book a free audit.