MAYBE! I got it! When I create Time Delay before the Anchor Point, it uses “wait until x days before anchor point” instead of just “wait 5 days”!

Hey @tieu,

You’re pretty close in it’s understanding!

The Target Date Delay is a unique time delay found only in date triggered flows and only when you’ve chosen to start/trigger the flow before the target date. This anchor point is similar to a normal time delay but instead of delaying for a certain period of time, it delay users until the specified date that caused the user to trigger the flow.

If you wanted to start the flow on your target date - i.e. on someone’s birthday or anniversary - this unique target date delay won’t be available. You can adjust which option you wanted under the date trigger flow settings.

Starting the flow before your target date is a great way to send preemptive reminders or teaser emails to build excitement in your recipients. For example, a great use case for this would be sending a discount email out to your recipients 1 week before their birthday (Email #1 in the screenshot) and then on their birthday/target date receive an email celebrating their birthday, but also to remind them to use their coupon if they haven’t already. This strategy is a very common one and is highlighted in our How to build a birthday flow Help Center article as well.

If that’s not the sort of strategy you were going for, you can always trigger the flow on the specified target date which would remove the target date delay anchor point all together. This results in a normal flow where it would be triggered once that specific date is reached. 

I hope this helps!

David

I don’t want the flow to start on the target date. I want it to start 12 months before that date. 

How do I get rid of the delay completely. 

Hey @samsonlarge,

Although you can’t remove the Target Date Delay component, you don’t necessarily have to use it! If you still wanted the flow to start before the date property and not use that unique delay component, you can just place the Target Date Delay step at the very end of your flow. This would be similar to the example below where the flow would trigger 3 months prior to the Birthdate date property but not make use of the Target Date Delay.

David

@David To  Actually mate. If you already created conditional splits and delays below that delay you can’t move them around. I had made a flow with over 23 splits in and now I need to completely scrap the thing and restart because you can’t move splits?? So frustrating and honestly a really basic feature included in every flow building platform I’ve ever used. Can we please get someone from Klaviyo to fix this issues so that they actually have a competitive flow builder?

Hey @samsonlarge,

Although you can’t remove the Target Date Delay component, you don’t necessarily have to use it! If you still wanted the flow to start before the date property and not use that unique delay component, you can just place the Target Date Delay step at the very end of your flow. This would be similar to the example below where the flow would trigger 3 months prior to the Birthdate date property but not make use of the Target Date Delay.

David

ALSO @David To Why can’t i just move the delay card to the bottom of the flow when I’m done. Seems like it shouldn’t be too hard to do but it’s no possible.  

Hey @samsonlarge,

Although you can’t remove the Target Date Delay component, you don’t necessarily have to use it! If you still wanted the flow to start before the date property and not use that unique delay component, you can just place the Target Date Delay step at the very end of your flow. This would be similar to the example below where the flow would trigger 3 months prior to the Birthdate date property but not make use of the Target Date Delay.

David