How to Test a Program
This article walks you through how to preview a Program Email, and how to test a complete Program configuration. Some steps assume that you have configured a Program already. For more information on configuring your Program, see the article How to Configure Programs (Path).
Preview Program Email
To preview an email step in Program:
- Navigate to Journey Orchestrator > Programs.
- Edit or create a Program and add an email step.
- Add participants to the model configuration page and ensure participants are in Review, New, or Active status.
- Edit the email step on the model configuration page.
- Click PREVIEW. The Email Preview dialog appears.
- Select a participant from the drop-down list. The email preview changes according to the selected participant and tokens will also be updated.
- You can also use Previous Participant and Next Participant options to view the email preview for each participant.
7. Click Send to me to send an email preview to the logged-in user, or click Send test email to and enter an email address to send the email preview.
- This option is only available for Programs with participants in Review, New, or Active Status.
- To create an accurate preview email, the participant mapping must be completed correctly. If this mapping is incorrect, the Preview may look incorrect.
- This feature can be used without publishing the Program.
Test Complete Program Configuration
1. Clone Existing Outreach: Cloning your Program will recreate it with the configurations you set. After an Outreach is Published, you will not be able to reconfigure it. Using a clone of your Outreach will allow you to test it, and gives you the chance to make any necessary changes before publishing the actual Outreach to your contacts.
In the Program list view, hover on the Outreach you would like to test, and select the Clone button to create a copy.
2. Remove Original Participants: Your cloned Outreach will also copy participant sources from the original. These sources will need to be removed to make sure the Outreach is not sent to your contacts before it is tested.
After cloning your Outreach, you should automatically be taken to the model configuration screen. Click the green Participants icon.
On the Participants Configuration page, click the Delete icon to remove the copied participant sources.
3. Add Test Participants: Your test or dummy participant will need a real email address. No other specific criteria are required for this test.
The easiest way to add a test participant is via CSV. On the Participants Configuration page, click the + icon on the right to add a new source and select CSV.
You can upload an existing CSV by clicking Browse to locate it. The option “Click here to download the csv template” provides an easy foundation for creating a new CSV file with test participant data. Once you’ve configured this template with the email address you would like to send the test to, you can upload it as your CSV.
If you’ve already created a Power List with a test contact(s), you can instead select this Power List as your source.
4. Add Uniqueness Criteria, Map, and Sync Participant Sources: You will need to add Uniqueness Criteria, map the participant source fields, and sync participant sources as you would with a standard Program. For more information on how to complete these steps, see the article Adding Participants to a Program.
5. Change Set Timer and Conditional Wait: If you would like to test every email that will be sent out by the outreach on the same day, you may need to change the Time Limit and Waiting Periods that were set up in the original outreach’s Set Timer and Conditional Wait options. To learn more about configuring these options, see the article Configure Model and Emails for Program.
6. Publish Outreach: After your test participant(s) is added, publish the test Program to begin sending emails.
On the model configuration page of your cloned Outreach, click the PUBLISH option.
7. Act as the Recipient of the Outreach: Depending on how you’ve configured your outreach, you may need to take different steps in order to test every aspect of it. This could include waiting a set period of time after receiving the Heads Up Email before the Survey Email is sent, responding to the survey to receive the Thank You Email, or not responding to the survey long enough for a Reminder Email or Escalation Email to be sent.