Testing Journeys

Once you've built a journey, it's a good idea to test it out before any of your users go through it. Here's how to make sure everything is working right.

# In this article

# Add yourself or a teammate to the journey

You can add a single person (like yourself or a teammate) to the journey to make sure you receive messages, user profile updates, and subscriptions like one of your users would.

1. Switch to Draft mode for the journey you want to test, and click Test Journey.

2. Enter the email address of the person you'd like to add to the journey. It's best to send test messages to someone within your organization, like yourself. If you select one of your users, they will start receiving messages from the journey (even if you're testing a journey that's turned off).

   NOTE

   Projects that identify users by userId require email addresses to send proofs from a journey.

3. (Optional) Add some test data to simulate the event that adds users to the journey. The JSON entry box accepts the contents of a dataFields object in a hypothetical call to Iterable's POST /api/events/track API endpoint. For example, consider the following event payload:

   {
   "email": "example@domain.com ", 
   
   "eventName": "exampleEvent", 
   
   "dataFields": 
     { 
     "signUp": true
     } 
   }
   

   To test the journey, you would enter:

    { 
    "signUp": true
    }
   

   If your journey includes filter tiles that check fields on a user's profile, make sure those fields exist on the test user's profile. (The fields you include in the JSON entry box don't have any effect on the user's profile — they're only used to simulate the conditions needed to start the test.)

   IMPORTANT

   • You should only include the contents of a dataFields object in the JSON entry box. If you include a full event payload, the test will fail.
   • Don't include the names of any custom events in your test data. For example, for an event called customEventName with a data field called customEventName.fieldName, you should only include fieldName.

   

4. Click Test Journey.

5. Check your inbox or device to make sure you're receiving messages from the journey.

   NOTE

   When you use the Test journey button, any sends and clicks that occur count toward your journey's campaign delivery and performance metrics.

# Add a group of your teammates to the journey

If the journey is already live, you can add a group of your teammates to it, using either an internal send list or a filter tile. This is a great way to test out the journey with a larger group of test users.

# Use an internal send list

1. In the Start tile, select the Schedule entry source.

2. Select an internal send list consisting of your team members.

   NOTE

   If you don't already have an internal send list for your team, head to the Lists page to create one.

3. Schedule the list to run when you're ready to add your teammates to the journey.

4. After you're finished testing, make sure you either turn off the journey or disconnect/update the Start tile. (Otherwise, your teammates will keep receiving messages from the journey!)

# Add a filter that checks for your company's email domain

You can use a filter to make sure only members of your team can get added to the journey.

In the Start tile, set up an entry rule that requires users to have an email address with your company's domain to be eligible to enter the journey.

It should look like this: