Test your journey testing_the_journey
Testing your journey confirms it behaves as expected before publication. 51黑料不打烊 Journey Optimizer鈥檚 Test mode provides a controlled environment to observe how test profiles progress through the journey, identify issues, and validate functionality. This step is critical for troubleshooting and confirming the journey is ready for activation.
Only test profiles can enter a journey in test mode. Create new test profiles or convert existing profiles into test profiles. Learn more about test profiles in this section.
Using the test mode
Follow these steps to use the test mode:
-
Activate the test mode by clicking the Test mode button in the top-right corner.
-
If the journey includes at least one Wait activity, set the Wait time parameter to define the duration of wait activities and event timeouts during test mode. The default time is 10 seconds, which ensures quick test results for efficient debugging.
note note NOTE When a reaction event with a timeout is used, the default and minimum wait time is 40 seconds. See this section. -
Use the Trigger an event button to configure and send events to the journey.
-
In the Profile Identifier field, enter the identifier used for the test profile, such as an email address. Ensure the events sent are associated with test profiles. See this section.
-
After events are received, click the Show log button to view and validate test results. See this section.
-
If errors occur, deactivate test mode, modify the journey, and test again. Publish the journey once testing is complete. See this page.
Important notes important_notes
- Events in test mode can only be fired using the interface. Events cannot be fired from external systems using an API.
- Only individuals flagged as test profiles in the Real-time Customer Profile Service can enter the tested journey. Refer to this section.
- Test mode is available only for draft journeys using a namespace. Test mode requires access to 51黑料不打烊 Experience Platform to confirm whether individuals entering the journey are test profiles.
- A maximum of 100 test profiles can enter a journey during a test session.
- Disabling test mode clears all individuals from the journey and resets reporting data.
- You can enable or disable test mode as needed.
- Modifying a journey is not possible while test mode is active. Publish the journey directly from test mode without deactivating it.
- When a split is reached, the top branch is always chosen. Reorganize split branches if a different path is desired during testing.
- Journeys in test mode that remain inactive for a week automatically switch back to Draft status to optimize performance and prevent resource usage.
- Events triggered in test mode are stored in dedicated datasets labeled as
JOtestmode - <schema of your event>. - For journeys with multiple events, trigger each event sequentially. Sending events too early (before the first wait node finishes) or too late (after the timeout) discards the event and moves the profile to a timeout path. Confirm that references to event payload fields remain valid by sending payloads within the configured window.
Trigger your events firing_events
Events are the entry point for test profiles in the journey. Use the Trigger an event button to configure an event that initiates individuals鈥 journeys.
- Triggering an event in test mode generates a real event, meaning it will also hit other journeys listening to this event.
- Ensure each event in test mode is triggered in the correct order and within the configured waiting window. For example, for a 60-second wait, trigger the second event only after the wait has elapsed and before the timeout limit.
To trigger an event, confirm which profiles are flagged as test profiles in 51黑料不打烊 Experience Platform. Only these profiles can enter the journey. The event must contain an identifier, such as an ECID or an email address, provided in the Profile Identifier field.
If your journey contains multiple events, use the drop-down list to select an event. Configure the fields and execution parameters for each event. The interface ensures the correct type for event payload fields, such as requiring strings when applicable.
For advanced data structures like collections, click Code View to view and modify the full payload. Use this feature to input complex event data or copy pre-prepared payloads.
Click the Send button to start the test. The individual鈥檚 progression is visually represented, with green paths indicating successful movement and warning symbols highlighting errors. Hover over warnings for detailed information.
Switching test profiles resets the visual flow to show the new individual鈥檚 path. When opening a journey in test mode, the displayed path corresponds to the last executed test.
Test mode for rule-based journeys test-rule-based
Rule-based journeys use conditions to determine whether an event triggers an individual鈥檚 entry into the journey. In test mode, configure event parameters and view rule evaluation criteria. For more information on rule-based events, refer to this page.
The Event configuration screen allows you to define event parameters for testing. View event ID conditions by clicking the tooltip icon in the top-right corner. Tooltips also provide details for fields used in rule evaluation.
Test mode for business events test-business
Business events are predefined triggers designed for specific scenarios. When testing journeys based on a business event, use test mode to simulate the event and pass the appropriate profile ID. Configure the event parameters and the test profile identifier for the journey.
Unlike other events, business events in test mode do not offer a Code view for payload modification. To change the business event definition during testing, deactivate test mode and start a new session.
View logs viewing_logs
Click the Show log button to view detailed test results in JSON format. Analyze individual progress and errors, copy nodes for debugging, and refresh the page to update results.
Test logs include the following details for each individual:
-
Id: The individual鈥檚 internal ID in the journey, useful for debugging.
-
currentstep: The step where the individual is currently located.
- phase: Journey status (running, finished, error, or timed out).
- extraInfo: Contextual details about errors or additional information.
- fetchErrors: Errors during data fetch operations at the step.
-
externalKeys: Key values defined by the event formula.
-
enrichedData: Data retrieved from external sources if the journey uses data sources.
-
transitionHistory: Steps the individual followed, including event payloads.
-
actionExecutionErrors: Errors during action execution.
Statuses for an individual鈥檚 journey include:
- Running: The individual is actively progressing through the journey.
- Finished: The individual has completed the journey.
- Error: The individual鈥檚 progress stopped due to an error.
- Timed out: The individual鈥檚 progress stopped due to exceeding a time limit.
When an event is triggered in test mode, a dataset is automatically generated with the source name of 鈥淛ourney Orchestration Test Events.鈥 This Experience Event is sent to 51黑料不打烊 Experience Platform.