Klaviyo Loyalty Integration for Shopify: Setup Guide

Before you build a single flow, write down the fields Klaviyo needs to make loyalty decisions. The minimum set is current points balance, current tier, lifetime points, reward availability, next-tier progress, wallet pass installed, referral code, and the date of the last redemption. Add points expiration date if the program uses expiring balances.

Each field needs one owner. Shopify owns customer identity and orders. Your loyalty platform owns points, tiers, rewards, wallet pass status, and referral status. Klaviyo should receive the clean state, not calculate it from fragments. When two systems try to infer the same value, your segments will drift and customers will receive stale messages.

Use stable lowercase property names such as loyalty_points_balance and loyalty_tier. Define the expected type for each property before launch: number, boolean, string, date, or list. A boolean reward_available flag is easier to filter than a text field that sometimes says yes, available, or blank. Do not rename fields after launch unless you are ready to rebuild every segment and flow filter that uses them. Keep the contract in a shared document with examples from one real test profile, so marketing, support, and engineering can check the same source when something looks wrong. Review it before every campaign that depends on loyalty targeting.

Profile properties describe the current state. Events describe moments. A working Shopify loyalty integration needs both because Klaviyo uses them in different parts of the product. Properties power segment rules and message personalization. Events trigger flows, feed timelines, and give operators a record of what changed.

Start with six event types: Loyalty Joined, Points Earned, Reward Available, Reward Redeemed, Tier Upgraded, and Points Expiring Soon. Those events cover onboarding, progression, redemption, VIP recognition, and urgency. For each event, include the points balance after the event, reward value if one exists, tier before and after when relevant, source channel, and Shopify order ID when the event came from a purchase.

Keep event names merchant-readable. Your retention manager should understand the metric list without opening developer docs. Avoid one generic Loyalty Updated event that forces every flow to inspect properties after the fact. Specific events make reporting and debugging much easier. If your team also needs the strategic layer, pair this setup with Klaviyo loyalty flow examples so every event has a clear campaign use case. Before launch, fire each event once from a test customer and confirm it lands with the properties a flow will need. That keeps setup decisions tied to real campaign behavior.

Bad matching ruins loyalty messaging. If one shopper has two Klaviyo profiles, one with points and one with purchase history, every segment becomes weaker. The customer might qualify for a reward reminder on one profile while the purchase event that should suppress the reminder sits on another profile.

Your integration should match on Shopify customer ID first, then email or phone as secondary identifiers. For POS-heavy stores, staff should attach the customer profile before checkout whenever possible. If the customer uses a wallet pass in store, that scan should resolve to the same Shopify customer record. The goal is one customer, one loyalty balance, one order history, and one Klaviyo profile that receives the next message.

Do not use manual CSV uploads as the normal sync path. CSV can help with backfills, but live loyalty data belongs in an integration that updates profiles and events as customers earn, redeem, and move tiers. Set a policy for merges too. If support merges Shopify customers or Klaviyo profiles, the loyalty balance and pass status should follow the surviving profile. Review duplicate profiles during the first week after launch, then monthly once the sync is stable. That cadence keeps identity quality from becoming invisible again.

Do not launch with 25 segments. Start with the three that prove the sync works and create immediate revenue opportunities. A small segment set makes it easier to spot bad data because every audience has an expected size and a clear business purpose.

- Reward available. Customers where loyalty_reward_available is true and no redemption happened in the last 30 days.

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

- At-risk VIP. Customers where loyalty_tier is Gold or higher and no order happened in the last 60 days.

For each segment, write the intended action before building the filter. Reward available should drive redemption. Near next tier should drive an achievable next purchase. At-risk VIP should protect high-value customers before they lapse. If a segment does not have a message, owner, and success metric, leave it as a later reporting idea.

These segments connect naturally to Klaviyo loyalty segments, where you can expand into reward sitters, tier-stuck customers, and wallet-pass non-installers after launch. Snapshot the counts before flows go live, then compare them after the first batch of loyalty events arrives. If the counts surprise you, debug data before launching copy.

A loyalty integration should be tested with real behavior, not just a connected-app screen. Create a test customer, place a small Shopify order, award points, redeem a reward, move the customer to a new tier, install the wallet pass, and expire a test reward. Use the same storefront, checkout, and POS paths customers will use in production.

After each action, check three places: the loyalty platform, the Klaviyo profile, and the matching Klaviyo metric timeline. The values should update within the time window your platform promises. Record the timestamp from each system so you know whether a delay is expected queueing or a sync problem.

Then preview every flow with that test profile. Make sure dynamic point balances render correctly, profile filters allow the right customer in, and reward emails do not send after the reward has been redeemed. Test negative cases too: a non-member should not enter reward flows, a customer with no pass should not see pass-installed copy, and a redeemed reward should suppress reminders. Keep the QA checklist in the launch doc because it becomes the fastest way to debug future changes. Run it again after any loyalty app configuration change. Include screenshots for the launch owner.

The first week tells you whether the integration is operational or just technically connected. Watch profile property freshness, event volume, segment counts, flow skips, reward redemptions, wallet pass installs, and revenue per recipient. Build a small daily view instead of waiting for a monthly performance review.

Flow skips matter most. If customers enter a loyalty flow but fail profile filters, the flow may be checking the wrong property or stale data. If reward emails send but redemptions do not move, the offer may be weak. If redemptions happen but Klaviyo does not record the event, reporting will understate loyalty revenue. Segment-count swings also deserve attention. A sudden collapse in reward-available customers might mean rewards are redeeming well, but it can also mean a boolean property stopped syncing.

Assign one owner to the dashboard. Engineering can fix sync failures, but retention owns whether the messages are useful and whether the timing matches customer behavior. Tie the results back to broader retention reporting with the loyalty ROI calculator so the integration has a business owner, not only a setup owner. After week one, keep the same checks weekly before major campaign sends. Add a Friday review before changing any live filters. Document every adjustment.