Hey there @Frank ,

Thanks for writing in! Hope to provide some info with what you’re experiencing with segment definitions and the placed order metric.

In short, there is no method to check condition of a customer who has ordered multiple quantities of specific items but also in different orders over all time. 

The logic for segmentation like this gets tricky because it changes depending on if you use placed order = 2 or placed order = 2 where item = X.

If you use the former, the number 2 is looking at the number of total orders that qualify for the segment. In other words, only if two discrete orders are placed will users qualify for the segment.

If you use the latter, as long as item X was ordered twice, it doesn’t matter whether it comes from the same order or multiple orders. In other words, it’s order “agnostic” which goes against what you’re stipulating. 

You can use them in combination to specify Placed order = 2 AND placed order = 2 where item = X but that will “lock in” the number of orders and the item quantity. However, Klaviyo still “won’t care” whether that item was ordered twice in the same order or once in one order and another time in another order. So to summarize again, we cannot segment to isolate the number of times the item comes up per order like you said initially.

Hope this helped!
Alex

Hey @alex.hong,

thanks for sharing your insights. Yes thats why I struggled to build the Segment the way i wanted.

Looking for another solution then.

Purpose of the Segment was more to check if a defined product is ordered again and again or if it was a one time thing.

Thanks again Alex.

My pleasure @Frank,

Glad I could offer some insight and help with your idea. I would consider seeing if your native storefront has any method to track this data as well. 

Have a good day :)
Alex