
You can automate loyalty rewards email for most recurring customer moments, from enrollment through points expiry. The work shifts from building one-off sends to setting rules, event triggers, and checks that keep each message accurate.
Short answer: Most recurring loyalty communications can run automatically when loyalty events reach an email platform. Welcome, points-earned, reward, expiry, and win-back flows need little daily work, but you still need to review reward rules, consent, timing, and performance.
What does it mean to automate loyalty rewards email?
The loyalty platform records the event
Loyalty automation has three layers. First, your loyalty system decides what happened: a customer joined, earned points, redeemed a reward, reached a VIP tier, or has points approaching expiry.
A Shopify loyalty program holds the underlying record. That matters because an email is only as reliable as the balance, reward eligibility, and event behind it.
Mage records loyalty activity and can send branded emails when customers earn points, unlock rewards, reach a VIP tier, and take other loyalty actions. It can also pass loyalty data into a connected marketing platform.
The email platform turns the event into a message
The email platform receives an event or reads a synced customer property. It then decides whether to send immediately, wait, suppress a message, or branch based on information such as a customer’s points balance or VIP tier.
A points-earned message can show the points awarded and the earning rule. A reward-redemption email can show the reward name, discount type, and code.
Automation is not the same as removing oversight
Automation handles repeatable delivery. It does not validate whether points should clear immediately, whether a reward is too generous, or whether a customer has already received several emails that day.
Build the rules first, then let the events carry the communication.
“I looked into so many different integrations for loyalty and referrals for our Shopify Store, but no one impressed me more than Mage on human connection, customer service, and value.”


Read the Reelie case study →
Myth: a loyalty program on autopilot needs no human oversight
What automation can handle
Automation can send a message after a defined event, personalize copy with loyalty data, wait for a chosen period, and branch based on customer attributes.
For example, a customer can receive a points-earned email after their purchase points are approved. A customer who changes tier can receive a message that explains their new benefits without someone building that email manually each time.
What automation cannot decide for you
Automation cannot decide whether the reward economics work. It cannot judge whether a short expiry window feels fair, whether a campaign conflicts with an abandoned checkout flow, or whether an email should go to someone who has not consented to marketing.
It also cannot resolve poor event design. If purchase points remain pending until the return window closes, the flow should wait for the approved points event rather than celebrate spendable points immediately.
Why reward logic comes before email logic
Set earning rules, approval timing, redemption conditions, exclusions, and expiry policy before building the flow. Then write the email around the actual customer state, including pending points when they are not yet available to spend.
Why automate loyalty email flows in the first place?
Reach customers at the moment loyalty activity happens
A loyalty event gives you a relevant reason to contact a customer. Joining, earning, redeeming, moving up a tier, or nearing expiry are clearer prompts than a broad weekly campaign.
Your email should continue that moment with a useful next step, such as viewing rewards or checking tier progress.
Keep loyalty visible between purchases
Customers can forget their balance, tier status, and available rewards between orders. Automated flows keep the program present without requiring your team to create a fresh campaign every time someone takes an action.
This is especially useful for a beauty loyalty program, where replenishment, review, birthday, and loyalty activity can create several well-timed reasons to return.
Reduce repetitive campaign work without losing relevance
Shopify separates marketing automations and customer segments from Shopify Flow workflows, which use triggers, conditions, and actions. Shopify’s automation tools can support targeted communication, while loyalty-specific events usually come from the connected loyalty platform.
Email automation can perform well as a general channel. Klaviyo reports an average 2.1% placed-order rate for automated emails and $3.56 revenue per recipient for email flows in its 2026 benchmarks, not loyalty-specific or Mage merchant results.
The core loyalty email automation flows to build
| Flow | Trigger or audience | What the email should do | Human check |
|---|---|---|---|
| Welcome | Loyalty enrollment | Explain earning and redemption | Confirm signup bonus and consent |
| Points awarded | Approved points event | Show points and earning reason | Check pending-point timing |
| Reward redeemed | Reward redemption event | Confirm reward and code | Confirm code and expiry |
| VIP tier change | Tier movement | Explain new tier benefits | Check upgrade and downgrade copy |
| Referral | Invite, claim, or reward event | Confirm the specific referral stage | Keep event meanings separate |
| Points expiry | Points nearing expiry | Show balance and deadline | Review expiry policy and suppression |
| Win-back | Dormant loyalty member segment | Remind customers of available value | Exclude recent purchasers |
Welcome flow after loyalty enrollment
Trigger this flow when a customer joins for the first time. Mage’s Welcome event can trigger a message after a customer enrolls in the loyalty program.
Explain how the program works: how to earn, what rewards exist, and where the customer can see their balance. Link to the loyalty page rather than trying to explain every rule in one message.
Points-earned or points-pending message
A Points Awarded event can include context such as the points awarded and earning rule. “You earned points for your purchase” is more useful when it tells the customer what changed.
Use a separate pending-points message only if it helps customers understand the wait. Purchase points may be held through an approval period, such as a refund window, so do not present them as immediately spendable before they have cleared.
Reward available and reward redeemed emails
A reward-available email should tell customers they can take a specific action, not imply every balance automatically unlocks every reward.
A Reward Redeemed email should confirm the reward name, points spent, discount type, and discount code. Then give the customer one next action, such as shopping eligible products or viewing their remaining balance.
VIP tier change and referral messages
A tier-change email should name the new tier and explain the benefits that now apply. If the customer has moved down, explain current status without pretending it is a celebration.
Keep referral messages separate. An invite sent means the advocate shared an invitation. A referral claimed means the friend claimed an offer. A referral reward earned means the advocate qualified for their reward after the referred friend completed a purchase.
Points expiry warning
Expiry is a high-intent reminder, but it needs restraint. Mage’s Points Expiry Soon event covers points expiring within the next seven days and aggregates them into one event per customer during that window.
You can send the reminder through Mage email templates or a connected platform. Include the expiring amount and current balance where available. Avoid stacking a separate promotional campaign on top of it.
Win-back and re-engagement flow
Build win-back from loyalty data, not just a long gap since purchase. A customer with a balance, close tier progress, or unused reward has a concrete reason to return.
Suppress customers who have purchased recently. For more ideas on diagnosing inactivity before adding another offer, see how to fix a loyalty program customers stopped using.
How loyalty events trigger email platform flows
| Layer | System | Role | Example |
|---|---|---|---|
| Loyalty rule | Mage | Evaluates customer activity | Purchase points become approved |
| Event or profile data | Mage integration | Sends event or syncs attributes | Points Awarded or VIP tier property |
| Flow logic | Email platform | Applies timing, branches, and suppression | Wait before sending an expiry email |
| Delivery | Email platform | Sends the message | Personalized points-earned email |
| General workflow | Shopify Flow | Runs connected triggers, conditions, and actions | Third-party app workflow where supported |
Mage events versus Shopify-native triggers
The sequence is straightforward: a customer acts, Mage evaluates the loyalty rule, Mage updates loyalty data or fires an event, and the email platform decides whether the customer enters a flow.
Shopify Flow supports triggers, conditions, actions, and third-party app connectors. Shopify Flow’s reference does not mean Shopify Flow alone creates loyalty-specific events. The loyalty app must expose the relevant data or action.
Klaviyo flow setup
Mage can sync points balance, lifetime points, redeemed points, VIP tier, birthday, enrollment date, and a cash value when flexible redemption is enabled. Its Klaviyo loyalty integration can also send events such as Points Awarded, Reward Redeemed, VIP Tier Changed, referral events, Points Expiry Soon, and Mage Welcome.
Send test events before building flows, because Mage events need to appear in Klaviyo before they are available as triggers. Enable only the events you plan to use.
Attentive journeys and subscriber attributes
Mage can send loyalty attributes and custom events to Attentive for use in segments and journeys. Mage supplies the loyalty state, while Attentive determines audience and delivery.
A customer’s attributes can support segments such as high points balance or a specific VIP tier.
Dynamic event data inside the email
Use customer properties for longer-term facts such as current tier or enrolled date. Use event properties for the immediate context, such as points awarded, reward name, discount code, points expiring, or days until expiry.
Add fallback values. Klaviyo can treat a zero points balance as empty, so an email should display zero rather than leaving an unexplained blank space.
What still needs human oversight after the flows are live?
| Area | What to review | Warning sign |
|---|---|---|
| Reward economics | Earning rates, rewards, exclusions, approval timing | Redemptions exceed expected cost |
| Consent and deliverability | Subscription status, suppression, sending rules | Customers report unwanted messages |
| Timing and overlap | Flow delays, campaigns, checkout messages | Multiple messages arrive together |
| Expiry policy | Window, reminders, customer notice | Customers lose balances unexpectedly |
| Edge cases | Refunds, zero balances, downgrades, missing names | Broken personalization or complaints |
Reward economics and eligibility
Review earning and redemption rules before launch, after major promotions, and when product margins change. Confirm whether purchase points are approved immediately or held until the return window closes.
Points expiry is off by default, and points earned before expiry is enabled never expire. That policy needs clear communication before you switch it on.
Consent, deliverability, and suppression
Check that your sending platform’s subscriber and consent requirements are followed. Do not assume every loyalty member is eligible for a marketing email.
Review suppression rules, frequency limits, and bounce or unsubscribe trends.
Timing, overlap, and customer experience
Map loyalty flows against promotional campaigns, abandoned checkout emails, order notifications, and referrals. Prioritize the most useful message when two events happen close together.
Automated loyalty communication does not always need another discount. You can build retention without discounting by reminding customers about progress, access, benefits, and rewards they have already earned.
Testing edge cases
Test zero balances, pending points, partial refunds, expired balances, tier downgrades, duplicate events, unsubscribed profiles, and missing names. Send tests to your own inbox and check them on mobile before activating the flow.
How to build a loyalty program on autopilot without making it feel automated
Start with five flows, not fifteen
Begin with welcome, points awarded, reward redeemed or available, expiry warning, and win-back. These cover enrollment, activity, redemption, urgency, and re-engagement.
Add tier, referral, birthday, cashback, and gift reminder flows only after you trust the data and timing in the core set.
Write the message around the customer action
Use one clear call to action. “View rewards,” “Redeem now,” “Shop,” or “Keep your status” gives the customer a practical next step.
Use event data to explain what just happened. A message that names the earning rule or reward feels more relevant than a generic loyalty announcement.
Use segments and branching for relevance
Use customer properties for longer-term segmentation and event properties for the immediate reason for sending. Branch by tier, balance, recent purchase activity, or approval status where those distinctions change the message.
Create a monthly oversight routine
Review delivery, clicks, redemptions, unsubscribes, flow errors, and customer replies monthly. Review reward economics, expiry policy, and suppression rules quarterly.
Frequently asked questions
Can loyalty rewards be fully automated by email?
Loyalty rewards can be largely automated when a loyalty platform sends events and customer data to an email platform. Merchants still need to manage rules, consent, timing, and performance.
What loyalty email automation flows should I set up first?
Start with welcome, points awarded, reward redeemed or available, points expiry warning, and win-back. These cover enrollment, activity, redemption, urgency, and re-engagement.
How does a points expiry email automation work?
A points expiry email automation sends a reminder when a customer has points approaching expiry. Mage can send a built-in expiry email or pass an event to a connected platform, and its expiry event groups points expiring within the next seven days into one reminder window.
Can Shopify Flow send automated loyalty rewards emails?
Shopify Flow can send automated loyalty rewards emails when the connected loyalty app and email setup expose the required triggers and actions. It does not independently know a customer’s points balance, reward eligibility, or expiry status.
Do automated loyalty emails need customer consent?
Automated loyalty emails need customer consent when your sending platform and local requirements classify them as marketing communication. Review subscriber status, suppression settings, and sending rules before activating a flow.
How do I stop automated rewards emails from becoming spammy?
Give each event a clear purpose, use frequency controls and suppression rules, and prioritize overlapping flows. Review complaint, unsubscribe, and delivery data regularly.
Loyalty email can run with little daily effort once the event design is sound. Build the core flows, test edge cases, and maintain a regular review routine.
Kris is the co-founder of Mage Loyalty. I spend most days talking to merchants, and making sure our customers get real results. If you run a Shopify store or Agency we should chat!


















