> 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/excluding-products-from-klaviyo-metrics-filter-products.md).

# Excluding products from Klaviyo metrics (Filter Products)

Stop gift wrapping, sample swatches, and other utility products from appearing in your Klaviyo flow emails by excluding them from Roadmap's metric event properties, per metric or across all metrics at

Roadmap's order-based metrics carry the order's products in their event properties, which is what lets a Klaviyo flow email show what the customer bought. Utility items pollute that personalisation: nobody wants their post-purchase email leading with the gift wrapping. **Filter Products** excludes chosen products or variants from a metric's event properties, and you can apply it to a single metric or to every Roadmap metric at once.

### Where to find it

In the Roadmap app, go to **Settings → Klaviyo Integration → Klaviyo Metrics**. There are two places to filter:

* **Per metric**: metrics that support filtering show a **Filter Products** button in the **Actions** column. On the **Loyalty** tab that's the two order metrics, **Placed Order (Roadmap)** and **Roadmap: Checkout Started**. On the **Reviews** tab, all four review metrics have one.
* **All metrics**: the **Filter Products** button at the top of the page (next to **Sync Metrics**) opens *Filter Products - All Metrics*. Exclusions saved here apply to **every Roadmap metric** across the Loyalty, Subscriptions, and Reviews tabs.

Both open a similar modal: an exclusion list for products and one for variants.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2Fkd82otug9hqNBTCfGkUt%2FScreenshot%202026-09-07%20at%2012.07.01%E2%80%AFPM.png?alt=media&amp;token=cbd5b54b-247e-44a6-ba02-314bb83af462" alt=""><figcaption></figcaption></figure>

### Exclude products or variants

{% stepper %}
{% step %}

#### Open the filter

Click **Filter Products** next to a metric (the modal is titled with that metric's name, for example *Filter Products - Placed Order (Roadmap)*), or the page-level **Filter Products** button to filter *All Metrics*.
{% endstep %}

{% step %}

#### Select products to exclude in metric properties

Search for a product or click **Browse**. Each excluded product appears in the list; remove one using the **X.**
{% endstep %}

{% step %}

#### Select variants to exclude in metric properties

Use the second list when only certain variants should be excluded, for example a sample-size variant of a product you otherwise want in emails.
{% endstep %}

{% step %}

#### Save

Click **Save**. From now on, the filtered metrics leave the excluded items out of their event properties.
{% endstep %}
{% endstepper %}

### What filtering changes

* Excluded products and variants stop appearing in the metric's **event properties**: the product titles, ids, and images your flow emails and product blocks read.
* **An order containing only excluded products doesn't fire the metric at all.** A gift-wrapping-only order, for example, triggers no *Placed Order (Roadmap)* event and therefore no flow.
* A per-metric filter applies only to that metric. Use the **All Metrics** filter to exclude a product from every Roadmap metric in one step.
* Good candidates: gift wrapping, sample swatches, shipping protection, and free-gift products.

{% hint style="info" %}
Filter Products only changes what Roadmap sends to Klaviyo. It has no effect on loyalty point earning, order processing, or anything on the storefront.
{% endhint %}

### Filtering review requests

The most common use of Filter Products is on the **Reviews** tab's **Roadmap: Eligible for Review Request** metric. Excluding your utility products there means a fulfilled order of gift wrapping or sample swatches never asks the customer to review them, and they stay out of the review request email's product list. **Review Submitted**, **Review reply**, and **Question answer** can be filtered the same way. See the [Klaviyo Review Integration guides](https://docs.roadmap.so/reviews/integrations/klaviyo-review-integration) for the flows these metrics power.

### Related guides

* [Klaviyo integration](/getting-started/klaviyo-integration.md): the full tour of metrics, profile properties, and Bundle Metrics (which controls whether bundles appear as one product or their components)
* [Loyalty × Klaviyo: overview](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-klaviyo-overview.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/getting-started/klaviyo-integration/excluding-products-from-klaviyo-metrics-filter-products.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.
