Klaviyo Loyalty Segments: 12 Audiences to Build

Good segments start with clean properties. The core set is loyalty_member, loyalty_points_balance, loyalty_tier, loyalty_lifetime_points, loyalty_reward_available, loyalty_next_tier_progress_pct, wallet_pass_installed, and last_reward_redeemed_at. These fields let Klaviyo separate membership, value, momentum, reward intent, and channel activation.

Add referral_code, referral_count, points_expiration_date, and last_wallet_pass_scan_at if your program uses referrals, expiring points, or in-store loyalty. Do not add properties just because the loyalty platform can sync them. Every property should support a segment, flow, report, or support use case. Otherwise the profile becomes noisy and harder for operators to use.

Keep each property focused. loyalty_tier should store the current tier only. loyalty_points_balance should store current redeemable points only. If you overload one property with several meanings, segment logic becomes hard to trust. Define property types before launch too. A number can be compared with greater-than filters. A date can drive expiration logic. A boolean can split pass installers from non-installers. A text field that mixes values forces manual cleanup. The cleanest loyalty segmentation programs look boring at the data layer because every property has one meaning. Add sample values to the data contract so campaign builders know which filters are safe. Recheck the sample profile after each sync release. Remove unused properties during quarterly cleanup. Keep field owners documented.

Start with segments that are easy to understand and easy to activate. Launch segments should not be clever. They should point to a message your team can send this week and a metric your team can review next week.

- Reward sitters. loyalty_reward_available is true and has not redeemed reward in 30 days.

- Near next tier. loyalty_next_tier_progress_pct is at least 80 and customer has ordered in the last 90 days.

- At-risk VIPs. loyalty_tier is Gold or higher and has not placed order in 60 days.

- Wallet pass not installed. loyalty_member is true and wallet_pass_installed is false.

These four segments support immediate Klaviyo campaigns and the first Klaviyo loyalty flow examples without creating audience clutter. Give each segment one default action. Reward sitters get a redemption reminder. Near-tier customers get progress copy and a targeted collection. At-risk VIPs get status-aware reactivation. Wallet pass non-installers get a pass install prompt when they have a balance or reward worth storing. Before flows go live, snapshot segment counts and inspect at least 10 profiles in each audience. That catches field naming errors, stale syncs, and customers who technically match the rule but should not receive the message. Save those counts for the launch review.

Once launch segments work, add value-based audiences. These help you decide who gets attention, not just who qualifies for a generic offer. Loyalty data is more useful when it changes priority, treatment, or budget allocation.

Build high-LTV loyalty members, high-LTV non-members, new members with no second purchase, and discount-sensitive redeemers. Each audience answers a different question. Who deserves personal retention treatment? Who should be invited into loyalty? Who joined but has not formed a habit? Who only buys when a reward is available? Add a high-potential segment too if your store has strong first-purchase indicators, such as high first order value or premium category purchase.

Pair these with loyalty ROI reporting so campaigns are measured by margin and repeat purchase behavior, not only clicks. A reward-sitter campaign can look good on revenue while training customers to wait for discounts. A VIP service message might produce fewer clicks but protect higher-margin repeat purchases. Use Shopify order history for spend, margin proxy, product category, and recency. Use loyalty properties for tier, balance, rewards, and pass status. The combined view is what lets you choose personal treatment for the customers who justify it. Revisit value thresholds quarterly as AOV changes. Check margin before discounting.

Every retention team should know the difference between loyalty members and non-members. Otherwise, program performance gets buried inside blended customer reports. A campaign can appear healthy overall while loyalty members are doing the work and non-members are not changing behavior.

Create four basic reporting segments: loyalty members, non-members, members with a purchase in the last 90 days, and non-members with a purchase in the last 90 days. Track repeat purchase rate, average order value, email engagement, reward redemption, and pass install rate. Keep the purchase window consistent across member and non-member segments so the comparison is fair.

This also helps acquisition. High-value non-members are a strong loyalty invitation audience. New non-members after first purchase should enter a wallet pass or loyalty welcome path, not the same generic post-purchase sequence as everyone else. Do not assume every non-member needs the same pitch. A first-time buyer may need a simple explanation of points. A repeat buyer with no membership may need proof that loyalty benefits match how they shop. A retail shopper may need wallet pass convenience. Member and non-member segments give you the base layer for those decisions, then behavior adds the nuance. Use the same split in monthly reporting dashboards.

Segment overlap causes confusing sends. A customer can be at-risk, near-tier, and reward-available at the same time unless you set a priority system. Without priority, Klaviyo can be technically correct and still create a bad customer experience.

Define priority before launch. For many merchants, the order is transactional loyalty notices first, then VIP retention, then tier progression, then general campaigns. That means points-expiring and reward-expiring messages win over a broad promotional send. If a VIP customer also has a reward available, the message should usually acknowledge both status and reward rather than sending two unrelated emails.

Use suppression logic inside campaigns and filters inside flows. If a customer is in the points-expiring flow, suppress them from the generic weekly promotion unless the promotion directly supports redemption. If a near-tier customer just purchased, suppress progress prompts until the new balance and tier data settle. Document the priority ladder in plain language so campaign builders do not have to rediscover it during a deadline. Review overlap before big sale periods, product launches, and loyalty events because those are the moments when many segments become active at once. The goal is not fewer messages in every case; it is one coherent next best message.

A segment without an action is just reporting. Assign one owner, one message type, and one success metric to every loyalty segment. This prevents the segment library from becoming a graveyard of audiences that nobody trusts or uses.

Reward sitters need a redemption reminder and redemption rate. Near-tier customers need a progress email and tier conversion rate. At-risk VIPs need a reactivation path and repeat purchase rate. Wallet pass non-installers need an install prompt and pass install rate. Member and non-member segments need reporting cadence, not necessarily a flow. High-LTV segments may need a service or merchandising playbook rather than a standard discount campaign.

Then connect results back to the broader customer retention strategy. Loyalty segments should help you decide what to send, who to prioritize, and where the program needs repair. If reward sitters never redeem, the reward may be hard to use. If near-tier customers do not progress, the threshold may be too far away. If wallet pass non-installers ignore every prompt, the pass value may not be clear enough. Archive segments that have no owner or action for 60 days. A smaller, governed library beats a long list of clever audiences. Add notes before archiving so future teams understand why.