How to Build a Klaviyo Segment for Repeat Buyers
A Klaviyo segment for repeat buyers is a saved set of profile conditions — typically Placed Order at least 2 times over all time — that updates automatically as new orders arrive. You build it in Lists & Segments → Create Segment and reuse it in campaigns, flows, and exports.
The catch: a segment built sloppily drifts. Six months later you discover it excludes wholesale accounts, or includes people whose second order was refunded. This guide covers the conditions that survive contact with real data, plus the export tricks that make segments useful outside Klaviyo.
What counts as a repeat buyer in Klaviyo?
Klaviyo counts events, not orders in your admin. If your integration sends a Placed Order event, two events means two purchases. If you re-send events during a data migration, a one-time buyer can look like a repeat buyer. Check Analytics → Metrics → Placed Order for duplicate timestamps before trusting the count.
Klaviyo’s own RFM definitions use a different threshold than most merchants expect: recent means purchased in the last 60 days, frequent means 3+ orders, monetary is measured against your own average. Their “Loyal” segment combines all three. That is a starting point, not gospel — a store selling $400 desks and one selling $12 candles cannot share thresholds.
How do you build the basic segment?
Open Lists & Segments → Create Segment → Define conditions.
- Set the segment type to Person.
- Add condition:
Placed Order—at least—2—over all time. - Add a filter:
Email—is set, so you do not count anonymous profiles. - Add
Placed Order count is greater than 0 in the last 365 daysif you only want active buyers. - Save it as
Repeat Buyers — 2+ orders — active 12m.
The name carries the definition. Rename it when you change the logic, or your team will argue about a number that changed meaning underneath them.
Add the exclusions people forget
- Refunds. Klaviyo does not subtract refunded orders from the count by default. If you send
Refunded Orderevents, addRefunded Order is zero over all time— or accept that a small fraction will be misclassified. - Staff and test accounts. Exclude a
testorinternalprofile property, otherwise your team inflates every segment they appear in. - Wholesale. If B2B orders flow through the same store, filter by a
customer_typeproperty or a tag. Mixing channels in one segment makes revenue per recipient meaningless.
Should you use segments or flows for targeting?
Different jobs. A segment is a snapshot you query any time; a flow is a trigger that acts on an event. In practice, segments power campaigns (a one-off sale announcement) and flows handle the ongoing work.
One real constraint: segments re-evaluate on a schedule, not instantly. A new segment can take a few hours to populate fully on large accounts, and very complex segments with many OR conditions recalculate slowly. If you build a segment and immediately launch a campaign, verify the count against a simpler condition first.
How do you use the segment for actual revenue work?
Three patterns that pay for themselves:
| Use | Segment condition | Why it works |
|---|---|---|
| Winback | 2+ orders, none in 180 days | Best-performing re-engagement audience most stores have |
| VIP early access | 3+ orders plus revenue above your median | Small list, high conversion on launches |
| Cross-sell | Repeat buyers minus a specific product tag | Targets the next category without guessing |
For the winback one, pair it with a flow triggered on Placed Order with a 180-day delay rather than a campaign, so it stays hands-off.
What is the export workflow?
Klaviyo lets you export a segment as CSV. Two things to know. First, the export includes only the fields on the profile plus whatever custom properties you defined — order line items are not in the default file. Second, Klaviyo’s export endpoint is rate limited, so a 100k-profile segment can take a while; do not kick off three exports at once.
The more useful route for analysis is the API: GET /api/segments/{id}/profiles with cursor pagination, which gets you current membership without a stale CSV sitting in someone’s Downloads folder.
Where does this break?
Guest checkout is the big one. If your store does not create an account, Klaviyo identifies people by email, so a customer who uses two addresses is two profiles. Merge duplicates occasionally — Klaviyo has a profile merge endpoint — or your repeat rate will read low and your winback segment will email people who bought last week.
Second failure mode: conditions stacked with OR. A segment with 2+ orders OR opened email in last 30 days is not a repeat buyer segment, it is nearly your whole list. Audit complex segments quarterly.
Key Takeaways
- A Klaviyo repeat buyer segment is a saved condition set, commonly
Placed Order at least 2 times over all time. - Klaviyo counts events, so duplicated
Placed Orderevents inflate the segment. - Exclude refunded orders, staff accounts, and wholesale profiles or the numbers mislead.
- Segments recalculate on a schedule — verify the count before launching a campaign.
- Guest checkout across multiple emails splits one buyer into several profiles; merge occasionally.
