> 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/filter-the-placed-order-metric-for-review-capture.md).

# Filter the Placed Order metric for review capture

Exclude products, collections, or customers from your Klaviyo review flow using trigger filters, profile filters, and Roadmap product filters.

Use this when you want tighter control over who enters your review request flow.

This is especially useful when some orders should not generate review emails, or when some products should never appear in review capture.

### Best way to exclude products from review emails

If you want to stop specific products appearing in your review email data, use Roadmap's product filter inside the metric setup.

This is the best option when your email uses event item data.

{% hint style="info" %}
**Filter Products** is available on every Roadmap metric, including **Roadmap: Eligible for Review Request**, and can be applied to all metrics at once from the top of the Klaviyo Metrics page. Full guide: [Excluding products from Klaviyo metrics (Filter Products)](/getting-started/klaviyo-integration/excluding-products-from-klaviyo-metrics-filter-products.md).
{% endhint %}

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FmEe4CnSZlEcrrLqIbEle%2FScreenshot%202026-04-24%20at%2010.07.27%E2%80%AFAM.png?alt=media&#x26;token=140fa56e-0ff7-4cd6-a28d-1336d7f56c31" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}

#### Open your Klaviyo metric settings in Roadmap

In **Roadmap**, open **Klaviyo Integration**.

Then open **Klaviyo Metrics**.
{% endstep %}

{% step %}

#### Open the Placed Order metric

Select **Placed Order (Roadmap)**.

This is the metric used for review request flows.
{% endstep %}

{% step %}

#### Use Filter Products

Open **Filter Products**.

Select the products you want to exclude from review capture.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FYNWbcWznhJG4bmdn6HJB%2FScreenshot%202026-04-24%20at%2010.08.00%E2%80%AFAM.png?alt=media&#x26;token=946bcae1-a8c9-4e5c-9ec8-56aff381d0dd" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Save and test the event output

Place a test order with both included and excluded products.

If an order contains three items and one is excluded, the metric data sent into Klaviyo only includes the remaining eligible items.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Excluded products are removed before the metric data is used in the flow.

If an order contains only excluded products, it will not trigger the flow.
{% endhint %}

### Why this is the best option first

This method filters products before the event data is used in Klaviyo.

That matters when your email pulls in line item data.

For example, if an order contains three items and one is excluded, the metric payload only includes the two eligible items.

This keeps the review email focused on products you still want to collect reviews for.

### How Klaviyo's native filters work

At the top of a Klaviyo flow, you can apply two filter types:

* **Trigger filters**
* **Profile filters**

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FoBKjbAISM5WQZIlNx5ZM%2FScreenshot%202026-04-24%20at%2010.04.38%E2%80%AFAM.png?alt=media&#x26;token=97b0ed29-fb16-481e-9e36-0ee34ace1e87" alt="" width="290"><figcaption></figcaption></figure>

When your flow uses **Placed Order (Roadmap)**, the trigger event includes event property data synced into Klaviyo.

That data behaves much like native Shopify/Klaviyo metrics, but it can also include Roadmap-specific properties such as order IDs and product IDs.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FKQTTrokGkNw3su0oNyr0%2FScreenshot%202026-04-24%20at%2010.11.19%E2%80%AFAM.png?alt=media&#x26;token=e9367add-9e3a-44bc-a4c5-fd9c8b9c70c8" alt="" width="375"><figcaption></figcaption></figure>

### Use trigger filters for event-level rules

**Trigger filters** evaluate the order event that started the flow.

Use them when the rule depends on the order itself.

Common examples:

* exclude sample products from review capture
* exclude specific collections
* exclude specific items or product IDs

Use this when the full order should be blocked from entering the flow.

If the condition matches, the customer does not enter the flow.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FdUMcT367F3iUnUn3pR6S%2FScreenshot%202026-04-24%20at%2010.04.55%E2%80%AFAM.png?alt=media&#x26;token=3f8f4cd9-48f1-48b3-8355-73b66d996dc8" alt="" width="375"><figcaption></figcaption></figure>

### Use profile filters for customer-level rules

**Profile filters** evaluate the customer profile, not the order event.

Use them when the rule depends on the person receiving the email.

Common examples:

* stop recent reviewers entering the flow
* exclude VIP, wholesale, or staff profiles
* remove customers once they meet an exit condition

Klaviyo keeps checking profile filters throughout the flow.

That means someone can exit later, even after they have already entered.

For example, if a customer submits a review before a reminder email is sent, a profile filter can remove them from the rest of the flow.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FGThyJrDI6ZYYLApTGQJC%2FScreenshot%202026-04-24%20at%2010.05.08%E2%80%AFAM.png?alt=media&#x26;token=6d71639c-b0fc-4318-b8a8-2d77dec4d28b" alt="" width="375"><figcaption></figcaption></figure>

### Trigger filters vs product filtering

These controls solve different problems.

**Trigger filters** decide whether the order should enter the flow.

**Filter Products** decides which products remain in the metric payload.

If you only use a trigger filter, excluded items can still cause issues when your email uses event-level product data.

If you need the email to show only reviewable items, filter the products in Roadmap.

### Recommended setup

For most review flows, use this approach:

1. Trigger the flow with **Placed Order (Roadmap)**.
2. Use **Filter Products** in Roadmap for product-level cleanup.
3. Use **Trigger filters** for order-level exclusions.
4. Use **Profile filters** for customer-level exclusions and exit rules.

This keeps the flow logic clean and the email content relevant.

### Related guides

* [Excluding products from Klaviyo metrics (Filter Products)](/getting-started/klaviyo-integration/excluding-products-from-klaviyo-metrics-filter-products.md)
* [Introduction to Klaviyo review flow setup](/reviews/integrations/klaviyo-review-integration/introduction-to-klaviyo-review-flow-setup.md)
* [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)
* [Creating conditional split using loyalty & review properties](/reviews/integrations/klaviyo-review-integration/creating-conditional-split-using-loyalty-and-review-properties.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/filter-the-placed-order-metric-for-review-capture.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.