Sending domains and authentication

Before email goes out, you set up a trusted sending identity: a physical address for the org, an authenticated sending domain, approved from addresses, and branded links.

Steps

• Add your organisation's physical mailing address. It is legally required in most regions and is used in the footer.
• Authenticate a sending domain by publishing the DNS records Salesforce gives you.
• Add the from addresses people are allowed to use on that domain.
• Brand the tracked links so they use your domain instead of a generic one.

Already on Marketing Cloud Engagement?

The implementation guide describes a unified messaging domain, and reply mail management can be configured for it. In practice this means teams running both products can work from the same authenticated domain rather than setting up a second one.

Needs confirmation: the exact steps for reusing an Engagement domain depend on your edition and release. Check with your Salesforce contact before changing DNS.

Gotchas

• DNS changes can take hours to verify. Plan for it.
• Bulk senders must meet inbox provider rules on authentication and one-click unsubscribe.