Test a journey

Use journey testing to verify the appearance and behavior of your messages, as well as channel configuration, tag conditions, and conversion or cancellation events. You can send a single message, or test the full journey according to your specified timing, and generate versions of Performance and message reports that are based on your test audience.

Test a journey

Send a journey to a test audience according to your specified timing, then evaluate its performance. Follow these steps to test a journey that has never been started, or started but never edited.

 Note

The option to test a journey is not available until the journey is configured with the minimum requirements to start it.

If you just created the journey, you will already be on the Manage screen. Otherwise, first go to Messages » Messages Overview and click for a journey. Then:

  1. From the Manage screen, go to Test and click Create a test.
  2. Enter at least one named user or Test GroupA reusable audience group that can be used as a recipient for test messages. and select from the results.
     Tip

    • If you used tag conditions in your journey, make sure you know which users in your test audience have which tags.
    • If you personalized messages using attributes, assign the relevant attributes to your test audience.

  3. Specify the amount of time you want between delivery of each message in your test journey.
  4. Click Create test.
  5. Click Start test on the Test screen. You can repeat this step to restart the test.

Now you can evaluate the test.

Test your changes after editing a journey

Follow these steps to test your changes after editing a started or paused journey.

If you just edited the journey, you will already be on the Manage screen. Otherwise, first go to Messages » Messages Overview and click for a journey. Then:

  1. Click Test changes next to the notice You have unpublished changes.
    1. If you have created a test for this journey before, click Yes, create new test to confirm deleting previous test data.
  2. Enter at least one named user or Test GroupA reusable audience group that can be used as a recipient for test messages. and select from the results.
     Tip

    • If you used tag conditions in your journey, make sure you know which users in your test audience have which tags.
    • If you personalized messages using attributes, assign the relevant attributes to your test audience.

  3. Specify the amount of time you want between delivery of each message in your test journey.
  4. Click Create test.
  5. Click Start test on the Test screen. You can repeat this step to restart the test.

Now you can evaluate the test.

Test a message in a journey

Send a single message to a test audience. You can send a test message at any time.

  1. Go to Messages » Journeys, select a journey in the map, and click Manage.
  2. Click for the message you want to test, and select Send Test Message.
  3. Enter at least one named user or Test GroupA reusable audience group that can be used as a recipient for test messages. and select from the results.
  4. Click Send.

Now you can verify the appearance and behavior of the message on each channel the message was configured for.

Evaluate a journey test

Journey tests are manually triggered, so the first message in the journey is sent to every member of the test audience, then the audience is filtered by channel availability and tag conditions.

After you start a journey test, verify:

View a journey Test report

  1. Go to Messages » Messages Overview.

  2. Click or for a journey, then go to Test. The report has these main elements:

    • Performance metrics: Statistical data for the journey and each message. See Performance Data on this page.
    • Message reports: Click Report to open an individual message report.

Performance data

The following data are included in the Test report:

Triggers
The trigger used to initiate the journey (tag change, custom event, inactivity, etc.) and the total number of times it was triggered. The trigger and count are located in the banner at the top of the report.
 Note

Users may trigger the journey more than once, depending on the journey’s rule limitLimits that cap the number of times any member of your audience can trigger a journey, helping prevent you from over-notifying your audience, e.g., a maximum of 1 per day. Rule limits are set per journey and apply at the named user level. , so this count may be higher than the number of individual users who triggered the journey.

Conversions / Reactivations
The number of users who exited the journey by a Conversion event. If your journey does not have a Conversion outcome, this count will not appear. For journeys using the Inactivity trigger, Conversions is instead labeled Reactivations. The conversion/reactivation count is located above Filtered for each message.
Filters and counts
The reasons why users exited the journey, or fell out of the funnel. Filters and their counts are listed under Filtered, to the left of each message in the journey. Filters include:
  • Conditions: The number of users who exited due to not meeting the message’s tag conditions, e.g., message 2 was only delivered to users with tag hotdog.
  • Other: The number of users who exited due to other reasons.
Users eligible for message
The total number of users that have met the criteria to receive the message.
Direct engagements
The total number of direct app opens and clicks on web notifications, and the percentage of direct engagements, calculated as the percentage of total number of sends / total number of direct engagements.