Create segments using custom properties with AND-OR logic

Hi @ageorgiev 

Thank you for posting your question in the community. The ability to create these segments is possible, but it all depends on how the data is coming into Klaviyo. Pending on the data type you may need to switch the data type in the segment builder.

See if that gives you the logic you are looking for.

@In the Inbox 

Hi @JessFosnough,

Yes, I can create two segments but this means I have to duplicate all further settings based on these segments. For example, if I want to create a flow for the profiles that match the desired condition (using trigger “Added to segment”) I would need to create two segments, two flows and duplicate all steps and branching in both flows. This seems very odd and error-prone to me.

Hi @ageorgiev! This is an interesting challenge you’ve run into - thanks @kaila.lawrence for the tag. 

First, @JessFosnough is correctly identifying the current limitation of Klaviyo’s segment builder. When setting up segment conditions, the only option right now is to use AND as an outer join, and OR as an inner join.

So here’s a quick confirmation of how you’d make this work for campaign sending.

As @JessFosnough pointed out, you’ll need two segments to grab each custom property pair.

IF you’re wanting to target both groups of people for one campaign, your recipients would look like [Include Segment 1: Property 1 = “AAA” AND Property 2 = “BBB” AND Segment 2: Property 3 = “CCC” AND Property 4 = “DDD” ]

Then there’d likely be scenarios where you’d send a campaign to only Segment 1 and EXCLUDE Segment 2 from the recipients, or vice versa.

For flows, here’s how to make it most efficient and prevent logic errors.

If we zoom out a little, that might help you find the best solution for what you’re trying to build in Klaviyo... If you’re willing to share more info about what types of properties you’re creating, and what your intended values are, I’m happy to give you more specific recommendations!

Generally, I agree with your desire to minimize flow triggers and conditional splits that feel like duplicates of another flow. So how can we best help you simplify the plans for your flow logic, and make it the most functional iteration possible?

For example, if Property 1 and Property 2 correspond to a product interest, is there a way to combine those into a broader category? AND is there existing product data from Shopify (or your ecom platform if not Shopify) that can be leveraged and remove the need for so many custom properties?

Then, after we consider that, maybe there’s a way to apply a similar consolidation to people with Property 3 and Property 4 on their profile…

I’ll keep an eye out for more details from you!

Warmly,

Gabrielle