Summary / TL:DR: This documentation covers several methods of warming IP’s in Blueshift.
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:
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 the deliverability is in good standing.
Settings for Day 1 Send:
This setting should be applied to the campaign(s) that are intending to warmup the new adapter. The remaining users from the segment still have to get messaged so another campaign needs to get created that excludes the users who received a warmup campaign.
Wrap up
Still need help?
We know this can be frustrating. To get further help open a Jira ticket.
Cannot find the article you’re looking for?
Suggest a new article here!