> 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/review-reward-emails.md).

# Review reward emails

Thank reviewers for their points — and celebrate photo and video bonuses — with the Roadmap: Loyalty Review Reward metric.

When a review earns points, this flow closes the loop — and with photo/video bonuses, it's also your best channel for teaching customers that media reviews earn more.

### Klaviyo event name

* `Roadmap: Loyalty Review Reward` — fires when review points are awarded (on approval and publish).

### Event properties

| Data point                      | Event property                |
| ------------------------------- | ----------------------------- |
| Total points awarded            | `points_awarded`              |
| Base review points              | `base_points`                 |
| Photo bonus                     | `photo_bonus_points`          |
| Video bonus                     | `video_bonus_points`          |
| Review included a photo / video | `has_photo`, `has_video`      |
| Reviewed product                | `product_title`, `product_id` |
| Customer ID                     | `customer_id`                 |

### Recommended flow structure

There's no pre-built example for this one — a simple recipe:

1. **Trigger:** `Roadmap: Loyalty Review Reward`
2. **Email — immediately:** thank them for reviewing `{{ event.product_title }}` and confirm `{{ event.points_awarded }}` points
3. **Optional split** on `has_photo` / `has_video`:
   * Media reviewers → celebrate the bonus: *Your photo earned you an extra {{ event.photo\_bonus\_points }} points!*
   * Text-only reviewers → plant the seed: *Add a photo next time for bonus points.*

That second branch quietly grows your UGC pipeline with every review cycle.

### Strategy

* The breakdown properties (`base_points` + bonuses) answer "why did I get 250?" before the customer asks.
* Points are only awarded for verified, published reviews — the [eligibility rules](https://docs.roadmap.so/reviews/managing-reviews/review-rewards-and-limits/loyalty-points-for-reviews) explain who enters this flow.

### Related guides

* [Leave a verified review](https://docs.roadmap.so/loyalty-and-rewards/points-and-ways-to-earn/leave-a-verified-review) — the earner, including the photo/video bonus settings
* [Loyalty points for reviews](https://docs.roadmap.so/reviews/managing-reviews/review-rewards-and-limits/loyalty-points-for-reviews)


---

# 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/review-reward-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.