Define campaign properties

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
• Tagging
• Seed lists
• Campaign execution report summary
• Campaign failure alerts
• Attribution preference
• Journey testing and optimization settings

Messaging preferences

With messaging preferences, you can set messaging limits or override messaging restrictions. You can also use messaging limits for IP warmup. For more information, see Set messaging preferences.

Journey re-qualification

You can specify whether and when a user who has entered the campaign can re-enter it.

• 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 exiting the journey.
• For event-triggered campaigns, you can specify that users can re-qualify once, once in a lifetime, or multiple times concurrently.
• Users cannot re-qualify for one-time and recurring campaigns.

Tagging

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.

Monitoring preferences

You can use Seed lists and specify the email addresses of users who should receive the campaign execution report summary or the campaign failure alert email.

Seed lists

Use a seed list to test where email or SMS messages are delivered across devices and clients, and to preview how your campaigns are rendered. Add a seed list to the campaign from the Monitoring Preferences section on the Properties tab. For more information, see Seed lists.

Execution report

For one-time and recurring campaigns, you can specify the 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 include information on the number of users who were messaged and the number who were skipped.

Campaign failure alert

For one-time and recurring campaigns, you can configure a timer to receive a notification if the campaign does not complete execution. This helps you identify potential issues earlier. An email is sent to the specified addresses.

If a campaign does not complete within the specified time, it is not always a cause for concern. In some cases, the delay may be due to campaign configuration settings. Use the following checklist to determine whether configuration settings are causing the delay.

• The campaign uses Dayparting.
• The campaign uses Send time optimization.
• The campaign uses automatic winner selection, which requires a holdout period to run the A/B test before selecting a winner.
• The campaign's messaging limit is lower than the number of customers in the segment.
• The campaign uses rate limiting.
• The campaign uses external fetches, and there is a rate limit on external fetch invocation.
• Your account has a backend rate limit on a channel or app used in the campaign.

Attribution preference

Use this setting to control whether Blueshift attributes goal events and related metrics to a campaign.

This setting is useful for transactional campaigns, such as order confirmations and password resets, and for test campaigns, where goal attribution may not be useful.

Select Skip goal event attribution for this campaign to prevent Blueshift from attributing goal events to this campaign based on attribution rules.

This option is unselected by default. You cannot change this setting while the campaign is in the launched state. To change it, pause the campaign first.

For more information about custom goals and campaign attribution, see Custom goals and campaign attribution.

Holdout testing

You can enable Holdout testing to measure the impact of running a campaign against a baseline of doing nothing.

Test mode

Select the Run in test mode option to test the campaign on real users without actually sending any messages. For more information, see Journey testing.