Salesforce sends at scale. Your domain still has to earn the inbox.
Marketing Cloud authenticates a private sending domain with SPF, DKIM and DMARC, and offers dedicated IPs for larger senders. Salesforce is clear that a new dedicated IP is warmed by the sender, and a new domain starts with no history either. Keep your journeys and sends exactly where they are. Add the domain here and we build its reputation while Salesforce keeps sending.
Keep sending from Salesforce. Warm the domain here.
Authenticate a private domain in Marketing Cloud
Without a Private Domain or the Sender Authentication Package (SAP), Marketing Cloud Engagement sends on Salesforce-operated domains rather than yours. A Private Domain adds SPF, DKIM and DMARC for your sending domain; SAP bundles it with a dedicated IP, link branding and reply mail management.
Know what Salesforce warms, and what it does not
Salesforce says there is no such thing as a pre-warmed IP: a new dedicated IP is warmed by the sender, raising volume gradually and pausing if engagement drops. That guidance is about the IP. The domain carries its own reputation, and on shared IPs it is the only one that is yours.
Add your brand domain to Inbox Boost
Use the domain in your From address, yourbrand.com. Any private sending subdomain you set up in Marketing Cloud stays with Salesforce. We set up what it needs and build its sender reputation. Nothing to connect to Salesforce: no API key, no connected app, no change to your account.
Keep every journey and send running in Salesforce
Journeys, triggered sends, newsletters: all of it stays in Marketing Cloud. Mailbox providers score the domain in your From address, so the reputation built here counts for every Salesforce send from yourbrand.com.
Check where Salesforce mail lands
Inbox placement tests show whether your sends reach Primary, Promotions or Spam across the major mailbox providers, and blacklist monitoring keeps watching the domain once it is warm.
- Nothing to connect: no Salesforce API key, connected app or package
- Nothing to change: journeys, data extensions and templates stay exactly as they are
- Shared or dedicated IP: it works either way, because the reputation belongs to the domain
- Watched after warmup: blacklist and authentication monitoring on your brand domain
The parts of the platform this plan leans on.
A Salesforce domain, warmed without pausing a single send.
Four checkpoints, in order. Click any step or let it play.
Salesforce questions, answered.
Does Inbox Boost connect to my Salesforce account?
I have a dedicated IP in Marketing Cloud. Why warm the domain too?
I am on Marketing Cloud’s shared IPs. Does this still help?
Do I need a Private Domain or SAP first?
Can I see whether it is working?
Checked against Salesforce's own documentation on 12 October 2026. Salesforce is a trademark of its owner; SenderSignal is not affiliated with it.
- Salesforce: Working with the Email Sender Authentication Package
- Salesforce: Private Domain DKIM, SPF and DMARC authentication FAQ
- Salesforce: Marketing Cloud Engagement dedicated IP and shared IP use policy
- Salesforce: Sending reputation and warming
- Salesforce Trailhead: Set yourself up for successful deliverability
Other crm & all-in-one: HubSpot, GoHighLevel, Zoho, Pipedrive, Keap. All use cases.
Warm the domain behind your Marketing Cloud sends.
Start free, add the domain, and keep every journey running in Salesforce while its reputation builds.