There are several ways in which you can test your campaign journey before and after you launch your campaign.
You can preview user specific content on the journey builder by specifying the user email or the Customer ID. With this option, you can preview the templates in the journey for the particular user.
Note: Templates using recommendations will show content based on the default Blueshift user: email@example.com
You can run a campaign in test mode to test the campaign’s configurations and messages before launching it.
- Use this feature for testing purposes only, ideally with a curated short list of test users.
- Do not use the Test mode to complete a dry run for the entire campaign journey for the entire eligible user population.
- A campaign in test mode must always have an end time set, which should be no longer than 1 month to prevent such campaigns from running forever.
Some possible use cases for this feature are:
- Debugging a specific message rendering issue across many users.
- QA-ing sends across many users before making a campaign live.
- Testing external fetch rate limiting against your own systems before making a campaign live.
- The test mode setting for a segment triggered campaign (one-time, recurring, and segment triggered) cannot be changed after a campaign is launched (i.e. when the campaign is in the 'paused' or 'launched' state).
- An event triggered campaign should either be run solely in test mode or solely in regular mode. We do not recommend toggling the "test mode" flag on and off for a campaign once it has been launched (i.e. when the campaign is in the 'paused' or 'launched' state) as it could lead to execution issues.
- After you have finished testing the campaign, we recommend that you clone it and launch it in regular mode to avoid any execution issues.
- When you launch a campaign in test mode, it does not send a message to the end user. Instead, it logs the message in your Blueshift S3 bucket folder campaigns/debug/<campaign_uuid> with the following file name: <channel>_<user’s email or user UUID>_<trigger_uuid>.html.
- You can review the messages in the S3 folder to understand which user qualified for which message (and which trigger). At this time, there is no way to visualize the test user’s flow through the campaign journey
- It does not apply messaging limits.
- Since it does not send a message, it also does not add to the user’s messaging counts.
- Links in the message body get rewritten so that they do not generate click stats.
- No stats of any kind get created.
Event or API triggered campaigns have the following additional characteristics:
- It ignores the campaign journey concurrency setting.
- Any live users that get processed while the campaign is in test mode will exit the campaign. This ensures no messaging occurs while the campaign is in test mode, even if the live user had received a message from a previous trigger when the campaign was live.
- Any test users that get processed while the campaign is live will exit the campaign. This ensures test users don't receive any subsequent messages if the campaign gets switched from test mode to live.
Select the Run in test mode option on the Campaign properties tab to test the campaign on real users without actually sending any messages.
- This feature is disabled by default.
- Test mode is limited to 5 campaigns.
Contact firstname.lastname@example.org if you want to enable this feature or if you need more campaigns allocated for testing.
For an event triggered campaign that is launched, you can test the event-triggered flows by publishing a test event from the Journey tab. This capability makes it easy to experience and validate a journey right from the Journey tab.
- To publish the test event, click the Test campaign with sample event icon.
The Publish a sample event window opens. The sample event has some pre-populated values from the most recent event received.
- In the Publish a sample event window, provide the user information.
- You can add additional parameters to the event data.
- Click Publish.
A sample event is generated and it triggers the event flow for the specified user.