Overview

Journey Builder 2.0 introduces a new Events action node that allows you to trigger custom events at specific points in a customer journey. These events can be used to track user progress, trigger other campaigns, and enrich user profiles with valuable interaction data.

🚧

Feature Availability Notice

The Events action is currently being released behind a feature toggle in this beta version. Contact your account manager to have this feature enabled for your account. We are actively working to enhance loop prevention mechanisms before making this feature generally available.

🚧

System Usage Allowance

Be aware that using Event Actions within your journeys will elevate the overall number of Events counted against your Project. If you have any questions about your allowed usage levels you should contact your account manager to confirm before using this feature.

Adding an Events Node to Your Journey

To add an Events node to your journey:

1. Open your journey in Journey Builder 2.0
2. Locate the User Actions section in the left panel
3. Find the Event icon in the options
4. Drag the Event icon from the left panel and drop it onto your journey canvas
5. Position it where you want this action to occur in your customer journey

Configuring an Events Node

Once you've added an Events node to your journey, you can configure it to trigger events in different ways:

Event Types

The Events node supports three types of event triggers:

• Event with Value: Trigger an event with a single value
• Event with Properties: Trigger an event with multiple properties in JSON format
• Plain Event: Trigger an event without any additional data

Setting Up Event with Value

To configure an event with a single value:

1. Click on the Events node in your journey
2. Enter an event name by either typing directly into the event name field, or clicking the dropdown to search and select from existing events.
3. Enter the value you want to associate with this event in the Value field
   Save your configuration

Setting Up Event with Properties (JSON Format)

To configure an event with multiple properties:

1. Click on the Events node in your journey
2. Enter an event name (by typing or selecting from existing events)
3. Enable the Event as JSON toggle to switch to JSON mode
4. Use the Add JSON Row button to add property fields
   1. For each property, enter:
      1. Key: The property name
      2. Value: The property value
5. To remove a property, click the delete (trash) icon next to the row
6. Save your configuration

🚧

If you delete all JSON rows, the node will automatically revert to the standard "Event with Value" mode.

How Events Nodes Work

When a user reaches an Events node in their journey:

1. The specified event is triggered
2. The event (with its value or properties) is recorded in the user's profile
3. Any campaigns that use this event as a trigger point will be activated
4. The user continues along their journey path

📘

Event Data in User Profiles

Events triggered by Events nodes are stored in the user's profile in the same format as events triggered through other methods. You can view this data in the Events tab of the user's profile.

Analytics for Events Nodes

The Events node displays an Arrived metric that shows how many users have reached this node in the journey.

This data helps you understand how many users have triggered the event and progressed through this stage of your journey.

Loop Prevention

❗️

In the current implementation, the system only prevents an Events node from triggering the same journey it belongs to (direct self-loops). This basic protection ensures that a journey cannot directly trigger itself through its own Events node.
Enhanced safeguards for more complex scenarios (such as campaigns triggering each other in circular patterns) are planned for upcoming releases. These future enhancements will include preventing execution of campaigns that are part of a loop and generating error notifications in your logs to explain when campaigns aren't executed due to loop detection.

Best Practice: When using Events nodes in the current version, carefully plan your cross-journey triggers to avoid creating circular references between different journeys, as the system currently only prevents direct self-loops.

Use Cases for Events Nodes

Events nodes can be useful in many scenarios:

• Journey Milestone Tracking: Record when users reach important points in their journey
• Multi-Journey Orchestration: Trigger different campaigns based on a user's progress
• Profile Enrichment: Add journey-specific data to user profiles
• Journey Branching: Use events to create complex branching logic across multiple journeys
• Analytics Enhancement: Create custom tracking events for deeper journey analytics

Example: Creating a Cross-Journey Trigger

You can use Events nodes to create connections between different journeys:

1. Set up a workflow campaign with an Events node that triggers "EventName" with a value
2. Create another campaign triggered by the same "EventName" event
3. When users reach the Events node in the first campaign, it will automatically trigger the second campaign
4. Both the event and the resulting actions will be recorded in the user's profile