Time-based engagement journey
Use a Time-Based Engagement Journey to engage users on a schedule. Send personalized messages at a defined date, time, or recurring frequency.
This example sends personalized weekly highlights. Adapt the pattern for other scheduled campaigns.
Configuration overview
Example journey flow
Users enter this journey every week. It then checks whether they engaged with the previous recap.
Engaged users receive weekly highlights, recommendations, and follow-up content.
Unengaged users receive a lighter reminder and can have their profile updated.
The journey repeats on the configured weekly schedule.

Step 1: Set journey details and conversion event
Enter a descriptive name for your journey. This helps you identify the journey later.
Provide a brief description that explains the purpose or goal of the journey.
Next, define the conversion event for this journey. Since this example focuses on encouraging users to open the app, select Open App as the conversion event.
To configure the conversion event:
From the Conversion Event dropdown, select Open App.
Enable Select Conversion Event Property.
Select the event property you want to use for conversion tracking.
For this example, select UTM Campaign as the property, choose Equals as the operator, and enter weekly_highlights as the value.
Set a conversion period to define how long users will be counted toward the conversion event after exiting the journey. For this example, set the conversion period to 7 days.

Step 2: Configure the engagement window
In the Entry Rules step, enable Engagement Window to define when journey messages can be sent.
For this example, the journey sends weekly highlights to users. Since these messages are not time-critical, it is better to deliver them during regular engagement hours.
Set the allowed sending time between 09:00 and 18:00, and select weekdays from Monday to Friday.
Keep Ignore messages sent outside Engagement Window disabled. If a message is triggered outside the selected time range, it will be held and delivered when the Engagement Window becomes active.

Step 3: Configure time-based entry rules
Next, choose how users should enter the journey.
For this example, select Enter users at an optimal time. Since the journey is designed to send personalized highlights on a weekly schedule, users should enter the journey at a planned time instead of entering immediately when they become eligible.
This allows you to control when the weekly highlights journey starts and ensures that users receive the communication at a consistent time each week.
Set the Frequency Type to Weekly.
For this example, set the frequency to 1 and select Monday as the day of the week. This allows the journey to run once every week and send personalized highlights at a consistent time.
Keep Use User’s Timezone enabled if you want each user to receive the message according to their local time.

Step 4: Configure eligibility options
In the Eligibility Options section, define how often users can enter the journey.
For this example, select Multiple Times. Since the journey sends weekly highlights, users should be able to enter the journey again in future weeks.
Set a Lock Duration to prevent users from entering the same journey too frequently. For example, you can set the lock duration to 7 days so that each user can enter the journey once per week.
You can leave Entry Capping empty unless you want to limit the total number of times a user can enter this journey.

Step 5: Select the entry audience
In the Audience step, select the users who are eligible to enter the journey.
For this example, select Active user for 7 days. This allows you to target users who have recently interacted with your app and are more likely to engage with weekly personalized highlights.
To target all users, skip this step and do not select a segment.

Step 6: Build the journey flow
Journey starting point
The journey starts on its configured schedule, not from a user action.
Review the starting configuration:
Trigger type: Time-Based
Eligibility type: Multiple
Audience: Active user for 7 days
Schedule: Beginning on 25/06/2026 at 13:25
Users can enter multiple times on the defined schedule. The selected audience includes users active within the last seven days.

Check the previous weekly recap
After users enter the journey based on the Time-Based trigger, the system checks whether they engaged with the Previous Weekly Recap event.
This check creates two paths.
On Performed
For users who have already shown interest in the previous weekly recap, send an email about the next personalized weekly highlights.
Your weekly highlights are ready.
On Timed Out
For users who did not interact with the previous recap within the expected time, send a follow-up message with a lighter reminder or a different content angle.
We picked a few things you might like.

Continue each path
After the previous recap engagement check, continue each path with the appropriate follow-up messages.
On Performed path
Users who engaged with the previous weekly recap continue through the main flow. In this example, they receive:
An email with the next weekly highlights
A push notification with personalized recommendations
An in-app message that guides them to explore weekly content
Example messages:
“Your weekly highlights are ready.”
“Your recommendations are here.”
“Explore your weekly content.”
On Timed Out path
Users who did not engage with the previous recap receive a lighter re-engagement message. You can also update their profile to use this information in future segmentation or campaigns.
Example message:
“We picked a few things you might like.”
Example profile update:
“Weekly recap not engaged.”

Check whether the recommendation was clicked
After users receive the weekly highlights and recommendations, the journey checks whether they clicked the recommendation.
On Performed
If the user clicks the recommendation, they continue to the On_Performed path and can receive additional personalized content.
Example in-app message:
Based on what you viewed, here are more suggestions for you.
On Timed Out
If the user does not click the recommendation, they continue to the On_Timed_Out path. In this example, the profile is updated to indicate that the weekly recap was not engaged with.
Exit points
An Exit Point marks where a user’s journey ends. In this example, the journey can end in two ways:
Completion of the expected action
The journey can end when users complete the expected engagement action, such as interacting with the weekly recap or clicking a recommendation.
End of follow-up attempts
The journey can also end when users do not engage after the follow-up messages are completed.
Step 7: Review and launch
Before launching the journey, review the main configuration areas:
Setup: Journey name, description, conversion event, and conversion filters
Entry Rules: Time-based entry logic, schedule, frequency, and engagement window
Audience: Selected segments or all-user targeting
Build: Journey steps, event checks, branches, messages, and exit paths
If the journey setup is still changing, save it as a draft and return later.
Launch options
Save & Launch
Use Save & Launch when the journey is ready to go live. This saves your latest changes and activates the journey.
Save
Use Save when you want to keep the current setup as a draft. This is useful if the journey still needs review, testing, or approval.
Navigation behavior
Back
Use Back to return to the previous step. Your existing work in the Build step remains available while you continue editing.
Back to Journey List
Use Back to Journey List to leave the journey creation flow and return to the journey listing page. If you leave without saving, your latest changes are not kept.
Last updated
Was this helpful?