I’m trying to set up First Purchase Anniversary Flow for my brand but I got confused.
Months ago, I started collecting First Purchase data with this flow:
Now, I want to create the flow. I used the default flow map in Klaviyo:
I have 2 questions/concerns.
-Since I started obtaining data months ago, is there any way to remove the 365-day time delay and start sending it right away? E.g., I have some customers who purchased in February 2024 already and we have this profile property in Klaviyo. If I set the flow live, they will need to wait 365 days, right? But I want to send it in February 2025. I don’t think removing the time delay entirely would work for the new recipients. But is there any way to manage it?
-My other concern is about the conditional split here. It does not seem right to me because we have some customers place orders more than once in a year. E.g., If someone places an order in March 2024 and July 2024, when the time comes, the conditional split will send it to the YES path. However, these orders are in a year and he should receive the 1st year anniversary message. I’m a bit confused.
Is there anyone managed it before?
Best answer by retention
I noticed you had a Flow Filter set to “Placed Order equals 1 over all time” - this will limit this Date triggered Flow to only first time customers since anyone who Placed Order more than once will be excluded from the Flow. So your second conditional split will not work as you intended.
I would remove that Filter so that past customers (and repeat customers) will continue to stay in this Flow as it repeats yearly.
Then, to separate folks between the first year, or subsequent anniversaries, use a conditional split on the “First Purchase Date” to see if the day was in the last 366 days. If it is (Yes), then it is their First Anniversary. If it’s greater than 366 days, then it’s past their one year so it’s in the “Repeat Annivesary” branch.
See here:
Alternatively, you can also use a Profile property update (like you did with the First Purchase Date) to set a custom property (e.g. first_annivesary = True) after the First Anniversary message is sent, so that subsequent date triggers will check that property if that value is previously set. If the profile has that property set to True, then it will go to the Repeat Anniversary branch.
You could manually backfill their purchase anniversary dates.....as such have to will not have to wait another full year to receive their anniversary email...and for new recipients, keep the 365 day delay in place
I noticed you had a Flow Filter set to “Placed Order equals 1 over all time” - this will limit this Date triggered Flow to only first time customers since anyone who Placed Order more than once will be excluded from the Flow. So your second conditional split will not work as you intended.
I would remove that Filter so that past customers (and repeat customers) will continue to stay in this Flow as it repeats yearly.
Then, to separate folks between the first year, or subsequent anniversaries, use a conditional split on the “First Purchase Date” to see if the day was in the last 366 days. If it is (Yes), then it is their First Anniversary. If it’s greater than 366 days, then it’s past their one year so it’s in the “Repeat Annivesary” branch.
See here:
Alternatively, you can also use a Profile property update (like you did with the First Purchase Date) to set a custom property (e.g. first_annivesary = True) after the First Anniversary message is sent, so that subsequent date triggers will check that property if that value is previously set. If the profile has that property set to True, then it will go to the Repeat Anniversary branch.
I noticed you had a Flow Filter set to “Placed Order equals 1 over all time” - this will limit this Date triggered Flow to only first time customers since anyone who Placed Order more than once will be excluded from the Flow. So your second conditional split will not work as you intended.
I would remove that Filter so that past customers (and repeat customers) will continue to stay in this Flow as it repeats yearly.
Then, to separate folks between the first year, or subsequent anniversaries, use a conditional split on the “First Purchase Date” to see if the day was in the last 366 days. If it is (Yes), then it is their First Anniversary. If it’s greater than 366 days, then it’s past their one year so it’s in the “Repeat Annivesary” branch.
See here:
Alternatively, you can also use a Profile property update (like you did with the First Purchase Date) to set a custom property (e.g. first_annivesary = True) after the First Anniversary message is sent, so that subsequent date triggers will check that property if that value is previously set. If the profile has that property set to True, then it will go to the Repeat Anniversary branch.
By clicking “Accept All Cookies,” you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
Privacy Preference Center
Your Privacy
Strictly Necessary Cookies
Performance Cookies
Functional Cookies
Targeting Cookies
Site Analytics
Your Privacy
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Privacy Notice
Strictly Necessary Cookies
Always Active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
Performance Cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Functional Cookies
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
Targeting Cookies
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Site Analytics
These cookies record your visit to our website, and are used to track your visit including information such as: web page interactions (clicks, hovers, focus, mouse movements, browsing, zooms and other interactions), referring web page/source through which you accessed the Sites, heatmaps and scrolls, screen resolution, ISP, and statistics associated with the interaction between device or browser and the Sites. If you are accessing our Services with a European IP address, you have been asked to consent to the use of these cookies (you are free to deny your consent).