Use test profiles to test your journey before publishing it. This mode allows you to run a test of your journey and identify issues using test profiles.
Only test profiles can enter a journey in test mode. You can either create new test profiles or turn existing profiles into test profiles. Learn more about test profiles in this section.
Before testing your journey, you must resolve all errors if any. Learn how to check errors before testing in this section.
To use the test mode, follow these steps:
To activate the test mode, activate the Test toggle, located in the top right corner.
If the journey has at least one Wait activity, set the Wait time parameter to define the time that each wait activity and event timeout will last in test mode. The default time is 10 seconds for waits and event timeouts. This will ensure that you get the test results quickly.
When a reaction event with a timeout is used in a journey, the wait time default and minimum value is 40 seconds. See this section.
Use the Trigger an event button to configure and send events to the journey.
Configure the different fields expected. In the Profile Identifier field, enter the value of the field used to identify the test profile. It can be the email address, for example. Make sure to send events related to test profiles. See this section.
After the events are received, click the Show log button to view the test result and verify them. See this section.
If there is any error, deactivate the test mode, modify your journey and test it again. Once tests are done, you can publish your journey. See this page.
JOtestmode - <schema of your event>
Use the Trigger an event button to configure an event that will make a person enter the journey.
When you trigger an event in test mode, a real event is generated, meaning it will also hit other journey listening to this event.
As a prerequisite, you must know which profiles are flagged as test profiles in Adobe Experience Platform. Indeed, the test mode only allows these profiles in the journey and the event must contain an ID. The expected ID depends on the event configuration. It can be an ECID or an email address for example. The value of this key needs to be added in the Profile Identifier field.
If your journey contains several events, use the drop-down list to select an event. Then, for each event, configure the fields passed and the execution of the event sending. The interface helps you pass the right information in the event payload and make sure the information type is correct. The test mode saves the last parameters used in a test session for later use.
The interface allows you to pass simple event parameters. If you want to pass collections or other advanced objects in the event, you can click on Code View to see the entire code of the payload and modify it. For example, you can copy and paste event information prepared by a technical user.
A technical user can also use this interface to compose event payloads and trigger events without having to use a third-party tool.
When clicking the Send button, the test begins. The progression of the individual in the journey is represented by a visual flow. The path progressively turns green as the individual moves across the journey. If an error occurs, a warning symbol is displayed on the corresponding step. You can place the cursor on it to display more information about the error and access full details (when available).
When you select a different test profile in the event configuration screen and run the test again, the visual flow is cleared and shows the path of the new individual.
When opening a journey in test, the displayed path corresponds to the last test executed.
The test mode is also available for journeys that use a rule-based event. For more information on rule-based events, refer to this page.
When triggering an event, the Event configuration screen allows you to define the event parameters to pass in the test. You can view the event ID condition by clicking the tooltip icon in the top right corner. A tooltip is also available next to each field that is part of the rule evaluation.
When using a business event, use the test mode to trigger a single test profile entrance in the journey, simulate the event and pass the right profile ID. You have to pass the event parameters and the identifier of the test profile that will enter the journey in test. In test mode, there is no “Code view” mode available for journeys based on business events.
Note that when you first trigger a business event, you cannot change the business event definition in the same test session. You can only make the same individual or a different individual enter the journey passing the same or another identifier. If you want to change business event parameters, you must stop and start again test mode.
The Show log button allows you to view the test results. This page displays the journey’s current information in JSON format. A button allows you to copy entire nodes. You need to manually refresh the page to update the journey’s test results.
In the test logs, in case of an error when calling a third-party system (data source or action), the error code and error response are displayed.
The number of individuals (technically they are called instances) currently inside the journey are displayed. Here is useful information that is displayed for each individual:
Here are the different statuses of an individual’s journey:
When an event is triggered using the test mode, a dataset is automatically generated with the name of the source.
The test mode automatically creates an Experience Event and sends it to Adobe Experience Platform. The name of the source for this experience Event is “Journey Orchestration Test Events”.