Loyalty Program Integration: How to Connect Your Rewards Program to Email and SMS Flows

Most "loyalty integrations" are just a data sync — points balance and tier land in a Klaviyo profile property, and nothing ever triggers off them. That's the gap costing you revenue. Connecting Yotpo, Smile.io, or LoyaltyLion to Klaviyo takes a few minutes. Building the flows that actually use that data once it arrives is the part almost nobody finishes.

This isn't a walkthrough of how to click "connect" on an integration. It's the part after that: the exact event and property structure your loyalty data needs, the trigger-split logic by tier and points balance, and three flow blueprints — points expiry, tier upgrade, redemption reminder — that your loyalty platform's help docs never cover.

Last updated: October 2026

What Does It Actually Mean to Integrate a Loyalty Program With Klaviyo?

Integrating a loyalty program with Klaviyo means two separate things: syncing loyalty data like points balance, tier, and redemption status into Klaviyo as properties and events, and then building flows that actually trigger off that data. Most brands only do the first part, which is why loyalty rarely shows up as real revenue.

Klaviyo is an email and SMS marketing automation platform that ecommerce brands use to send personalized, behavior-triggered campaigns and flows.

Yotpo is a loyalty and rewards platform that lets ecommerce brands run points programs, VIP tiers, and referral incentives natively on their store. Yotpo Loyalty, Smile.io, and LoyaltyLion all offer native Klaviyo integrations that push loyalty data into your account automatically. The setup is quick: connect an API key, map a handful of fields, and loyalty data starts appearing on customer profiles. That's the sync. It's necessary, but it's also where most teams stop, treating the connection as the finish line instead of the starting point.

The integration only becomes valuable once that data is wired into trigger logic — flows that fire when points cross a threshold, a customer moves up a tier, or a redemption window is about to close. If you haven't already confirmed your Klaviyo and Shopify data sync is capturing base purchase events cleanly, that's the prerequisite this entire integration sits on top of. And if your team hasn't built flows in Klaviyo before, the full Klaviyo flow setup process is worth reading before you layer loyalty-specific logic on top of it.

Custom Events vs. Custom Properties: The Difference That Determines Whether You Can Trigger a Flow

Klaviyo custom properties store a single current value on a profile, like current points balance or current tier, and you can segment on them but can't trigger a flow the moment they change. Custom events fire in real time and are the only data type that can start a flow automatically.

Custom properties is a field on a Klaviyo profile that holds a single current value until something overwrites it — current points balance, current tier, points-expiry date. Custom events is a timestamped record of something that happened, and it's the only data type in Klaviyo that can trigger a flow the instant it arrives. Confusing the two is the most common reason a loyalty integration looks "connected" but never actually drives a send.

Loyalty Data: Event or Property?

• Points balance: Property — segment on it ("balance above 500"), but don't expect it to trigger a flow on its own.
• Points earned (the transaction): Event — this is what should fire a flow, since it carries a timestamp and an amount.
• Tier level: Property — stores the current tier for segmentation and personalization.
• Tier changed (upgrade or downgrade): Event — this is the trigger for a tier upgrade sequence, not the static tier property.
• Points expiry date: Property — a date field you build date-based flow logic against.
• Redemption status: Event — "Redeemed Reward" fires when a customer uses points, which is what should pull them out of a redemption reminder flow.

This is the single most common reason loyalty flows never get built: the native integration syncs properties, not events, and properties alone can't start anything. If your loyalty platform's default sync only updates a few fields, you're in the same position as a brand that's never set up tracking custom events Shopify doesn't send by default — the data exists, but nothing in Klaviyo is listening for it. The fix is usually a webhook from the loyalty platform into Klaviyo's events API, configured specifically for points-earned, tier-changed, and redeemed-reward moments. Klaviyo's own Events API documentation lays out exactly how those timestamps and properties need to be structured if your platform's native integration doesn't cover it.

What Data Should Sync From Your Loyalty Platform to Klaviyo?

At minimum, four things need to sync from your loyalty platform to Klaviyo: current points balance, current tier, a points-expiry date if your program expires points, and a points-earned event with a timestamp and amount. Yotpo's native integration covers most of this by default.

Yotpo Loyalty has the most built-out Klaviyo integration of the major platforms. It pushes points balance, VIP tier, and referral status as profile properties, and it can be configured to send points-earned and points-redeemed as trackable events. The gap is usually on the expiry side — Yotpo doesn't natively sync an expiry-date property, so if your program expires points, you'll typically pull that in through a scheduled export or a direct API call rather than relying on the default sync. Yotpo publishes its own Klaviyo integration guide with the exact field mapping for your account type.

Smile.io and LoyaltyLion both sync tier and points data into Klaviyo through their respective integrations, but neither pushes a true points-earned event by default — only the end-of-day balance as a property. If you want a flow to trigger off the moment someone earns points, rather than waiting for the next scheduled profile update, you'll generally need to configure that through their webhook settings or route it through a middleware tool. It's a few extra hours of setup, and it's the difference between a loyalty flow that fires same-day and one that's always a step behind the customer's actual behavior.

The Points Expiry Flow: Trigger Logic and Timing

A points-expiry flow should never be a single email sent to everyone on the same schedule. It needs at least two touches timed against the actual expiry date, split by points value, because a customer about to lose a small balance doesn't need the same urgency as one about to lose a large one.

Points expiry flow is an automated email and SMS sequence triggered by an approaching points-expiration date, built to prompt redemption before the balance disappears.

1. Build or source a points-expiry-date property on the customer profile.
2. Create a flow triggered by a date-based segment — profiles whose points expiry date is approaching.
3. Split the flow by points value: a lower-balance tier gets a single reminder; a higher-balance tier gets a two- or three-touch sequence.
4. Send the first touch with enough lead time to act, stating the exact point count and what it's worth in plain terms.
5. Send a follow-up closer to the deadline, to the segment that hasn't redeemed, with a direct link to the redemption page.
6. Exit the flow immediately if the customer redeems or makes a purchase that resets the clock.

The timing logic here is close to what governs a replenishment flow — Blossom's benchmark data puts replenishment flows, which rely on a similar date-based trigger, between $4 and $10 in revenue per recipient. A points-expiry flow with no segmentation by points value is the loyalty version of sending every replenishment reminder on the same fixed day regardless of what the customer actually bought — it works for some people and misses everyone else's real timeline. If you're already running RFM analysis on your customer base, layer that in too. A high-value RFM segment losing a points balance is a different message than a one-time buyer who redeemed a signup bonus and never returned.

How Do Tier Upgrade Emails Work in a Loyalty Program?

Tier upgrade emails should trigger off a tier-changed event the moment a customer crosses a threshold, not off the static tier property that only tells you where someone sits today. The email itself should read like a status update, not a promotion, with no discount code attached to it.

The event for this already exists in the mapping above — it's the tier-changed event, not the static tier property. The property tells Klaviyo what tier someone is in right now; the event tells Klaviyo the exact moment it changed, and a flow needs the event to fire at all.

Treat the copy like a status-recognition moment rather than a sale. The tone should mirror what we'd use for rewarding your best customers without giving anything away — the upgrade itself is the reward. Stacking a discount code on top of it cheapens the thing the customer just earned, and it trains your highest-tier members to wait for a coupon instead of feeling recognized.

The Redemption Reminder Flow: Closing the Loop on Unused Points

A redemption reminder flow is not the same as a points-expiry flow, even though the two can look identical from a distance. Expiry flows fire off a date on the calendar; redemption reminders fire off a points balance that's been sitting unused for a set stretch of time, regardless of when it expires.

Keep these as two separate flows with two separate entry conditions. A customer who earned a meaningful points balance recently and hasn't redeemed anything is a different problem than a customer whose points are about to expire. Collapsing both into one generic "loyalty update" email is exactly the kind of send that underperforms a split, behavior-triggered sequence — the reader can't tell if the email is urgent or just a reminder, so it reads as noise and gets ignored.

• Dormant balance trigger: points balance above a set threshold with no redemption activity in roughly a month.
• Threshold-crossed trigger: points balance just crossed into reward-eligible territory for the first time.
• Browse-without-redeem trigger: the customer visited the rewards page but didn't redeem, if your platform tracks that event.

Revenue per recipient (RPR) is the average revenue a flow generates per email delivered, and it's the cleanest way to compare a loyalty flow's performance against every other automated send you run.

Flows that trigger off real customer behavior average $1.94 in revenue per recipient compared to $0.11 for standard campaign sends, according to Blossom's benchmark data. A loyalty integration that never triggers a flow is leaving that entire gap on the table.

Not sure if your loyalty data is actually driving flows or just sitting in a profile field? Get your free lifecycle audit — we'll score your loyalty integration against the trigger logic above.

How Should Loyalty Flows Coordinate With Your Winback and VIP Flows?

Loyalty flows need explicit suppression logic against your winback and VIP flows, or a lapsed customer with an expiring points balance can end up receiving two separate come-back messages within days of each other. Loyalty data should inform those flows, not compete with them for the same inbox moment.

A lapsed customer with expiring points is the textbook overlap case. If your winback flow and your points-expiry flow both have that person in scope at the same time, they could get two unrelated "come back" messages days apart — one about the brand, one about their points. Pick one as the lead message and have the other stand down, or reference it directly.

The cleaner fix is usually to fold the points balance into your winback flow as a data point instead of running two competing sequences. "Your points are expiring soon" is a stronger line inside an existing winback email than a brand-new flow fighting for the same inbox moment. The same logic applies to VIP flows — a VIP who's also mid-sequence in a generic tier-upgrade email is getting a demotion in tone at exactly the wrong time.

Why Don't Most Loyalty Integrations Drive Revenue?

Most loyalty integrations don't drive revenue because the project stops at the data sync. The points balance shows up on the profile, the dashboard says the integration is connected, and nobody goes back to build the flows that would have made the sync worth doing in the first place.

This is diagnosable in about five minutes. Open your Klaviyo flows list and search for anything referencing your loyalty platform. If what comes back is nothing, or a single flow that fires one "welcome to the program" email, the sync is doing a fraction of what it could. The data is already there, sitting in profile properties. Nothing is reading it, because nothing was ever built to.

Build the Flows, Not Just the Sync

Turning a loyalty integration into revenue means mapping points-earned, tier-changed, and redemption events correctly, building the points-expiry, tier-upgrade, and redemption-reminder flows as separate sequences, and coordinating them with your winback and VIP flows so they don't collide. That's the work most brands skip after connecting the sync.

The checklist here isn't complicated: map your loyalty data into the right mix of events and properties, build the points-expiry, tier-upgrade, and redemption-reminder flows as three separate sequences with their own trigger conditions, and make sure none of them collide with your winback or VIP flows. None of that requires a new tool. It requires going back into an integration you probably already paid for and finishing the job.

Start with whichever flow is missing entirely. If there's a points-expiry date sitting unused in a Klaviyo property right now, that's the one email most likely to be costing you redemptions today.

Want these flows built and mapped to your specific loyalty platform? Book a free strategy call — we'll map out your next 90 days of loyalty-driven retention revenue.

Frequently Asked Questions

The questions below address the specific points of confusion that come up most often when connecting a loyalty platform to Klaviyo, including how the data sync works, what events trigger flows, and how points-expiry and redemption reminders should be structured and timed.

How do I connect my loyalty program to Klaviyo?

Most loyalty platforms — Yotpo, Smile.io, and LoyaltyLion included — offer a native Klaviyo integration you activate with an API key inside their app settings. That connects the data sync. Getting flows to actually trigger off that data is a separate step that requires mapping the right events, not just properties.

Can you automate loyalty points expiry emails?

Yes, by building a date-based flow off a points-expiry property, split by points value so higher-balance customers get more touches than lower-balance ones. A single generic expiry email underperforms a segmented, multi-touch sequence timed against the actual expiry date.

What data does Yotpo send to Klaviyo?

Yotpo's native integration pushes points balance, VIP tier, and referral status as Klaviyo profile properties, and can be configured to send points-earned and points-redeemed as events. It does not natively sync a points-expiry date, which most brands have to pull in separately if their program expires points.

Does Klaviyo integrate with Smile.io or LoyaltyLion?

Yes, both platforms have native Klaviyo integrations that sync tier and points data as profile properties. Neither pushes a true points-earned event by default, so triggering a flow off individual earning activity usually requires configuring their webhook settings or routing through a middleware tool.

How do you remind customers to redeem loyalty points?

Build a dedicated redemption reminder flow triggered by a dormant points balance rather than folding the reminder into your points-expiry flow. The two have different trigger conditions and should run as separate sequences so each message stays specific to the actual situation a customer is in.

Get tactics like this in your inbox every week. Subscribe to our newsletter →