Redemption emails
Send the reward the moment a customer spends points, using the Roadmap: Loyalty Redemption Created metric, with a different email per reward type.
The moment a customer spends points is the moment they are most engaged with your program. This flow gets the reward into their inbox, so a code does not die with a closed tab.
Klaviyo event name
Roadmap: Loyalty Redemption Created— fires when a customer spends points on a way to redeem, at the step that generates their discount.
Both reward types fire it: an Amount Discount, whether fixed or percentage off, and a Product Redemption, where points buy a whole product.
Event properties
Points spent
points_spent
Balance after redeeming
current_point_balance
Reward name
reward_name
Reward type
reward_type = amount_discount or product_redemption
Discount type
discount_type = fixed_amount or percentage
Discount value
discount_value
Currency
discount_currency
Code
coupon_code
Code expiry
coupon_expiry
Where they redeemed
redemption_source
Transaction date / time
transaction_date, transaction_time
Redemption ID
redemption_id
Product redemptions carry the claimed product as well:
Product title
redeemed_product_title
Variant title
redeemed_variant_title
Product ID
redeemed_product_id
Variant ID
redeemed_variant_id
Product image
redeemed_product_image
discount_value is a number and discount_currency is separate, so build the currency symbol in your template. reward_name is the ready-to-print version if you would rather not.
Two properties worth understanding
current_point_balance is the balance after the redemption. Elsewhere we tell you to read balances from profile properties so the number stays current. Here, use the event value: the metric fires the instant points come off, which can be ahead of the profile sync.
redemption_source tells you where the customer redeemed from. Somebody redeeming at checkout already has the code applied and is mid-purchase, so an email at that moment pulls them out of a cart they were about to convert. Somebody redeeming from the loyalty page is browsing, and that is where the email earns its keep. Split on this property to suppress or delay the checkout case.
A recommended flow
Trigger:
Roadmap: Loyalty Redemption CreatedConditional split on
redemption_source, to drop or delay redemptions made at checkoutConditional split on
reward_typeAmount discount branch: the code, what it is worth, and when it expires
Product redemption branch: the product image and title, and how to claim it
The two reward types genuinely need different emails. A discount code says "use this at checkout". A product redemption has already been chosen, so the email has to say how it reaches them.
Strategy
Put the code where a thumb can reach it. This email's whole job is retrieval. Big code, one button, no preamble.
Say what is left.
current_point_balanceon a redemption email turns one reward into the start of the next one.Use the expiry if you set one. A code with a date attached converts harder than one without.
Watch for codes that never get used. Redemptions that sit unspent are worth a reminder, and are visible in the admin's unused loyalty coupons.
redemption_idis what ties a Klaviyo event back to that record when you are chasing a support question.
Related guides
Last updated