> 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/setting-up-a-klaviyo-post-purchase-review-flow-less-design-restrictions.md).
# Setting up a Klaviyo post-purchase review flow (Less design restrictions)
Build a Klaviyo post-purchase review flow with item-count trigger splits, using the Roadmap: Eligible for Review Request trigger and a Review Submitted follow-up.
Use item-count splits to create review-request emails without a dynamic product table.
#### When to use an item-count flow
Create separate review-request emails based on purchased item count. This gives you more design flexibility.
You will need more **Trigger split** steps in the flow.
Most teams cap this approach at `3` items. More review requests can reduce completion rates.
#### About the trigger: Roadmap: Eligible for Review Request
Use `Roadmap: Eligible for Review Request`, not a Shopify order trigger. It fires when fulfilled orders contain review-eligible products.
This means:
* The flow starts at fulfillment. You do not need shipping checks.
* Only customers with reviewable products enter the flow.
An order or item is excluded when:
* The customer already reviewed the product and the review limit prevents another review.
* You permanently excluded the product or variant using **Filter Products**.
The metric respects the **Review limit** in Roadmap review settings. **One review per product** excludes products the customer reviewed. **One review per product per order** supports repeat purchases.
Use **Roadmap admin → Klaviyo integration → Metrics → Filter Products** to permanently exclude products or variants. Exclude items like gift wrapping and sample swatches.
{% hint style="info" %}
If every item is excluded, the metric does not fire. `Item Count` includes only review-eligible items.
{% endhint %}
#### Set up the flow
{% stepper %}
{% step %}
**Start a new flow**
Go to **Flows** and select **Create Flow**.
Select **Build your own**. Name the flow. For example, use `Post Purchase Review Flow Item Count Example`.
{% endstep %}
{% step %}
**Set the Roadmap trigger**
Click the **Trigger** card. Under **Select a trigger → Your metrics**, choose **Roadmap: Eligible for Review Request**.
Use **Trigger filters** for order-level rules. Use **Profile filters** for customer segments, such as B2B customers.
{% hint style="info" %}
The metric already excludes ineligible products and previously reviewed items.
{% endhint %}
{% endstep %}
{% step %}
**Add a delivery delay**
Under **Timing**, drag **Time delay** below the trigger. In **Time delay details**, set **Set time delay** to `14` **Days**.
Start with `7–14` days. The trigger fires at fulfillment, so the delay begins when the order ships.
{% endstep %}
{% step %}
**Split the flow by item count (1, 2, 3+)**
Build **Trigger split** steps so each branch receives an email for its item count.
For the first split, set:
* **Metric:** `Roadmap: Eligible for Review Request`
* **Dimension:** `Item Count`
* **Operator:** `equals`
* **Value:** `1`
Add **Email #1** on the **Yes** branch.
On the first split's **No** branch, add another **Trigger split**. Set **Dimension** to `Item Count`, **Operator** to `equals`, and **Value** to `2`. Add **Email #2** on the **Yes** branch.
On the second split's **No** branch, add a final **Trigger split**. Set **Dimension** to `Item Count`, **Operator** to `is greater than`, and **Value** to `2`. Add **Email #3** on the **Yes** branch.
{% endstep %}
{% step %}
**Design each email**
Open each email action. Start with a template and customize it for `1`, `2`, or `3+` items.
Save each message before returning to the flow.
{% endstep %}
{% endstepper %}
#### Optional: add a follow-up email
The `Roadmap: Review Submitted` metric lets you stop reminders for customers who submit a review.
Repeat this setup after **Email #1**, **Email #2**, and **Email #3**:
1. Add a **Time delay** of `3` days.
2. Add a **Conditional split**.
3. Set `What someone has done (or not done) → Person has Roadmap: Review Submitted → at least once → since starting this flow`.
Let the **Yes** branch end. Add the follow-up email on the **No** branch.
{% hint style="info" %}
Keep the reminder short. The follow-up email should be shorter than the first request and act as a simple reminder to leave a review.
{% endhint %}
You can also trigger a separate thank-you flow with `Roadmap: Review Submitted`.
#### Result
* Eligible fulfilled orders enter the flow.
* `Item Count` routes customers to the correct email.
* Reviewers exit before the follow-up email.
#### Troubleshooting
**The trigger does not appear in Klaviyo**
* Confirm the Roadmap Klaviyo integration is connected.
* Select **Your metrics** in the trigger picker.
* Confirm Roadmap metrics have synced to Klaviyo.
**Customers do not enter the flow**
* Confirm the order was fulfilled.
* Confirm it contains a review-eligible product.
* Check the review limit and **Filter Products** exclusions.
**The follow-up sends after a review**
* Set the split to `at least once` and `since starting this flow`.
* Place the follow-up email only on the **No** branch.
#### Frequently asked questions
Why use the eligible-review trigger?
It adds only customers with reviewable products. Ineligible orders never enter the flow.
Can I thank customers after they submit a review?
Yes. Trigger a separate flow with \`Roadmap: Review Submitted\`.
#### Related guides
* [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)
* [How to create your email design (Less design restrictions)](/reviews/integrations/klaviyo-review-integration/how-to-create-your-email-design-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)
---
# 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/setting-up-a-klaviyo-post-purchase-review-flow-less-design-restrictions.md?ask=&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.
