Skip to main content
Solved

Replenishment Flow Reminder - Back population

S
Contributor I
Forum|alt.badge.img+1
  • SAD
  • Contributor I
  • 1 reply

I have set up two replenishment flows. One will be going live tmwr and the other is for back population.

I am having issues with the back population flowand I have a few questions:

#1 I have created a segmented list, but the parameters I have set up are only providing profiles that have ordered at least once but it is not taking out profiles who have ordered twice between dates (Aug 1, 2024 - March 3, 2025). When I adjust parameters, it will show everyone who has placed an order more than once (which is a lot lower). How do I set up the parameters correctly so I have the right profiles in the segmented list?

The goal is to send everyone who has only ordered once to reorder/replenish. The flow is set up with a trigger metric, with profile filters, what someone has done/not done.

 

#2 - When will the first email be sent out to the back population segmented list? My first email is set at 35 days, second email, X days later, third email X days later.

 

#3 - Will a profile be removed from the flow if they place an order at any time within the email sequence, or do I need to set up a trigger for this? 

 

#4 - I have set up a conditional split at the X days mark to send a reminder email to profiles who have not engaged with the previous 3 emails. Will this email only go out to those who have not engaged with previous 3 emails or to all eventhough an order was placed?

Best answer by retention

HI ​@SAD, welcome to the community!

For #1, you can try the rule “Placed Order equals 1” instead of “at least once.”  They sound the same, but equal means exactly one time, where as “at least once” means one or more times. 

For #2, when you back populate the Flow, they will happen as if they entered the Flow had it been Live from the first time delay.  In your example, if you turned on the Flow today, with a 35 days delay to the first message, then the person that would have entered the Flow 35 days ago, will now be ready to be sent today.  Someone 34 days ago, will be sent tomorrow, and so on.  It will not back-populate beyond 35 days, because they have already passed the time delay of the Flow.  You can read more about how Back Populating works here:

For #3, by default, there are no implicit rules on any Flow to remove anyone with the exception if the user is suppressed (e.g. unsubscribed, or manually suppressed).  To create such conditions, that’s where Profile Filters or Trigger Filters can come in.  Trigger Filters are rules/exceptions of the Trigger for people to enter the Flow.  Profile Filters are rules/filters based on the a users profile or behavior.  In your example, you can set a common Profile Filter for “Has not made a purchase since starting the flow” as you can see here: 

You can learn more about Flow Trigger Filters and Profile Filters here:

For #4, this one is a bit harder to figure out for you since I don’t have all the details of how you setup the conditional branch.  When you setup a filter “Not opened or Not clicks an email” you can also specify specific emails (or any emails).  So you *can* set it up to be just those three emails - OR - you can setup to be with any emails.  Do you mind sharing a screenshot of your conditional branch so we can see how you did it?

Hope these help!  Keep them coming. :) 

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

2 replies

retention
Partner - Platinum
Forum|alt.badge.img+62
  • retention
  • 2025 Champion
  • 949 replies
  • Answer
  • March 4, 2025

HI ​@SAD, welcome to the community!

For #1, you can try the rule “Placed Order equals 1” instead of “at least once.”  They sound the same, but equal means exactly one time, where as “at least once” means one or more times. 

For #2, when you back populate the Flow, they will happen as if they entered the Flow had it been Live from the first time delay.  In your example, if you turned on the Flow today, with a 35 days delay to the first message, then the person that would have entered the Flow 35 days ago, will now be ready to be sent today.  Someone 34 days ago, will be sent tomorrow, and so on.  It will not back-populate beyond 35 days, because they have already passed the time delay of the Flow.  You can read more about how Back Populating works here:

For #3, by default, there are no implicit rules on any Flow to remove anyone with the exception if the user is suppressed (e.g. unsubscribed, or manually suppressed).  To create such conditions, that’s where Profile Filters or Trigger Filters can come in.  Trigger Filters are rules/exceptions of the Trigger for people to enter the Flow.  Profile Filters are rules/filters based on the a users profile or behavior.  In your example, you can set a common Profile Filter for “Has not made a purchase since starting the flow” as you can see here: 

You can learn more about Flow Trigger Filters and Profile Filters here:

For #4, this one is a bit harder to figure out for you since I don’t have all the details of how you setup the conditional branch.  When you setup a filter “Not opened or Not clicks an email” you can also specify specific emails (or any emails).  So you *can* set it up to be just those three emails - OR - you can setup to be with any emails.  Do you mind sharing a screenshot of your conditional branch so we can see how you did it?

Hope these help!  Keep them coming. :) 

Joseph Hsieh // retentioncommerce.com // twitter: @retention
S
1 person likes this
S
Contributor I
Forum|alt.badge.img+1
  • SAD
  • Author
  • Contributor I
  • 1 reply
  • March 4, 2025

Thank you for the explanation. It is very helpful. I will make the changes suggested to the segmented list. Your explanation of the back population entering the flow also makes more sense to me now. See the screenshot of the conditional split. 

One recommendation a Klaviyo expert mentioned was to consider email campaigns for the back population profiles. 

 

Reply


Terms & Conditions

Links & Resources

Platforms

Partners

Useful Things

About

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