Skip to main content
Solved

First Purchase flow back population


Forum|alt.badge.img+1

Hi everyone!

I’m having trouble with my First Purchase Anniversary Flow again.

I have huge data of First Purchase Date tags. This flow is running since June 2024.


And I recently launched first purchase anniversary flow:

 


However, I’m unable to back populate the flow since it’s date-triggered flow. Is there any way to add those 91K people to this flow?

 

Thanks!

Best answer by Mich expert

Back-populating profiles into a date-triggered flow in Klaviyo, like your First Purchase Anniversary Flow, can be tricky because Klaviyo doesn’t allow retroactive triggering for profiles based on past dates. However, you can achieve this goal with a workaround:

Solution: Use a Segment and Manual Flow Trigger

  1. Create a Segment for Profiles to Back-Populate

    • Go to Lists & Segments and create a new segment with the following conditions:
      • Properties about someone > First Purchase Date > is before > [today's date].
      • Optionally, add filters to exclude profiles already in the flow to avoid duplicates.
  2. Export the Segment

    • Export the segment as a CSV file by clicking Manage Segment > Export Segment to CSV.
  3. Manually Trigger the Flow for the Segment

    • Duplicate your existing First Purchase Anniversary Flow and make it a manually triggered flow:
      • Change the trigger from Date Property to List-Based Trigger.
      • Upload the exported CSV file as a new list and set the flow to trigger for this list.
    • Activate the duplicated flow temporarily to process these profiles.
  4. Deactivate the Temporary Flow

    • Once all 91K profiles have gone through the flow, deactivate it to avoid conflicts with the original flow.
  5. Continue with the Original Flow

    • Keep your original First Purchase Anniversary Flow active for new profiles that meet the date condition moving forward.

Key Notes

  • If the flow sends time-sensitive emails (e.g., exactly on the anniversary date), use Delays in the temporary flow to adjust the timing for each email stage.
  • Monitor the temporary flow closely to ensure profiles are processed as expected.
  • For large datasets, stagger the upload to prevent exceeding Klaviyo’s processing limits.

Let me know if you’d like detailed guidance on any of the steps!

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

3 replies

Mich expert
Problem Solver IV
Forum|alt.badge.img+11
  • Problem Solver IV
  • 64 replies
  • Answer
  • January 16, 2025

Back-populating profiles into a date-triggered flow in Klaviyo, like your First Purchase Anniversary Flow, can be tricky because Klaviyo doesn’t allow retroactive triggering for profiles based on past dates. However, you can achieve this goal with a workaround:

Solution: Use a Segment and Manual Flow Trigger

  1. Create a Segment for Profiles to Back-Populate

    • Go to Lists & Segments and create a new segment with the following conditions:
      • Properties about someone > First Purchase Date > is before > [today's date].
      • Optionally, add filters to exclude profiles already in the flow to avoid duplicates.
  2. Export the Segment

    • Export the segment as a CSV file by clicking Manage Segment > Export Segment to CSV.
  3. Manually Trigger the Flow for the Segment

    • Duplicate your existing First Purchase Anniversary Flow and make it a manually triggered flow:
      • Change the trigger from Date Property to List-Based Trigger.
      • Upload the exported CSV file as a new list and set the flow to trigger for this list.
    • Activate the duplicated flow temporarily to process these profiles.
  4. Deactivate the Temporary Flow

    • Once all 91K profiles have gone through the flow, deactivate it to avoid conflicts with the original flow.
  5. Continue with the Original Flow

    • Keep your original First Purchase Anniversary Flow active for new profiles that meet the date condition moving forward.

Key Notes

  • If the flow sends time-sensitive emails (e.g., exactly on the anniversary date), use Delays in the temporary flow to adjust the timing for each email stage.
  • Monitor the temporary flow closely to ensure profiles are processed as expected.
  • For large datasets, stagger the upload to prevent exceeding Klaviyo’s processing limits.

Let me know if you’d like detailed guidance on any of the steps!


Forum|alt.badge.img+1
  • Author
  • Contributor I
  • 2 replies
  • January 17, 2025

@Mich expert thank you so much Mich! This helps a lot!

Just one more question, could you please give me more details about this:

If the flow sends time-sensitive emails (e.g., exactly on the anniversary date), use Delays in the temporary flow to adjust the timing for each email stage.

So, do I have to use conditional splits & time delays every single day from June to today?


Mich expert
Problem Solver IV
Forum|alt.badge.img+11
  • Problem Solver IV
  • 64 replies
  • January 17, 2025

Thanks for messaging 

You can send me a message privately