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

# Points earned emails

Confirm every points earn with the Roadmap: Loyalty Points Earned metric — the highest-volume loyalty email and the heartbeat of the program.

The points earned email is an **essential** flow and the highest-volume one — it fires on every earn. Done well, it's the heartbeat of your program: a small, consistent reminder that shopping with you pays.

### Klaviyo event name

* `Roadmap: Loyalty Points Earned` — fires when any earning rule awards points.

### Event properties

| Data point                  | Event property                                    |
| --------------------------- | ------------------------------------------------- |
| Points earned in this event | `points_earned`                                   |
| How they were earned        | `points_earned_method` (e.g. `place-order`)       |
| Human-readable detail       | `details` (e.g. *Points awarded for Order #1080*) |
| Order/reference ID          | `reference_id`                                    |
| Transaction date / time     | `transaction_date`, `transaction_time`            |
| Customer ID                 | `customer_id`                                     |

### The pre-built flow

1. **Trigger:** `Roadmap: Loyalty Points Earned`
2. **Email — immediately:** "Thanks for choosing us"

The example email deliberately uses **profile lookups** for the balance rather than event values — so the numbers are current even if the email is opened days later:

```liquid
You just earned {{ event.points_earned|default:'' }} points — {{ event.details|default:'' }}.
Your balance is now {{ person.roadmap_loyalty_total_points|default:'' }} points.
```

### Strategy

* **Keep it light.** This email fires often — one clear number, one redemption nudge, done.
* **Filter small earns if volume gets noisy.** Add a flow filter on `points_earned` (e.g. greater than 50) so a small puchase doesn't trigger the flow.
* **Always show the next goal**: `{{ person.roadmap_loyalty_next_tier_points|default:'' }} points to {{ person.roadmap_loyalty_next_tier_name|default:'the next tier' }}` turns a receipt into a reason to come back.

### Related guides

* [Loyalty × Klaviyo: overview](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-klaviyo-overview.md)
* [Loyalty profile properties and email snippets](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-profile-properties-and-email-snippets.md)
* [Tier earned emails](/loyalty-and-rewards/loyalty-klaviyo-integration/tier-earned-emails.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.