Configure wait for a date attribute in user journey

  • Created : May, 24, 2021
  • Last Updated : Jan, 13, 2022

Journey Builder

NotifyVisitors journey builder enables you to create campaigns and engage users with them on the basis of their various lifecycle stages. You can provide a personalized experience to the users on the basis of the triggers, conditions, and actions. As your users move through different channels, you can easily engage them on the channels at which they are present, creating for them an omnichannel messaging experience. 

Apart from configuring different conditions and triggers, you can manage the flow of the journey as well through different features. One of the prominent features to manage the flow of the user journey is wait for a date attribute. Read this article to know more about the feature and how you can configure this feature in NotifyVisitors.


“Wait for a date” feature enables you to engage the users on a specific date, or before or after any system event. It works as a reminder to the users to perform an action on the arrival of the date of any event or before or after the event if the user misses it.

When can you use this feature in a user journey? 

Suppose a user has four active insurance policies and your system sends him a message regarding the renewal of the policy. In such a scenario, it will be useful for the user to get the notification of the renewal of the policy which is coming in X days or if the user missed the renewal then the same can be used to remind the user after x number of days.

To implement such scenarios, you can add a unique user ID attribute for the policy and identify the policy as an individual user. This way you can run a journey for the users and engage them on the date of the renewal of the policy, or before or after the date of the renewal, in case the user misses it.

Let us see how you can engage the users at different time intervals after he performs an event.

  1. You can create a user journey by navigating to the NotifyVisitors dashboard> Analytics> journey builder.

user journey navigation

2. Next, create an event. We are here creating an event for PURCHASE. As we are here taking the use case of a user purchasing a policy, we created a PURCHASE EVENT and added the attributes of the EVENT EXPIRED as we will engage the user using the “wait for a date” attribute feature. You can add other attributes also to simplify the journey of the user such as user id, the source, and the location of the users.

    purchase journey

3. Navigate to the WAIT FOR A DATE feature under the FLOW CONTROL section. Drag and drop the WAIT FOR A DATE BLOCK. Choose the TYPE OF WAIT and the details regarding it.


4. Choose the “wait for the date & time value of an event attribute” in the TYPE OF WAIT category.  Next, you can choose the time interval from the drop-down menu in the WAIT DETAILS category.



Now, let us understand the feature with the above-stated use case :

Taking the above use case of policy purchase, we will now understand how you can engage the users at different time intervals.

Suppose a user purchased an insurance policy and the date for the expiry of the insurance policy is after one year. In such a case, the journey of the user will begin with the PURCHASE of the policy and will wait for the arrival of the EXPIRY OF THE POLICY as you had added the EXPIRED EVENT as the attribute.

1.You can engage the user with a campaign before the expiry of the event to remind him about the renewal of the policy. In such a case you can choose BEFORE from the WAIT DETAILS category.


Note: You can choose the time frame in terms of months, weeks, minutes, hours, and days. Here we are choosing 1 month, which means we are here urging and reminding the users before the one -month of expiry of the insurance policy to renew the policy in advance. You can keep on engaging the users as the date of the expiry of the policy comes closer by selecting the time frame.

2.Next condition is, you can wait for the status of the renewal for the policy by configuring the time trigger. That means you can configure the time-trigger of let's say one day after the expiry of the policy if the user has still not renewed the policy. If the payment has not been made, you can check if he has opened the mail or not. If the user has opened the mail, you can send him an SMS urging him to renew the policy.  You can repeat the same step if the user has not opened the mail with a modified SMS.

You can choose AFTER from the WAIT DETAILS  category. In this case, you can check after one day of the policy’s expiry if the user has missed the policy renewal. Further, you can send him a reminder via email.


Consequently, you can end the journey for the users who have renewed the policy and further engage the users who have not renewed the policy yet.


The WAIT FOR A DATE feature helps you in managing the user journey by engaging the users at a specific time interval on an event trigger.

Related Articles