Create a Date Property Triggered Flow

read

Overview

Using a Date Property to trigger a flow is a great way to set up an email sequence around key dates you might collect from customers and subscribers, such as:

  • Birthday
  • Anniversary
  • Appointment
  • Subscription Date
  • Wedding Date
  • Pregnancy Due Date

Learn how you can use signup forms to collect date properties from your customers. If you would like to trigger a flow off a date property you capture and store on profiles, choose the Date Property option from the initial Trigger Setup screen.

With this trigger option, you can build an automated flow that either starts on a specific date, or you can choose to set a flow in motion before a specific date. A person will qualify to enter a Date Property triggered flow whenever the selected property is added or updated on their profile.

With our dynamic Time Delays, you can automate emails leading up to a given date at certain points in time, send an email(s) on the date itself, and then send follow up emails after the date all within a single flow.

Note

If your flow counts down to a given date, we will automatically insert recipients into the appropriate place in your flow series when the date is set on their profile and they qualify to enter. This means not everyone will start at the beginning of a sequence when counting down to a date, if for example, you don't acquire someone's date property that far in advance

Configure a Date Property Trigger

When you first choose the Date Property trigger, you will be prompted to select which specific date property you would like to trigger the flow.

All date-based profile properties in your account will appear in the dropdown menu for selection.

After selecting a date-based profile property, you will need to choose when the flow should start:

  • Before the date
  • On the date

If you choose to start the flow before the date, you can choose any number of days, weeks or months. This will also produce an anchor point (Target Date Delay) on the actual date.

The final step is to set when the flow should repeat:

  • Monthly
    Recipients will qualify to enter this flow on a monthly recurring basis on the same day each month. For example, a monthly subscription reminder series.
  • Yearly
    Recipients will qualify to enter this flow on a yearly recurring basis on the same month/day. For example, a yearly birthday series.
  • Should not repeat
    Recipients will qualify to enter this flow only once when the full date matches (day, month, and year). For example, an appointment reminder.

You can also choose to apply a flow filter during your initial setup to restrict the flow to only certain people, and you can add or adjust these filters at any time. 

Update a Date Property Trigger

After you configure an initial Date Property trigger, you cannot edit the date property you selected. You can, however, edit when the flow will start and when it will repeat.

To edit these aspects of the trigger, click the Trigger card on the canvas, and click into the Trigger Setup pane on the lefthand sidebar.

How the Date Property Trigger Works

Whenever a date property is added or updated on a profile, Klaviyo will check to see if any flows are triggered by that date property. If so, and the date falls within the timeline of the flow, we'll pull the profile into the flow and insert them at the appropriate point based on the timing established within the series.

If a date is set or updated on a profile but doesn’t fall within the timeline of your flow, the profile will not be scheduled at that time. We’ll check daily and queue up the recipient based on the starting point you set for your series. For example, if you have a birthday flow starting 2 weeks before someone’s birthday, recipients will only qualify once their birthday is 2 weeks away.

If someone “missed the starting point” because the date property was set too late, we will insert them midway into the series at the appropriate point.

Let's say you have a wedding flow that starts 6 months before someone's wedding. Every month leading up to their wedding date, you share content and products that you think will interest the bride or groom. On April 1st you receive a recipients wedding date, and it's 1 month away. Klaviyo will automatically insert this recipient at the "Wait until 1 Month before person's Wedding" time point.The recipient will immediately be queued to receive the appropriate content.

If a date property is updated on a contact's profile, they will be added or removed from the flow accordingly. Before every email sends, Klaviyo verifies that the date used to trigger the flow is still the same:

If the date has been updated or deleted altogether, we will automatically skip all remaining scheduled emails to ensure the recipient doesn't get should-be-timely emails around a date that's now void.

If a new date is set, however, we will automatically re-queue the person based on the updated date. This is particularly helpful for appointment-focused flows -- if someone's appointment is rescheduled, all emails are automatically rescheduled around the new date.

If you've set your flow trigger to repeat, either monthly or yearly, we'll check all profiles in your account daily to ensure anyone who is due to enter a date-based flow is queued up. This check runs a full day ahead of time to ensure that no recipients miss out, regardless of what timezone they're in.

Counting Down with Time Delays

When you configure a flow to start before a specific date, a Target Date Delay is automatically created to serve as an anchor point. This component will have a target icon and will say "Wait until person's [Date Property]".

If you drag in a Time Delay before this target date anchor point, you will see a special type of delay configuration. This configuration will prompt you to fill in “Wait until ___ days/weeks/months before person’s [Date Property].” This allows you to easily countdown to the date using a regular Time Delay.

If you drag in a Time Delay after the Target Date Delay anchor point, the setup will be the same as a regular time delay. You will be prompted you to set the delay to wait a certain number of days/weeks/months after the previous step.

The Time Delay component is dynamic for Date Property-triggered flows, so you can place the same component anywhere and schedule actions easily, whether you're trying to countdown to the target date or follow up after the date.

Frequently Asked Questions (FAQ)

What is the Target Date Delay?
When you configure a flow to start before a given date, we will automatically create a Target Date Delay to serve as an "anchor point" in your series.

This Target Date Delay will always say, "Wait until person's [date]". This allows you easily countdown to this anchor and send an email on the target date itself by placing the email directly after the Target Date Delay. While you can configure this delay, you cannot delete it.

I have a flow counting down to a date property starting, let's say, 6 months in advance. What if someone doesn't get the date property set until 3 months out? Do I need to create separate flows for each possible entry time-point?
No, you don't need to create separate flows for each possible entry time-point. If your flow counts down to a given date, we will automatically insert someone into the appropriate place in the sequence when the property gets set on their profile. This means that not everyone must start at the beginning of a sequence when counting down to a date, if for example, you don't acquire someone's date that far in advance.

Can I trigger a flow around a specific date (i.e. July 4) instead of selecting a Date Property?
No. In order to trigger emails around a specific set date, like July 4, you would also need to choose your target audience for these emails. To achieve this, you must schedule a campaign to a target list/segment on the date of your choosing. To schedule a series of emails leading up to a single date, you can use scheduled campaigns to ensure that each email is prepared in advance to send at the right time.

 

Was this article helpful?
11 out of 14 found this helpful