After you design your campaign journey, you can set the campaign properties, like messaging preferences, journey re-qualification, tagging, seed lists, campaign execution report summary, campaign failure alerts and so on, from the Campaign Studio Properties tab.
With messaging preferences, you can set messaging limits or override messaging restrictions.
|Skip User Messaging Limits Check||
In order to minimize message fatigue, you can set a limit on the maximum number of messages a single user can receive in a given period of time. This setting is available under the Maximum Messages tab in Account Settings.
By selecting Skip User Messaging Limits Check you can ignore the messaging limits.
|Message users who have unsubscribed or have reported your emails as spam||By default, Blueshift will not message users who have previously unsubscribed or reported spam unless you override that via this setting.|
|Skip duplicate messaging check||A transaction segment might return multiple transaction records for the same user. By default, Blueshift does not send multiple messages to the same user, even if the message is for a different transaction record. By selecting this setting, you can bypass this default behavior and send multiple messages to a user, one for each transaction record.|
|Skip global inclusion segment check||
A global inclusion segment helps to ensure an account can only message users based on certain user attributes. This is done from the Other Settings tab in Account Settings. Select this option to ignore this limitation and message all eligible users.
|Sometimes you may need to send out critical communication for example a password reset confirmation or a notification for a system outage. When communicating such critical information, it is important to ensure that the intended users receive your message independent of their preferences for your promotional/ marketing campaigns. The first 3 settings can help you achieve this objective.|
|Limit number of messages for this campaign to __||For one-time and recurring campaigns, you can limit the maximum number of messages that can be sent by the campaign.|
|Limit messaging rate to __ messages per minute||
For one-time and recurring campaigns, you can also limit how fast the campaign can message users.
Note: You cannot choose a rate that is lower than 1 message per minute or one that can cause the campaign to take more than 1 day to message all eligible users in the segment. For example, if a segment has 4800 users, you cannot use a messaging rate of 100 messages/ hour since that would lead to a campaign execution time of 48 hours (=2 days). For more information, see Messaging rate limitations.
|The last 2 settings will be most critical during your IP warmup phase.|
Note: You must set the messaging rate such that the campaign execution time for one-time and recurring campaigns is not greater than 1 day. If the (segment size or campaign messaging limit) / (campaign rate limit) > 1 day (1440 minutes), an error occurs when you try to save the campaign.
For example, consider a campaign where the segment size is 1M and the campaign messaging limit is set to 100K.
- If the campaign rate limit is set as 1000/minute, then the time required to execute the campaign is 100K/1000 = 100 minutes which is < 1 day.
- If the campaign rate limit is set as 100/minute, then the time required to execute the campaign is 100K/100 = 1000 minutes which is still < 1 day.
- If the campaign rate limit is set as 10/minute, then the time required to execute the campaign is 100K/10 = 10,000 minutes which is > 1 day and hence an error occurs and you will not be able to save the campaign.
IP warming is a tactic that you can use to gradually increase the number of messages sent from a specific source. When you gradually increase the number of messages that you send, your email source gains trust with ISPs and email service providers so that your emails are not marked as spam.
Slowly, over a period of time, you can launch more one time campaigns with more users in the segment that you can target. You can also use trigger filters to exclude users who received an email from the previous campaign. So, over a period of time, you can gradually increase the number of emails that you send so that ISPs/email service providers gain trust on the source that sends emails and do not mark the emails as spam.
For example, in the campaign that you create, you include a segment that contains 500 users. Now, if you send 500 messages at the first go, an internet service provider (ISP)/email service provider (ESP) may suddenly notice something unusual and start marking your emails as spam. To avoid that, you have to create a campaign with conditions that limit the number of emails sent with every run.
In the Limit number of messages for this campaign to setting, you can specify an upper limit. For example, if you specify 100, we send only 100 emails even if a segment that you are targeting includes more users.
In addition, you can use the Limit messaging rate option to set a cap on the messaging rate for one-time and recurring campaigns. You can specify the number of messages that our platform sends per minute. For example, you can specify that our platform sends 200 messages per minute. This setting provides additional functionality that you can use to warm up the email source.
To send a specific number of messages within a specific window, you can specify the messaging limits and a start time for the campaign.
For example, if you want the Blueshift platform to send 600 messages/hour, and want to send messages between 1pm to 4pm only, here's what you can do:
- In the Start setting under Execution Schedule, specify the time as 1:00 PM.
- In the Limit number of messages for this campaign to setting, specify 1800 messages (based on the 3 hour interval that you want to choose and send 600 messages per hour).
- In the Limit messaging rate setting, specify 10 messages per minute (based on 600 messages for every 60 minutes).
This configuration ensures that 600 messages per hour (or 1800 messages per minute) are sent between 1pm and 4pm.
You can also add the criteria bsft_open_message_uuid is empty in the trigger filter to ensure that a message is sent to users who have not yet opened a message that was sent as a part of the campaign.
You can specify if and when a user who has entered the campaign can enter the campaign again. You can change the journey re-qualification settings only when the campaign is in draft state.
- For segment triggered campaigns, you can specify a time period in minutes, hours, or days.
- For event triggered campaigns, you can specify that users can requalify once at any time, once in a lifetime, or multiple times concurrently.
- Users cannot requalify 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.