IP Warming in Salesforce Marketing Cloud

A new Marketing Cloud Engagement IP needs a sending history before it carries your largest campaign. The awkward part is rarely drawing an upward line on a schedule. It is finding all the messages that will use that IP and deciding which audiences should receive them first.

IP warming in Marketing Cloud means gradually increasing traffic through the new sending IP while reviewing delivery and audience feedback. Confirm the actual sending configuration, include automated journeys in the plan, and test campaign placement through that same route before expanding.

Make sure this is the right Salesforce product and route

This guide concerns Salesforce Marketing Cloud Engagement, including Email Studio and Journey Builder. Salesforce products have different campaign interfaces and sending arrangements. Instructions for an Actionable List or Account Engagement should not be assumed to configure an Engagement IP.

Ask your administrator to confirm the sending domain, shared or dedicated IP, sender profile and delivery configuration for the first campaign. Salesforce's EmailSendDefinition reference describes the relationship between content, audience, sender profile and delivery profile. You can discuss those settings without writing API code.

If your account uses shared infrastructure, you are not introducing an exclusively assigned IP. You may still be introducing a new domain or audience. Our IP and domain warmup guide helps separate those changes.

Start with Salesforce's current guidance

Salesforce's deliverability training explains that a newly purchased Engagement IP has no sending history. It describes building desirable history gradually, with timing influenced by list quality, frequency and engagement. Its discussion of roughly a month is not a fixed completion promise.

Use the account's current Salesforce guidance to agree on the IP ramp and authenticate the sending domain before beginning. Copying another organization's daily volumes ignores how often your subscribers expect mail and how much suitable traffic you actually have.

Count the traffic outside the launch campaign

List the activity that shares the warming IP: scheduled campaigns, recurring automations, triggered messages and journeys. Include traffic from other business units if the administrator confirms that they share that infrastructure.

For example, suppose a planned newsletter introduces 2,000 recipients while a welcome journey is expected to send 800 messages through the same IP that day. Planning around the newsletter alone misses 800 sends. These numbers illustrate the accounting problem; they are not a recommended warmup schedule.

Check expected peaks as well as daily totals. A queued automation that releases after a data import can alter the pattern even when the newsletter stayed within its agreed size. Keep the team that owns those automations involved in the ramp.

Choose the first audience by relevance and consent

Use recent subscribers whose relationship with the business supports the message. Preserve unsubscribe status, complaint exclusions and hard-bounce history when moving audiences or creating new data extensions. An old export is not automatically a suitable first campaign audience.

Group reporting by mailbox provider where the data supports it. A result dominated by one provider can hide trouble at another. For business domains, the visible address may not identify the receiving service, so avoid classifying every custom domain as Microsoft or Google without evidence.

Expand only when the completed feedback supports the next send. A smaller relevant audience is more useful than filling a daily target with people who did not expect the email.

Run a placement check through the campaign route

MailSlurp inbox placement testing supplies controlled provider addresses and reports where the marked message was observed. For Engagement, keep the test audience isolated using your account's normal supported audience mechanism, such as a dedicated sendable data extension configured by your administrator.

1. Create a fresh placement test and copy its current marker and all seed addresses.
2. Prepare a seed-only audience with the required subscriber and personalization fields.
3. Use the campaign content, From identity and delivery configuration planned for the launch.
4. Put the exact marker in the subject or body.
5. Verify exclusions and the final recipient count before sending only to the test audience.
6. Wait for completed results and compare the provider rows with the send's own delivery feedback.

Use a controlled campaign send when the editor's preview or test mode does not exercise the same routing or personalization. The MailSlurp placement instructions explain the marker and result states. Keep Engagement's IP configuration with the administrator while using MailSlurp to inspect the campaign's received results.

Interpret missing and poor results before increasing

• Seed excluded before sending. Check audience eligibility, subscriber state, exclusions and required fields.
• Send delayed or deferred. Review sending configuration, current ramp and provider feedback.
• Marker not present in received email. Inspect published content and the exact revision that was sent.
• Spam concentrated at one provider. Review that provider's received headers, authentication and sender history.
• Placement improved but complaints rose. Reconsider audience selection and production feedback before expansion.

Do not erase unresolved results from the review. A message that was not observed within the window needs investigation, not a guessed inbox classification. Our placement-rate guide explains how missing results affect comparisons.

Can another mailbox warm the Engagement IP?

Traffic builds history for the route that actually sends it. A separate Gmail or Microsoft 365 mailbox has its own path. MailSlurp's sender warmup product serves supported verified connections; use Engagement's process for its IP and MailSlurp to test the campaign delivered through it.

What should happen after the initial ramp?

Keep checking delivery and placement during bigger launches, seasonal peaks and provider migrations. If the audience or volume changes sharply, run a fresh placement test.

Check your Marketing Cloud campaign's placement with MailSlurp before it reaches the next, larger audience.