When a business moves to a Salesforce dedicated IP, typically within Marketing Cloud or Account Engagement (Pardot), they transition from a shared environment where reputation is communal to a blank slate. This blank slate, or 'cold' IP, is viewed with suspicion by Internet Service Providers (ISPs). Because the IP address has no history of legitimate sending, any sudden spike in volume will be categorized as potential spam. To avoid this, you must engage in a disciplined IP warming process.
IP warming is the deliberate act of gradually increasing the volume of mail sent from a new IP address over a period of weeks. The goal is to establish a positive sending history with mailbox providers like Gmail, Yahoo, and Microsoft. By starting small and increasing volume predictably, you prove to these providers that you are a legitimate sender with engaged recipients.
The Technical Foundation of IP Warming
Before sending the first email, your Salesforce instance must be configured correctly. This includes ensuring that SPF, DKIM, and DMARC are fully authenticated. In Salesforce Marketing Cloud, this is usually handled through the Sender Authentication Package (SAP). Without these protocols, warming is impossible because ISPs cannot verify that you own the domain sending from the new IP.
Furthermore, you must ensure your feedback loops (FBLs) are active. Salesforce handles most FBL registrations automatically for dedicated IPs, but verifying that complaint data is flowing back into your suppression lists is critical. If a user marks your email as spam during the warming phase and you continue to email them, your reputation will plummet before the process even gains momentum.
Selecting Your Warming Segments
One of the most common mistakes in IP warming is using your entire list from day one. Instead, you must curate your warmest segments. These are subscribers who have recently opted in or have opened/clicked an email within the last 30 to 60 days.
High engagement signals to ISPs that your mail is wanted. If your initial batches result in high open rates and near-zero complaint rates, ISPs will increase your 'sending allowance' more quickly. Avoid sending to older, unengaged lists or purchased data during this period, as the risk of hard bounces and spam traps is significantly higher.
A Sample Volume Throttling Schedule
While every sender profile is different, a standard approach involves doubling your volume at regular intervals. A typical schedule for a sender with a target volume of 500,000 emails per month might look like this:
- Days 1-3
- Send 500 emails per day to your most engaged users.
- Days 4-7
- Increase to 1,000 emails per day.
- Week 2
- Increase to 5,000 - 10,000 emails per day.
- Week 3
- Gradually move toward 20,000 - 50,000 emails per day.
- Week 4 and beyond
- Continue doubling until you reach your steady-state production volume.
During this time, it is vital to monitor for deferred or throttled messages. If you notice that an ISP like Outlook is pushing your mail into a queue rather than delivering it, stay at your current volume or even decrease it for a few days until the throttling subsides.
Monitoring Deliverability and Placement
Visibility is the most important asset during a migration. Relying solely on Salesforce's built-in 'Sent' and 'Delivered' metrics can be misleading, as a 'Delivered' status only means the ISP accepted the message, not that it reached the inbox. It could very well be sitting in the spam folder.
Using a monitoring tool like SenderSignal allows you to track your IP reputation and blacklist status in real-time. If your new dedicated IP ends up on a blocklist during week two, you need to know immediately so you can pause sending and remediate the issue. Dedicated monitoring helps bridge the gap between Salesforce’s outbound logs and the actual experience of the end-user.
Managing Content During the Warmup
During the warming phase, keep your content as 'safe' as possible. This is not the time for aggressive sales language, excessive use of 'Free' or 'Buy Now' in subject lines, or complex HTML layouts with dozens of external links.
Keep your messages simple, relevant, and highly personalized. High-value content such as newsletters, account updates, or requested alerts are ideal. The goal is to generate as many positive signals (opens, clicks, and 'not spam' markings) as possible. If a user moves your email from the 'Promotions' tab to the 'Primary' tab, that is a massive win for your IP reputation.
Identifying and Handling Setbacks
It is rare for an IP warming process to be perfectly linear. You may encounter a 'soft bounce' spike where an ISP rejects mail with a message like '421: Too many connections'. This is a sign that you are moving too fast.
When this happens, do not stop sending entirely, as this can look suspicious. Instead, hold your volume steady for three to four days. If you see high bounce rates, audit your data sources immediately. Integrating SenderSignal into your workflow during this phase can help you identify if the issue is specific to one provider or a broader reputation problem across all receivers.
Final Handover to Production
Once you have reached your target volume and are seeing consistent inbox placement across major providers, you can consider the IP 'warmed.' However, reputation maintenance is ongoing. Salesforce dedicated IPs require a minimum volume (usually around 100,000 to 250,000 sends per month) to stay 'hot.' If you stop sending for more than 30 days, the ISP filters will 'forget' your reputation, and you may need to go through a re-warming process.
By following a structured ramp-up, prioritizing engaged users, and maintaining constant surveillance of your placement metrics, you can transition to your Salesforce dedicated IP without the risk of long-term deliverability damage.