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.

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

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.

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.

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.

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:
Trigger the flow with Placed Order (Roadmap).
Use Filter Products in Roadmap for product-level cleanup.
Use Trigger filters for order-level exclusions.
Use Profile filters for customer-level exclusions and exit rules.
This keeps the flow logic clean and the email content relevant.
Related guides
Last updated
