Date Triggered Flows When the Date is Nested in the Product

Hi @TTG2023,

Thanks for sharing this question with our community.

My recommendation is to pass in the tour date as a custom property, build segments based on time intervals (I’ll explain what that means in a second) and use multiple segment-triggered flows (rather than metric-triggered) to send these marketing emails. This is because with a segment-triggered flow you can use the “date” date type which will give you more flexibility to target users based on values like “day is in the next” and other date-based properties.

Here’s an example screenshot below using a date (birthday). Using this segment you can send X amount of emails X amount of days in advance of a date (the tour date). When I say time intervals, what I mean is using “is in the next 3 months” in the segment definition and setting up as many segments as you think is necessary to target your tour dates i.e. day is in the next 6 months and triggering a separate flow off of that. You can also add time delays in the flow + as many marketing emails in each segment-triggered flow as you see fit for the given time interval i.e. 3 marketing emails in a segment triggered flow for tour date is in the next 3 months.

The one issue here is if the user books multiple tours, there’s no way to prevent the custom property for tour date from being overridden with that value. You can create multiple custom properties for each tour date to avoid this.

I hope that’s helpful.