Can Klaviyo make the Viewed Product event segmentation more customisable?
Hello everyone.
I was wondering whether Klaviyo may consider making segment creation more customisable when custom and Klaviyo properties involving user behaviour onsite are selected. At the moment, when using properties like this to segment, the only inclusion criteria it is possible to select is “equals” (see below).
But can other options also be added to this? Say for example, “does not equal”; “contains”; “does not contain”? This would enable segments to be created for, in the example of “contains” segments, the segmentation of users according to a wider range of products, for example those with similar prefixes, or those of similar kinds. Let’s say you want to run a “Christmas” campaign, and you want to send an email to everyone who had viewed a product with “Christmas” in the product name. This would let you easily create that segment. It may be necessary for the “contains” option to work, to enable users to input values with free-text. At the moment it is a drop-down. Could the two be combined somehow?
Does not equal would work similarly as the equal segment, just flipped. This can also be useful for several kinds of campaigns.
Interested to hear your thoughts!
Ed
Page 1 / 1
Hi @ejvfscribbler,
Thanks for sharing your question with the Community!
We love to hear feedback from our users on what you would like to see more of or what you think should be changed to be more user-friendly. Thank you for your suggestions! We relay feature requests to our product engineers and evaluate what users are communicating they want to see!
I do agree the ‘contains’ feature is very helpful to have, and I’m happy to say we do have the option available when choosing ‘Product Categories’ for Segment filter with options like ‘Viewed Product’ and ‘Ordered Product’. The intention behind the Product Category section is, as you said, further customization according to the customer’s business needs, like targeting all ‘Christmas Category’ products in a segment. However, this is the only feature where the option ‘contains’ is available to filter a user’s onsite behavior.
However, if you explore your dropdown menu options outside of ‘What Someone Has (or Has Not Done)’ and click ‘Properties About Someone’ you will see that there are various options available to segment off, that would aid the Advanced Segmentation you’re looking to create like, ‘contain/doesn’t contain’, ‘is/isn’t in’, ‘equals/doesn’t equal’ and so on.
While there might not be an explicit ‘does not equal’ or ‘does not contain’ feature at this time for the Viewed Product metric, you can create the same result by changing the drop down menu to say ‘Has Viewed Product Zero Times Over All Time Equals _____’. This would confirm that this is not a product a customer has every shown interest in or interacted with in their customer history.
Thank you for sharing your thoughts and insights with the Community! Keep them coming, we love to hear it!
Best,
Taylor
Hi @ejvfscribbler,
Thanks for sharing your question with the Community!
We love to hear feedback from our users on what you would like to see more of or what you think should be changed to be more user-friendly. Thank you for your suggestions! We relay feature requests to our product engineers and evaluate what users are communicating they want to see!
I do agree the ‘contains’ feature is very helpful to have, and I’m happy to say we do have the option available when choosing ‘Product Categories’ for Segment filter with options like ‘Viewed Product’ and ‘Ordered Product’. The intention behind the Product Category section is, as you said, further customization according to the customer’s business needs, like targeting all ‘Christmas Category’ products in a segment. However, this is the only feature where the option ‘contains’ is available to filter a user’s onsite behavior.
However, if you explore your dropdown menu options outside of ‘What Someone Has (or Has Not Done)’ and click ‘Properties About Someone’ you will see that there are various options available to segment off, that would aid the Advanced Segmentation you’re looking to create like, ‘contain/doesn’t contain’, ‘is/isn’t in’, ‘equals/doesn’t equal’ and so on.
While there might not be an explicit ‘does not equal’ or ‘does not contain’ feature at this time for the Viewed Product metric, you can create the same result by changing the drop down menu to say ‘Has Viewed Product Zero Times Over All Time Equals _____’. This would confirm that this is not a product a customer has every shown interest in or interacted with in their customer history.
Thank you for sharing your thoughts and insights with the Community! Keep them coming, we love to hear it!
Best,
Taylor
While this solution is helpful, it’s not exactly what I’m after.
For example, let’s say I want to create a segment of users who have/have not viewed an array of products, rather than just one single product. The “equals” filter means I can only specify one specific product rather than an array of products that contain a common character string, since the equals filter demands an exact rather than a partial string match. Adding a “contains” option, as well as an “equals” option here, would enable the creation of segments like these.
Adding the same array of options to “What someone has done (or not done)” that are available for “Properties about someone” would help resolve this sort of problem!
This is very necessary - please have them bump this up as a feature that is greatly needed.
This would be a great feature to have and would improve Klaviyo’s segmentation a great deal for us - any updates regarding this feature? Thanks
Hi all!
Thanks for asking for an update here, would love to share more insight!
So after discussing more with product specialists, the reason why there can’t be more advanced segmentation with the Viewed Product event is because the event only passes one set of data rather than data in an array format. Therefore only the equals function can exist. For example, this isn’t the case when segmenting the Placed Order event. However, I do agree this is a limitation of the event at this time.
