> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/loyalty-and-rewards/loyalty-klaviyo-integration/redemption-emails.md).

# 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](https://docs.roadmap.so/loyalty-and-rewards/points-and-ways-to-earn/ways-to-redeem-points-overview.md), 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.

{% hint style="info" %}
Tier rewards do not fire this metric.
{% endhint %}

### Event properties

| Data point              | Event property                                            |
| ----------------------- | --------------------------------------------------------- |
| 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:

| Data point    | Event property           |
| ------------- | ------------------------ |
| 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

1. **Trigger:** `Roadmap: Loyalty Redemption Created`
2. **Conditional split** on `redemption_source`, to drop or delay redemptions made at checkout
3. **Conditional split** on `reward_type`
4. **Amount discount branch:** the code, what it is worth, and when it expires
5. **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_balance` on 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_id` is what ties a Klaviyo event back to that record when you are chasing a support question.

### Related guides

* [Ways to redeem points: overview](https://docs.roadmap.so/loyalty-and-rewards/points-and-ways-to-earn/ways-to-redeem-points-overview.md)
* [Points earned emails](https://docs.roadmap.so/loyalty-and-rewards/loyalty-klaviyo-integration/points-earned-emails.md)
* [Loyalty profile properties and email snippets](https://docs.roadmap.so/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-profile-properties-and-email-snippets.md)
* [Loyalty × Klaviyo: overview](https://docs.roadmap.so/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-klaviyo-overview.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.roadmap.so/loyalty-and-rewards/loyalty-klaviyo-integration/redemption-emails.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
