> 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/reviews/integrations/klaviyo-review-integration/introduction-to-klaviyo-review-flow-setup.md).

# Introduction to Klaviyo review flow setup

### Why automate review requests after purchase?

The most reliable way to collect reviews is to automate requests after a customer buys. Roadmap integrates with Klaviyo so you can trigger review-request emails to verified buyers—without manual follow-ups.

* **Verified buyers only:** Reviews collected from this flow are marked as **Verified Purchase**.
* **Consistent capture:** Every order can trigger the same high-quality workflow.
* **Personalized and scalable:** Use Klaviyo to personalize timing, subject lines, and product content.

If you don’t see Roadmap’s order metric in Klaviyo, confirm the Roadmap ↔ Klaviyo connection is active, then try again after new orders are placed.

### Use this trigger metric

When building a review-request flow, use the Roadmap order metric:

* **Metric:** `Placed Order (Roadmap)`

Why only use `Placed Order (Roadmap)`? Roadmap’s metric includes the specific event properties used in our Klaviyo walkthroughs and supports verified review collection (via the order ID included in the review link).

### Recommended flow structure

At a minimum, your Klaviyo flow should follow this structure:

* **Trigger:** When someone **Placed Order (Roadmap)**
* **Timing:** Add a **Time delay** (commonly 7–14 days; many stores use 5–10 days after delivery)
* **Action:** Send an **Email** asking for a review

If you’re unsure about timing, start with **7–14 days**. The Roadmap walkthrough example uses a **Wait 14 days** step in Klaviyo.

### Create the review request flow in Klaviyo

{% stepper %}
{% step %}

#### Create a new flow

In Klaviyo, go to **Flows** in the left navigation and open **Create Flow**.

On **Create Flow**, select **Build your own** to create a flow manually.
{% endstep %}

{% step %}

#### Set the trigger to Placed Order (Roadmap)

In the flow builder, click the **Trigger** card ( **Select a trigger**).

In the right panel ( **Select a trigger**), open **Your metrics** and select **Placed Order (Roadmap)**.

When the dialog **Confirm your trigger selection** appears, click **Confirm and save**.
{% endstep %}

{% step %}

#### Add a delivery delay

From the left sidebar, under **Timing**, drag **Time delay** under the trigger.

Click the delay step to open **Time delay details**, set **Set time delay** (for example, `14` **Days**), then click **Save**.
{% endstep %}

{% step %}

#### Add the review request email

From the left sidebar, under **Actions**, drag **Email** under your delay step.

Write your review-request message in Klaviyo’s email editor and include your Roadmap review form link (see next section).
{% endstep %}
{% endstepper %}

### Set up the review form landing page (required)

Your email should send customers to a Shopify page that contains the **Roadmap** **Reviews Form** section.

Roadmap’s recommended setup is: create a **page template** in the Shopify theme editor, add **Apps → Reviews Form** (Roadmap), then create a page in **Online Store → Pages** and assign that template.

Use [How to set up your review form landing page for your Klaviyo flow](/reviews/integrations/klaviyo-review-integration/how-to-set-up-your-review-form-landing-page-for-your-klaviyo-flow.md) for the full setup.

### Best-practice conditions to consider

### Delay timing

* Send the first email after a realistic delivery window (common: **5–10 days after delivery**).
* If you can’t reliably calculate delivery date, use a purchase-based delay (common: **7–14 days**).

### Limit how often a customer receives the flow

In Klaviyo, use flow filters or splits to avoid over-messaging repeat customers.

### Rewards / incentives (optional)

If you offer an incentive, keep it compliant with your local laws and platform policies, and make sure it doesn’t encourage misleading reviews.

### Setting up reminder emails

You can increase completion rates by adding follow-ups if the customer hasn’t left a review yet.

* Add a reminder delay\
  After your first review request email, add another **Time delay** (for example, **7–10 days**).
* Add a second email\
  Add another **Email** step and adjust the copy (short, friendly reminder).
* (Recommended) Add logic so reminders stop once a review is submitted\
  Use a **Conditional split** in Klaviyo to check for your “review submitted” signal (based on how you track it in your account), so customers who already reviewed don’t continue receiving reminders.

Common cadence: **1st request** → 5–10 days after delivery, then **1st reminder** → 7–10 days later if still no review.

### Other ways to collect reviews

* **On-site review forms:** Customers can leave reviews directly from product pages (PDPs) and through your Roadmap review form page.

### Common questions

<details>

<summary>Can I send review requests manually?</summary>

Yes—but automated Klaviyo flows are typically much more effective and consistent.

</details>

<details>

<summary>Do customers need to log in to leave a review?</summary>

No. Roadmap verifies the review using the order ID included in the review link from your Klaviyo email.

</details>

<details>

<summary>Can I request reviews for subscription refills?</summary>

Yes. Any order that triggers `Placed Order (Roadmap)` can enter your review request flow.

</details>

<details>

<summary>Can I customize the review request email design?</summary>

Yes. Emails are built in Klaviyo, so you have full control over design, branding, and copy.

</details>

### Related walkthroughs

* [Setting up a Klaviyo post-purchase review flow (Dynamic table styled email)](/reviews/integrations/klaviyo-review-integration/setting-up-a-klaviyo-post-purchase-review-flow-dynamic-table-styled-email.md)
* [Setting up a Klaviyo post-purchase review flow (Less design restrictions)](/reviews/integrations/klaviyo-review-integration/setting-up-a-klaviyo-post-purchase-review-flow-less-design-restrictions.md)
* [How to set up your review form landing page for your Klaviyo flow](/reviews/integrations/klaviyo-review-integration/how-to-set-up-your-review-form-landing-page-for-your-klaviyo-flow.md)
* [How to create your email design (Dynamic Table)](/reviews/integrations/klaviyo-review-integration/how-to-create-your-email-design-dynamic-table.md)
* [How to create your email design (Less design restrictions)](/reviews/integrations/klaviyo-review-integration/how-to-create-your-email-design-less-design-restrictions.md)

### Summary

* Connect Roadmap to Klaviyo and use `Placed Order (Roadmap)` as the flow trigger.
* Add a **Time delay** so customers have time to receive and try the product.
* Send customers to a dedicated Shopify page containing the **Review Form**.
* Add reminder emails (with logic to stop reminders once a review is submitted).


---

# 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/reviews/integrations/klaviyo-review-integration/introduction-to-klaviyo-review-flow-setup.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.