How can I run two separate journeys (e.g., a re-engagement journey and a scheduled promotional journey) at the same time without sending messages from both to the same user?

You can effectively manage users across multiple journeys to prevent message overlap by using a combination of Tags, Conversion Goals, and the Segment Split element. This ensures users in a specific-purpose journey (like a re-engagement campaign) do not receive messages from a general promotional journey until they have completed the first one.

Here is a recommended setup for two common scenarios: a Re-engagement Journey for inactive users and a Scheduled Promotional Journey for your main audience.

1. Re-engagement Journey Setup

This journey targets users who have become inactive and aims to bring them back.

1. Entry: Use an Audience-based Entry triggered by user inactivity (e.g., "Last Application Open is more than 3 days ago").
2. Apply a Tag: Immediately after the entry point, add a Set Tags element to apply a unique tag, such as in_winback_flow. This marks the user as being in this specific journey.
3. Send Messages: Add your re-engagement push notifications or emails.
4. Set a Goal: Add a Conversion Goal element to track when a user becomes active again. The goal should be a key activity event, like an "Application Open".
5. Configure Exit: In the Conversion Goal settings, enable the option to have the user exit the journey once the goal is achieved.
6. Remove the Tag: On the "Goal Reached" path of the Conversion Goal, add another Set Tags element to remove the in_winback_flow tag.

This setup ensures that as soon as a user re-engages, they are untagged and removed from the win-back flow.

2. Scheduled Promotional Journey Setup

This journey sends scheduled messages to your general audience.

1. Entry: Set up the entry for your main audience (e.g., all users).
2. Schedule Messages: For each push notification, you can set a specific date and time for it to be sent. Users entering the journey will wait until the next scheduled message's date arrives.
3. Add a Segment Split: Before each push notification element, insert a Segment Split.
4. Configure the Split: Set up the split to check for the tag from the re-engagement journey:
   • Branch 1 (User is in win-back): Create a condition "Tag in_winback_flow is true". Leave this branch empty or connect it past the push notification. Users in this branch will skip the message.
   • Branch 2 (User is active): This will be the "Else" branch. Connect this branch directly to your push notification element. Only users who are not in the win-back flow will receive the message.

By following this structure, you create a system where: 
* Inactive users enter the re-engagement journey and are tagged. 
* The tag prevents them from receiving messages from the promotional journey. 
* Once they become active, the tag is removed, they exit the re-engagement journey, and they immediately become eligible for the next scheduled message in the promotional journey.