Solved

Conditional Split Specific Email Open

P
Rank
Badge +2

I'm looking to add a conditional split to one of my flows.

 

Essentially, we are sending 4 emails over 1 month. After 30 days they hit the conditional split. I'm looking to have anyone who has opened one of those 4 emails continue on the flow and anyone who has NOT opened one of those 4 emails to be split onto a separate branch.

 

However, when I go to make the trigger, it is just a generic "Opened Email at least once in the last 30 days". 

 

There is a filter option, but when I select it and go to choose my property it says there are no items on this list.

 

I found this article on segments where it's mentioned that you can build segments off who opened a specific email. However, I don't know how to do this.

 

https://help.klaviyo.com/hc/en-us/articles/115005061447-Introduction-to-Segments-in-Klaviyo#what-is-a-segment-1

 

Can you help?

icon

Best answer by elisegaines 1 June 2021, 21:00

View original

7 replies

E
Rank
Userlevel 5
Badge +23

Hey @Peyton! It sounds like you’re on the right track -- using that additional filters option is the best way to specify which emails the split should look at. Your conditional split rule should look like this, but with the name of your flow in the blank: 

That said, you won’t be able to select the name of your flow in that field until at least one person has received and opened a message from that flow. This is because the options populate based on past activity. So, as soon as someone opens a message from that flow, you’ll be able to build the split you’re envisioning! 

P
Rank
Badge +2

“you won’t be able to select the name of your flow in that field until at least one person has received and opened a message from that flow. This is because the options populate based on past activity.”

 

This is the EXACT response I needed. Thank you so much! Glad to know I was in the right place and just need to be patient. I’ll obviously need to wait to test this out, but since it’s a 30 day flow, I should simply be able to wait for one entry and then establish the split conditions throughout.

 

Thank you,

Peyton

P
Rank
Badge +2

Apologies, quick follow up, what do you put in the equals box? Or should that be left empty?

 

NVM --- I now understand. 

 

The drop down needs to say flow and the name of the flow goes in “Equals”

I can’t delete this, so please disregard.

D
Rank
Badge

Does anyone know if it’s possible to specify a specific email inside a flow rather than the whole flow that can contain multiple emails?

Dov
Userlevel 7
Badge +61

Hi @dcrobertshaw,

Thank you for your question.

Yes this is entirely possible! In your filter, select “Message” or “Subject”. Just keep in mind somebody would have to have performed the action for that email i.e. Opened that email (in the example below) in order for the message name or subject line to appear as an option.

Thanks for being a member of our community.

DD
H
Rank

What do I put in the message field? Is it the specific email name? ...like “Email #2”. Would it only scan for the message name in that particular flow? Because some of the other emails in other flows may have the same name.

Dov
Userlevel 7
Badge +61

Hi @Harcharan,

Thanks for sharing this with us.

It would not exclusively scan for message names in that flow, it would indeed scan for message names across all flows. If you encounter the issue of having duplicate messages names, you can resolve by using the message id in the “equals” field. The message id is an alphanumeric code which is unique to each flow email. Our friend at Retention explains how to use the message ID in more detail in the thread below:

The same idea can be used in your conditional split filter.

Thanks for being a community member

DD

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Links & Resources

Platforms

Partners

Useful Things

About

  • Terms and Privacy
    © 2022 Klaviyo All rights reserved. Klaviyo and the Klaviyo logo are trademarks or registered trademarks of Klaviyo, Inc. or its affiliates.