One Time Send Campaigns using Message Limit Feature

Blueshift allows you to set a limit at the campaign level for the number of messages that should be sent regardless of the segment size. If the size of the segment is less than the limit that is set, then the campaign will be sent to the entire segment. Otherwise the number of sends will be limited to what was set in the messaging preferences. You can read more about that feature here.

Example warming schedule:

Open

This warming schedule kicks off with 200 messages. Volume is then doubled after each day while excluding users who previously received a campaign with a message limit. After increasing the volume over several days the full segment size will be reached and the IP is considered warmed, as long as deliverability is in good standing.

Campaign settings for Day 1 Warmup Send:

Open

This setting should be applied to the first campaign that will be used to warmup the new adapter. This campaign will use the main segment that contains 75k customers and because “Limit number of message(s) for this campaign to” is set to 200, the campaign will only send to 200 customers.

Main segment:

In order to message the remaining users, a new campaign and segment need to be created that excludes those 200 customers who were sent the initial warmup campaign.

The remaining users from the main segment still have to get messaged so another campaign and segment need to be created that excludes those 200 customers who were sent the initial warmup campaign.

Segment that EXCLUDES customers who received warmup campaign:

The day 2 warmup volume then doubles to 400. You would use the same exclusion segment from above and add a messaging limit of 400 at the campaign level. This way you are only sending warmup campaigns to customers who did not previously receive one. To send to the remaining customers from the segment another campaign and segment need to be created that suppresses the day 2 warmup campaign.

Segment that EXCLUDES customers who received the second warmup campaign:

This process should be repeated for the subsequent warmup days until the total volume of 75k is reached.

Just as a quick recap, the day 1 warmup campaign should use the main segment without any conditions but have the limit 200 messages in place. To send to the remaining users in the same day another segment that suppresses these 200 customers needs to be used in another campaign. The two campaign sends will add up to the total amount of customers that are in the main segment. Day 2, 3, 4 etc. warmup campaigns will continue to use segments that suppress customers who previously received a warmup campaign. So in the day 3 warmup campaign the segment should be suppressing customers who received day 1 and day 2 warmup campaigns and then the send for the remaining users would only suppress the customers who were sent the day 3 warmup campaign. Day 4 warmup campaign would suppress customers who received days 1-3 warmup campaigns and the send for the remaining users would only suppress the customers who were sent the day 4 warmup campaign. So on and so forth.

Segment Triggered Campaigns using Control Bucket

You can also use a segment triggered campaign that uses the control bucket in the filtering. The control bucket is a number 1-100 that is randomly assigned to user profiles and is used to split segments into smaller groups or buckets. For example, if you have segment of 100,00k customers, and add a condition of bsft_control_bucket is less then or equal to 50, this should return a count of roughly 50k customers.

With the control bucket you will have to play around with the range to first get the count of 200 if we are basing it on the IP warming schedule from above. Once you get that count in a test segment, you can use the main segment at the campaign level and use the control bucket condition that yields the 200 customers for the warmup trigger and add another trigger without any conditions that will be sent to the remaining customers on the segment.

In the first trigger you can see that we have the control bucket condition that will sent to roughly 200 customers. The remaining users who do not qualify for the control bucket condition will receive the second trigger. The total of both trigger sends will add up to count of the main segment.

For the day 2 warmup you have to include the main segment conditions, suppress sends for the IP Warmup 200 trigger, and and a control bucket range until you get a count close to 400. This segment is only used to get the desired volume for the warmup campaign trigger. You would then add those conditions to the trigger filter while still using the main segment.

The IP Warmup trigger should always suppress customers who were sent past warmup trigger.

This process should be repeated until the full IP warming volume has been reached.