> 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/tier-earned-emails.md).

# Tier earned emails

Celebrate a customer reaching a new tier with the Roadmap: Loyalty Tier Earned metric and tier-specific emails.

Reaching a tier is the biggest moment in a member's loyalty life — the payoff for everything your tiers promised. This **essential** flow celebrates it and, more importantly, tells the customer exactly what their new status unlocks.

### Klaviyo event name

* `Roadmap: Loyalty Tier Earned` — fires when a customer reaches a tier.

### Event properties

| Data point                | Event property                                                      |
| ------------------------- | ------------------------------------------------------------------- |
| New tier                  | `new_tier` — an object with `name`, `id`, `level`                   |
| Previous tier             | `previous_tier` — same shape (`name` is empty for first-tier earns) |
| Membership expiry         | `membership_expiry`                                                 |
| Points earned this period | `points_earned_during_period`                                       |
| Customer ID               | `customer_id`                                                       |

Use `{{ event.new_tier.name }}` in subjects and copy: *You've reached {{ event.new\_tier.name }}!*

### The pre-built flow

The most sophisticated of the examples:

1. **Trigger:** `Roadmap: Loyalty Tier Earned`
2. **Filter:** email marketing consent
3. **Delay:** 1 day (weekdays) — so the celebration doesn't collide with the points earned email from the same order
4. **Conditional split** on `roadmap_loyalty_current_tier_name` *contains* *\[insert tier 2 name]* → the "Tier 2 Reached" email
5. **Second split** for *\[insert tier 3 name]* → the "Tier 3 Reached" email

Fill the *\[insert tier … name]* placeholders with your actual tier names, and duplicate the split for extra tiers. If you rename a tier in Roadmap, update the split values too.

### Strategy

* **Tier-specific emails beat a generic one.** Each email should list that tier's actual benefits — this is the moment the customer decides whether tiers matter.
* **Point at the next rung**: even in the celebration, `{{ person.roadmap_loyalty_next_tier_name }}` keeps the ladder visible.
* Pair with a [tier-reached Customer Reward](/loyalty-and-rewards/membership-tiers-and-referrals/reward-customers-for-reaching-a-tier.md) or a [tier-promotion discount code](/loyalty-and-rewards/membership-tiers-and-referrals/send-discount-codes-for-birthdays-and-tier-promotions.md) so the email has a concrete gift to deliver.

### Related guides

* [Tier demotion alerts](/loyalty-and-rewards/loyalty-klaviyo-integration/tier-demotion-alerts.md) — the other side of the tier lifecycle
* [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/tier-earned-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.