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.
Click the Test Journey button in the toolbar at the bottom of the page.
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).
(Projects that use
userIdas a unique identifier will still need to enter an email address to send proofs from a journey.)
(Optional) Add test data to simulate the event that starts the journey. For example, if users are added to your journey after they sign up, you could add
"signUp":trueto simulate the event.
If your journey includes filters 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 box do not get added to the test user's profile—they're only used in the test send.)
Don't include the names of your custom events in your test data. For example, for an event called
customEventNamewith a data field called
customEventName.fieldName, you should only include
Click Test Journey.
Check your inbox or device to make sure you're receiving messages from the journey.
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
In the Start tile, select the Schedule entry source.
Select an internal send list consisting of your team members.
If you don't already have an internal send list for your team, head to the Lists page to create one.
Schedule the list to run when you're ready to add your teammates to the journey.
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:
Keep in mind
- You can only send one marketing template to an email address in an 18-hour
period. If you've tested a journey multiple times with the same email address
and aren't receiving messages, try using an alias
firstname.lastname@example.org). Some email domains don't support aliases. If that's the case for you, use a secondary email address to get around the 18-hour send limit.
- Test users will complete the entire journey, even if the journey is turned off.
- Users who are in a long delay tile when a journey is turned off may exit the journey before their delay step is complete.