Architect Journey Starter: On Dynamic Date

Dynamic Date Starter is used to trigger users according to their date type attributes or their date type event parameters. You can select an event or attribute option in this starter. When you select an event, you need to select an event parameter that will be in a date format. Also, only date type attributes are listed in the Dynamic Date Starter.

Dynamic Date Starter can take users from every platform such as website, mobile application, and contact list, as well as those where the data comes from Upsert User Data API. The same users can perform certain events or have date type attributes across these platforms. In such a case, the Dynamic Date Starter takes into account the last action or last updated attribute of the user.

The starter operates once a day at 1 AM (GMT+0). Therefore, do not forget to add a ‘wait’ element after the starter element which aligns with the customer’s time zone to ensure that you’re not sending messages at night.

Tips & Tricks

• If you are going to run a journey that needs to ignore the year within the date for each user, you can activate the Repeat Annually option. Once you activate this, it will ignore the year of the date. For Birthday or Anniversary use cases, you need to activate the option. This needs to be done as users have birthdays every year, and their birth years are also in the past. For such use cases, you need to ignore the year. The same goes for Anniversary.

• You can select the Before the Date option to trigger users ahead of a specific date. It allows you to send a message to users before the specified day. For example, you can send a voucher code 7 days before the user’s birthday to make them feel valued and boost their engagement. 

• In case you want to trigger users after a particular day had passed, you can select the After the Date option. If you have any cases like data is sending out from any source in a specific time but also you want to trigger a dynamic date starter after it, you can use this option. Also, you can use this option for some cases like ‘X days after the purchase’ to send a post-purchase message.

• Segmented users may come from Upsert User Data API or any other source without their language information. That’s why selecting the "All Languages" option on the Launch Settings is suggested.

In case you want to check certain parameters of the trigger event, you can add event parameters to the trigger section. This can help you target a more specific action. For example, if you want to send check-in reminders 2 days before a flight to your customers, you can add event parameters such as gate number, seat number or package information to personalize your messages even more.

For example, you want to segment an audience that booked a flight for future dates and did not purchase any ancillaries like baggage or seat selection. After the segmentation, you will send notifications for ancillaries to your passengers including information of their flight details. In this case, you can set your segmentation for a starter as follows:

Constant Event Parameters help you keep the same event for entering the journey for every single passenger, and use the event parameters of this event. This way, you can send the right content to your passengers. If your users have other flights that might fit into this segment, you can use the constant event parameters to send notifications with the correct flight details. For example, if a passenger named John booked a flight without any extra baggage or seat from CDG to JFK, you can send them a reminder 3 days in advance of their flight as follows: "Hello John, you can use your seat for a better view from CDG to JFK. How about a discount code for a better deal? Use SEAT10 to get 10% off."

Additional Segmentation

You can add more segments to your starter condition to target your audience more precisely. For example, you can take users whose birthday is today and who has a high discount affinity. Then users can enter the journey if they meet the date condition and the additional segment filters.

You can select from predefined segments, standard segments, predictive segments, RFM segments, and saved segments to filter your users to take into the journey.

Requirements

Before starting to use Dynamic Date in your journeys, make sure to complete the following requirements:

• Insider Tag Integration should be completed.
• SDK X integration should be completed for mobile app data reading.
• System rules should be defined.
• Date type attribute should be created.
• Events should be activated.
• Events should be sent from the website, mobile app, Upsert User Data API (if you are using any of them).

Use Cases

With the On Dynamic Date starter, you can:

• Send celebration messages to your users on occasions that are yearly repeated, such as birthdays, anniversaries, etc.,
• Target users whose subscription is about to get expired,
• Send a post-purchase email X days after the purchase date,
• Sending a flight reminder before the flight date.