How to enter former profiles within the "1st Anniversary" flow

Hi Jess! 

Thank you so much for your support.

Yes, you are right, the back-populating is not possible when the flow is based on date. I didn’t know it.

Your idea seems good, however I think when the segment is uploaded to the clonned flow, all emails will be sent at the same time. I mean, if the first order of one client was 2nd June 2023, and today is 1st May 2024, and I upload the segment today, all emails will be sent today, rather than next 2nd June 2024.

What do you think? Do you think the whole emails will be sent at the same time? I can test it placing a delay between the trigger and the email for checking, but before doing it I need your idea.

Thanks!

A lot 😅

@mrosique,

Ok, I have an idea that might solve part of the problem. Is the first purchase date a profile property from which you can create a segment? If so, try this:

 - Create a segment where first purchase date is between 365 and 366 days ago. (Since this year was a leap year, you might want to make it 366 and 367, or just play with the numbers until you get what you want)

 - Clone the anniversary flow and make the segment the trigger.

 - Add a profile filter that excludes customers who are already in the original anniversary flow, so it won’t send them another email when they qualify for the this flow.

I think this will work for customers who purchased from a year ago today (or whatever day you start it) through the time you created the anniversary flow.

For customers who purchased MORE than 366 days ago - my only idea is to create a segment with the farthest back purchase date (ie, purchased between 400 and 401 days ago, or whenever it happens to be), and follow the steps above, making sure to exclude profiles who qualify for the original anniversary flow and second one. You could change the message slightly, since it’s not really an anniversary for them - “thanks for being our customer for over a year!” or something like that.

I’m not used to working with date-based flows, so it’s kind of clunky! Let me know what you think.

@bluesnapper - Thanks for your reply! I think I understand what you are saying about adding past profiles with a time delay.

But, if instead of back-populating - if a new flow is created that is based on a segment, would that work? What I was trying to accomplish was to create a segment that would pull in customers who purchased 365 days before today - whenever “today” is, so they would come in organically - and send them the email(s), with out a time delay. Does that make sense?

I didn’t realize that date-triggered flows couldn’t be cloned and triggered with a segment, but it does make sense now, haha! 

Thanks for your input!

Just chiming in here, thanks for the shoutout @JessFosnough.

I did ponder about a way to add those past profiles who’s purchase anniversary is coming, but before the date triggered Flow was created… but I think I came to some of the same conclusion you guys have discussed in this thread. 

Instead, I’d offer this workaround similar to what we do with Birthday anniversaries in the similar situation.

We create monthly groups of those folks that *should* have received an “anniversary” and send it at the 1st of each month.  It’s not as snazzy as sending it on the actual 1-year mark, but I think it’s a good compromise.  

Klaviyo has a “day is in the month of” condition that’s handy for this scenario.

Here’s an example of the “Birthday Months” (for May in this case) - but you can adjust it for your Purchase Anniversary date field for each of the Months:
 

You can create those Segments ahead of time, and schedule them ahead of time (check the box for Determine recipients at send time) until you’re at the month when you’re all caught up to the Flow.  

Not the perfect solution, but perhaps an acceptable one?

@bluesnapper - thanks for the explanation, it definitely makes sense! I think we are just getting our wires crossed, haha!

If the segment I was envisioning worked correctly, it would pull in everyone who made a purchase 366 days before “today”. (366 b/c of leap day) Of course, the customers who were added the day it is created would not go in the flow. But tomorrow, when the original customers no longer qualify, and customers are pulled in who made a purchase 366 days before “today” (which is now tomorrow), then they would go through the flow. I have screen shots of my idea and what it returns, using the Birthday field, since I don’t have a First Purchase date in my account.

Here are the results:

Here is my profile with a (fake) birthday of 2023-05-02

What I don’t understand is why the other record (United - MW Newsletter) is in the segment, when the Birthday for that profile is 2023-05-03. It is another test account that I use.

So, perhaps this approach doesn’t work, either. Sigh….Well, I tried! 😂

Thank you for your help, @bluesnapper and @retention!

@mrosique - Good luck, and I hope Joseph’s idea can help you!