After you design your campaign journey, you can set the following campaign properties from the Campaign Studio Properties tab:
- Campaign execution schedule
- Messaging preferences
- Monitoring preferences
- Journey re-qualification
- Seed lists
- Campaign execution report summary
- Campaign failure alerts
- Journey testing and optimization settings
You can specify if and when a user who has entered the campaign can enter the campaign again.
- For segment triggered campaigns, you can specify a time period in minutes, hours, or days. A user can re-qualify for a journey only after the user exits the journey.
- For event triggered campaigns, you can specify that users can re-qualify once at any time, once in a lifetime, or multiple times concurrently.
- Users cannot re-qualify for one-time and recurring campaigns.
You can add tags to your campaign to organize your marketing content.
You can also use tags to implement a strict workflow for your team so that they don’t accidentally send the campaign to the wrong set of users. For more information, see Tag based campaign restrictions.
By using a seed you can test where an email will land across different email clients and devices as well as see how your campaigns are rendered in different browsers and email clients. Add Seed lists for the campaign from the Monitoring Preferences section on the Properties tab. For more information, see Seed Lists.
For one-time and recurring campaigns, you can specify email addresses of people who should receive a summary of the last run of the campaign. This will be an email version of the execution summary report and will contain information on the number of users who were messaged and the number of users who were skipped.
For one-time and recurring campaigns, you can set up a timer to get a notification if the campaign does not complete execution. This can help you to identify any issues sooner rather than later. An email is sent to the email addresses specified.
If a campaign does not complete in the specified time, it might not always be a cause of concern. The delay might be due to certain campaign configurations. You can use the following checklist to find out if campaign configurations are causing the delays.
- Campaign uses Dayparting.
- Campaign uses Send time optimization.
- Campaign uses automatic winner selection because of which there is a holdout time for running the A/B test before selecting the winner.
- Campaign has a messaging limit that is lower than the number of customers in the segment.
- Campaign uses rate limiting.
- Campaign uses external fetches and there is a rate limit on invoking external fetch.
- Your account has a (backend) rate limit on a channel or app used in the campaign.
You can enable Holdout testing to measure the impact of running a campaign against a baseline of doing nothing.
Select the Run in test mode option to test the campaign on real users without actually sending any messages. For more information, see Test Mode.