> 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/membership-anniversary-emails.md).

# Membership anniversary emails

Mark each year of membership with the Roadmap: Loyalty Anniversary Points Reward metric, and say something different at year one and year five.

An anniversary email is the one send that is purely about the relationship rather than the product. This flow delivers the [anniversary points](https://docs.roadmap.so/loyalty-and-rewards/points-and-ways-to-earn/award-points-on-membership-anniversaries.md) your earner awards, and lets you treat a one-year member differently from a five-year one.

### Klaviyo event name

* `Roadmap: Loyalty Anniversary Points Reward` — fires when anniversary points are awarded.

It fires once per customer per year, on the anniversary of their **member since** date, early in the morning in your store's timezone.

{% hint style="info" %}
Customers inside a B2B company program do not fire this metric. See [B2B loyalty and Klaviyo](https://docs.roadmap.so/loyalty-and-rewards/b2b-loyalty/b2b-loyalty-and-klaviyo.md).
{% endhint %}

### Event properties

Same shape as points earned, with anniversary specifics:

| Data point              | Event property                                    |
| ----------------------- | ------------------------------------------------- |
| Points awarded          | `points_earned`                                   |
| Method                  | `points_earned_method` = `membership-anniversary` |
| Detail                  | `details` = *3 year membership anniversary*       |
| Transaction date / time | `transaction_date`, `transaction_time`            |
| Customer ID             | `customer_id`                                     |
| Years of membership     | `anniversary_year`                                |
| Join date               | `member_since`                                    |
| Anniversary date        | `anniversary_date`                                |
| Tier at the time        | `current_tier`                                    |

{% hint style="info" %}
`anniversary_year` is the one to build on. It is a plain number, so a conditional split on it is what stops every member getting the same email every year for a decade.
{% endhint %}

`anniversary_date` is the anniversary itself. `transaction_date` is when the points were written, so the two can differ when the award runs either side of midnight in your timezone. Use `anniversary_date` in the copy.

### A recommended flow

1. **Trigger:** `Roadmap: Loyalty Anniversary Points Reward`
2. **Delay:** until a civil hour in the customer's own timezone, the same way the [birthday flow](https://docs.roadmap.so/loyalty-and-rewards/loyalty-klaviyo-integration/birthday-points-emails.md) does it
3. **Conditional split** on `anniversary_year`
4. **Email per branch:** at minimum a year-one email and an everything-else email

### Strategy

* **Lead with the number.** "Three years with us" is the whole email. The points are the gift, the year is the reason.
* **Pair the award with the balance.** Their anniversary points plus everything saved up is a bigger, more spendable number than the award alone. Pull the balance from [profile properties](https://docs.roadmap.so/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-profile-properties-and-email-snippets.md).
* **Keep it away from the birthday send.** Both are "here are some points because we like you" emails. If a customer's join date and birthday land in the same fortnight, one of them should carry the occasion and the other should stay quiet.
* **If your earner is tier-scoped,** only eligible tiers fire the metric at all, so the flow does not need its own tier filter. `current_tier` is still useful for changing the tone.

### Related guides

* [Award points on membership anniversaries](https://docs.roadmap.so/loyalty-and-rewards/points-and-ways-to-earn/award-points-on-membership-anniversaries.md)
* [Birthday points emails](https://docs.roadmap.so/loyalty-and-rewards/loyalty-klaviyo-integration/birthday-points-emails.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)


---

# 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/membership-anniversary-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.
