> 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/points-expiring-reminders.md).

# Points expiring reminders

Turn point expiry into a comeback trigger with the Roadmap: Loyalty Points Expiring metric and its Set Alert window.

This is a **retention lever**, not a courtesy note. If your program [expires points](https://docs.roadmap.so/loyalty-and-rewards/getting-started/how-to-configure-your-point-settings), the expiry deadline is one of the strongest re-purchase triggers you have — points a customer is about to lose feel more valuable than points they might earn.

### Klaviyo event name

* `Roadmap: Loyalty Points Expiring` — fires when a customer's points approach expiry.

You control how far ahead it fires: in Roadmap's Klaviyo settings, click **Set Alert** on the metric and choose the alert window.

### Event properties

| Data point                              | Event property                                                                                                     |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| Points expiring on the next expiry date | `points_expiring`                                                                                                  |
| Total points expiring                   | `total_points_expiring`                                                                                            |
| Next expiry date                        | `expiry_date`                                                                                                      |
| Days until expiry                       | `days_until_expiry`                                                                                                |
| Your configured alert window            | `alert_window_days`                                                                                                |
| Per-date breakdown                      | `expiry_breakdown` — a list of `{expiry_date, points, transaction_count}` when points expire across multiple dates |
| Current balance / tier                  | `current_point_balance`, `current_tier`                                                                            |
| Customer name                           | `customer_first_name`, `customer_last_name`                                                                        |

### Recommended flow structure

No pre-built example ships for this one — mirror the demotion recipe:

1. **Trigger:** `Roadmap: Loyalty Points Expiring`
2. **Email 1 — immediately:** `{{ event.points_expiring }} points expire on {{ event.expiry_date }}` — with the best redemption they can afford
3. **Email 2 — a few days before expiry:** final urgency, if they haven't redeemed

Gate email 2 with a flow filter on *placed order* or a profile check so redeemed customers drop out.

### Strategy

* **Name the number and the date.** "Your points are expiring" is ignorable; "258 points expire on 19 September" isn't.
* **Pair the reminder with the redemption**, not the earn: link the loyalty page or list what their balance buys right now.
* **Match the alert window to your redemption ladder.** Customers need enough runway to place an order — 30 days is a sensible default.

### Related guides

* [How to configure your point settings](https://docs.roadmap.so/loyalty-and-rewards/getting-started/how-to-configure-your-point-settings) — where expiry itself is configured
* [Tier demotion alerts](/loyalty-and-rewards/loyalty-klaviyo-integration/tier-demotion-alerts.md) — the same play for tier status
* [Loyalty profile properties and email snippets](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-profile-properties-and-email-snippets.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/points-expiring-reminders.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.