How do I combine Tag and Event conditions in a Customer Journey?

When building a Customer Journey that targets users based on a mix of conditions, such as Tags and their event history (e.g., performed Event A but not Event B), it's best practice to use the entry point for the primary trigger and a Condition Split element for the more detailed filtering inside the Journey.

Here are the two most effective methods to set this up:

Method 1: Real-Time Triggering (Recommended)

This approach is ideal for reacting to a user's actions as they happen. The Journey starts the moment a user performs a specific action.

1. Set the Entry Point: Start your Journey with a Trigger-based entry and select the specific event that should initiate the flow (e.g., Initial Action event).
2. Add a Condition Split: Immediately after the entry element, add a Condition Split.
3. Configure Conditions: Inside the Condition Split, add the rest of your targeting rules. For example:
   • Check for the absence of an event (e.g., Event Purchase count is 0).
   • Check for a specific Tag (e.g., Tag product_name is your_product_name).

This setup creates an "always-on" Journey that continuously listens for the trigger event and then immediately checks if the user meets the other criteria.

Method 2: Scheduled Audience Check

This approach is useful for targeting a broader audience on a recurring schedule (e.g., daily or weekly).

1. Create a Broad Segment: Create a segment that includes only your most stable, high-level condition. For example, a segment of all users with the Tag product_name set to your_product_name.
   • Important: Do not add your event-based rules (like Initial Action or Purchase) to this segment.
2. Set the Entry Point: Start your Journey with an Audience-based entry and select the segment you just created.
3. Enable Scheduled Launch: To ensure the Journey runs repeatedly for new users entering the segment, enable Scheduled Launch and set your desired frequency (e.g., daily).
4. Add a Condition Split: After the entry element, add a Condition Split to check for the remaining event-based conditions.

By separating the initial trigger from the detailed filtering, you create a more efficient and accurate Journey.