> 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/referral-completed-emails.md).

# Referral completed emails

Thank the referrer when their friend's first order lands, with the Roadmap: Loyalty Referral Complete metric.

When a referred friend places their first order, this flow thanks the **referrer** — and its real job is to prompt the *next* share. Referrers who get thanked refer again.

### Klaviyo event name

* `Roadmap: Loyalty Referral Complete` — fires for the **referrer** when their friend's first order lands.

### Event properties

| Data point                                           | Event property                      |
| ---------------------------------------------------- | ----------------------------------- |
| The referrer's reward                                | `reward_name` (e.g. *1,000 Points*) |
| Friend's order value                                 | `order_value`                       |
| Friend's order number / ID                           | `order_number`, `order_id`          |
| Referrer ID / email                                  | `referrer_id`, `referrer_email`     |
| Coupon code (when the referrer reward is a discount) | `coupon_code`                       |
| Customer ID                                          | `customer_id`                       |

### The pre-built flow

1. **Trigger:** `Roadmap: Loyalty Referral Complete`
2. **Email — immediately:** "Thanks for spreading the word {{ person.first\_name|default:'You' }}!" — confirming `{{ event.reward_name }}` and showing their updated balance via `{{ person.roadmap_loyalty_total_points|default:'' }}`

### Strategy

* **Close the loop fast.** The reward confirmation is the payoff moment — don't batch or delay it.
* **Ask for the next referral in the same email.** The customer just experienced the program working; that's the moment to hand them their link again.
* Show the updated points balance from profile properties rather than event data, so it's always current.

### Related guides

* [Referral invitation emails](/loyalty-and-rewards/loyalty-klaviyo-integration/referral-invitation-emails.md)
* [Manage referrals](/loyalty-and-rewards/membership-tiers-and-referrals/manage-referrals.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/referral-completed-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.