> 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/getting-started/klaviyo-integration.md).

# Klaviyo integration

Connect Roadmap to Klaviyo once and every product syncs: loyalty, subscription, and review metrics for flows, profile properties for segments, and controls for bundles.

Connect Roadmap to Klaviyo once and everything syncs automatically: **metrics** fire into Klaviyo as events happen (for triggering flows), and **profile properties** keep each customer's loyalty, subscription, and review standing written to their Klaviyo profile (for segments, splits, and email content).

### Where it lives

In the Roadmap app, go to **Settings → Klaviyo Integration**. Three areas:

* **Klaviyo Profile**: the profile properties Roadmap writes to customers, with a **Manual Sync** button.
* **Klaviyo Metrics**: the event metrics Roadmap fires, with per-metric controls and a **Sync Metrics** button.
* **Connection Settings**: manage your Klaviyo API keys.

### Connect your Klaviyo account

Add your Klaviyo API key under **Connection Settings** (both sync pages also show a banner linking to it until a key is saved). For generating the key in Klaviyo, follow [How to integrate Roadmap with Klaviyo](https://docs.roadmap.so/reviews/integrations/klaviyo-review-integration/how-to-integrate-roadmap-with-klaviyo): it's one setup shared by every Roadmap product.

### Klaviyo Profile: the properties

Properties sync automatically and update when an order is placed or points and membership data change. **Manual Sync** pushes everything on demand. Three tabs:

* **Loyalty**: 15 properties covering points balance, tiers, expiry dates, and spend. Full list and email snippets: [Loyalty profile properties and email snippets](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-profile-properties-and-email-snippets.md).
* **Subscriptions**:

| Data point                   | Klaviyo property                              |
| ---------------------------- | --------------------------------------------- |
| Has active subscription      | `person.roadmap_has_active_subscription`      |
| Lifetime subscription orders | `person.roadmap_lifetime_subscription_orders` |
| Has paused subscription      | `person.roadmap_has_paused_subscription`      |

* **Reviews**:

| Data point           | Klaviyo property                      |
| -------------------- | ------------------------------------- |
| Latest review rating | `person.roadmap_latest_review_rating` |

### Klaviyo Metrics: the events

Metrics sync to Klaviyo automatically when the related event occurs. After install, click **Sync Metrics** once so they appear in Klaviyo for the first time. Three tabs:

* **Loyalty**: 12 metrics from welcome through referrals, some with their own controls (**Set Alert** on Points Expiring and Tier Demotion Alert, **Set Time / Send Now / Enabled** on Monthly Update, **Filter Products** on the order metrics). Full guide: [Loyalty × Klaviyo: overview](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-klaviyo-overview.md).
* **Subscriptions**: Subscription created, canceled, paused, failed, payment failed, and Upcoming order.
* **Reviews**: Eligible for Review Request (fires when an order containing eligible products for review is fulfilled), Review Submitted, Review reply, and Question answer, each with **Filter Products** to scope which products fire it. **Sync reviews to klaviyo catalog** pushes your reviews to Klaviyo for use in emails: see the [Klaviyo Review Integration guides](https://docs.roadmap.so/reviews/integrations/klaviyo-review-integration).

To keep utility products like gift wrapping out of your events, use **Filter Products**, per metric or across all metrics at once: see [Excluding products from Klaviyo metrics (Filter Products)](/getting-started/klaviyo-integration/excluding-products-from-klaviyo-metrics-filter-products.md).

### Bundle Metrics

**Show bundles as a single product in Roadmap metrics**: when enabled, the *Placed Order (Roadmap)* and *Eligible for a Roadmap review* metrics use the bundle's product ID and title instead of the individual constituent products. Turn this on if your flows should treat a bundle as one item.

### Where each product's guides live

* **Loyalty**: [Loyalty × Klaviyo: overview](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-klaviyo-overview.md) and the per-flow guides alongside it.
* **Reviews**: [Klaviyo Review Integration](https://docs.roadmap.so/reviews/integrations/klaviyo-review-integration): review request flows, review snippets in emails, and conditional splits.
* **Subscriptions**: the subscription metrics above power flows like the [Klaviyo win-back flow for cancelled subscriptions](/subscriptions/subscriptions-klaviyo-integration/klaviyo-win-back-flow-for-cancelled-subscriptions.md).
* **Forms**: storefront forms can send submissions to Klaviyo, configured per form in the form's settings: see [Forms](https://docs.roadmap.so/forms).


---

# 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/getting-started/klaviyo-integration.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.