Skip to main content
Solved

Using multiple trigger splits in one flow vs creating multiple flows with single trigger filter?


Forum|alt.badge.img+2
  • Contributor I
  • 4 replies

Hi,

I’m new to Klaviyo and trying to figure out the best way to do things within a currently running setup. In my abandoned cart flow, there’s currently a trigger split according to category, i.e. whether the product is from a certain collection or not. My question is whether it is better to create a separate cart abandon flow for each trigger split (i.e. using trigger filters per category), as technically, you could end up having a lot of trigger splits if you want to split by more than one category. 

 

I guess a similar situation is when using custom profile data to hide or show certain content, e.g. discount code to new subscribers vs customers who previously purchased. Is it better practice to create a conditional split or just create 2 separate campaigns?

 

The only thing I can think of is that depending on the level of targeting, these structures could get very complicated and difficult to manage!

 

Many thanks! Nat

Best answer by MichalSofia

Hi ​@NatM 

 

I have a million triggers that I operate and I find that I prefer to keep the same trigger under one flow unless I want to get two separate reporting.

For example, I am using an identity resolution that sends a browse abandonment email to customers who visited my site and did not sign up to my email program. I keep the evergreen browse abandonment separate from the identity browse abandonment because I want it to be easy to see the uplift and value from the identity resolution specifically.

 

Regarding the show/hide, I like to make two splits when the topic is completely different. But if there are just some adjustments or personalization capabilities, I use show/hide and the if/else language in my campaigns.

 

I hope this helps!

View original
Did this topic or the replies in the thread help you find an answer to your question?

2 replies

MichalSofia
Problem Solver II
Forum|alt.badge.img+1
  • 2025 Champion
  • 8 replies
  • Answer
  • March 31, 2025

Hi ​@NatM 

 

I have a million triggers that I operate and I find that I prefer to keep the same trigger under one flow unless I want to get two separate reporting.

For example, I am using an identity resolution that sends a browse abandonment email to customers who visited my site and did not sign up to my email program. I keep the evergreen browse abandonment separate from the identity browse abandonment because I want it to be easy to see the uplift and value from the identity resolution specifically.

 

Regarding the show/hide, I like to make two splits when the topic is completely different. But if there are just some adjustments or personalization capabilities, I use show/hide and the if/else language in my campaigns.

 

I hope this helps!


Forum|alt.badge.img+2
  • Author
  • Contributor I
  • 4 replies
  • March 31, 2025

 

MichalSofia wrote:

Hi ​@NatM 

 

I have a million triggers that I operate and I find that I prefer to keep the same trigger under one flow unless I want to get two separate reporting.

For example, I am using an identity resolution that sends a browse abandonment email to customers who visited my site and did not sign up to my email program. I keep the evergreen browse abandonment separate from the identity browse abandonment because I want it to be easy to see the uplift and value from the identity resolution specifically.

 

Regarding the show/hide, I like to make two splits when the topic is completely different. But if there are just some adjustments or personalization capabilities, I use show/hide and the if/else language in my campaigns.

 

I hope this helps!

 

Thank you, that’s insightful! One question though, you mentioned “I am using an identity resolution that sends a browse abandonment email to customers who visited my site and did not sign up to my email program.” — are you referring to your email list or something else? I’m wondering how you’re sending emails to non-subs :-)