Hi there @CandleShack,

Welcome to the Community! Thanks for asking your question regarding segments here and hope I can help.

To begin collecting first purchase dates from new customers, you'll need to set up a Flow to apply this property. The flow setup will look like this:
​
Trigger: Placed Order
Conditional Split: What someone has done > placed order > equals > 1 > over all time
Update Profile Property: Create Profile Property > First purchase Date > Select date data type > check Use current date when this step is reached

There is unfortunately no way to retroactively update every person's first purchase date, but there is a workaround if you were able to export your customer's first order history from within your ecommerce backend. This would allow you to apply this first purchase date as a custom profile property.

Hope this helped,
Alex

Wow! Amazing! Thanks a lot for your help. Will definitely try it out :-D

Glad I could help @CandleShack! If you have any questions feel free to ask our Community again!

Hello @alex.hong 
I hope you’re well.
We tried to do your tutorial to set the date of the first purchase.
We checked and it doesn't work for us. 
I put you the screenshots below the different flows

can you help us ? 

have a good day !

Hi there @MathieuM,

Thanks for reaching out. I’d be glad to assist. Where do you seem to be running into issues? I believe that you have set things up properly so are you seeing contacts not have a property changed or is there something else? 

Looking forward to your response,

Alex

Thanks for your answer @alex.hong !

The contacts are not updated with the purchase date.

I'm not sure where the problem comes from... 
Can you redo the 2nd flow of your tuto but with more screen.

If there is a problem, it comes from here.
Thanks for your help Alex !

Hi there @MathieuM,

Apologies. Thank you for bringing something back in mind for myself. Upon reviewing, it appears that you are correct that this would not update and that this method may not be sustainable in the long term! This is due to how back population works in Klaviyo in relation to dates such as 365 days. I've since edited my response to reflect this. 

Thank you,

Alex