Loading

Marketing Cloud Next - Issues Sharing Email Sending Domains between Marketing Cloud Account Engagement and Marketing Cloud Next

Fecha de publicación: Oct 16, 2026
Descripción
This article addresses situations where you use Marketing Cloud Account Engagement and are setting up Authenticated Domains for email sending in Marketing Cloud Next. 
Solución

There are two options for Account Engagement customers who are trying to send email with Marketing Cloud Next. 

 

Option 1 (recommended): Use a separate unique subdomain

  1. Choose a unique subdomain that Account Engagement doesn't use, for example a new subdomain of your main domain.
  2. In Marketing Cloud Next, go to Setup and create a new Authenticated Domain with that subdomain.
  3. Add the DNS records Marketing Cloud Next provides to your DNS provider.
  4. Verify and activate the domain in Marketing Cloud Next.



Option 2: Share the same domain

Please note that even if you use the same domain in Marketing Cloud Next that was previously used in Marketing Cloud Account Engagement, a warming period is still recommended because the IP addresses that the emails originate from will not be the same.

Below are some scenarios if you are attempting to use the same domain for email sending in both Marketing Cloud Account Engagement and Marketing Cloud Next. You may run into issues in these situations if your Account Engagement setup uses a custom return path.

 

If your Account Engagement setup does not use a custom return path during email sending

You can set up the same authenticated domain in Marketing Cloud Next and use it in both products.

 

If your Account Engagement setup uses a custom return path during email sending

Salesforce recommends using Option 1; use a unique subdomain for Marketing Cloud Next.

If you are not sure if you're using a custom return path, you can double check if you have a custom return path in a few ways:

  1. Check the email headers on emails being sent from Account Engagement and validate what domain shows up in the "envelope-from" address
    1. Domains that look like "bounce.s7.exacttarget.com -or- bounce.s10.mc.pd25.com -or- bounce.j.s11.pdmailservice.com" are not customized. 
  2. Review all your sending domains and see if there are records in both these locations (example assumes your sending domain is bounce.mysendingdomain.com)
    1. TXT record - this will be pointing at an SPF record that looks like "v=spf1 include:cust-spf.exacttarget.com -all"
    2. MX record - this will be pointing at something that looks like "bounce.s13.exacttarget.com"
  3. By reviewing old support cases to see if you've requested this before and/or contacting Account Engagement support to confirm if you have custom return path active.

If your business requires that you must use the same domain in Marketing Cloud Next as you used in Marketing Cloud Account Engagement, please note that we do not currently support simultaneously sending email using the same domain on Marketing Cloud Next and Marketing Cloud Account Engagement when a custom return path is used for Account Engagement email sending. 

You are able to use the same email sending domain if you stop Account Engagement email sending prior to setting up the same domain in Marketing Cloud Next. Use these instructions: 

  1. Add the the same authenticated domain in Marketing Cloud Next
    1. This will give you visibility into the DNS records required to authenticate your domain Marketing Cloud Next. 
    2. NOTE: do NOT add the DNS records at this time. Doing so will impact your ability to send authenticated email from Marketing Cloud Account Engagement.
  2. Once you are ready to start sending email from Marketing Cloud Next, stop all sending email from Account Engagement before you set up the domain in Marketing Cloud Next.
    1. It would be highly recommended to delete the email sending domain in Account Engagement to prevent errant sending, as those emails would not be properly authenticated any longer.
    2. Alternatively, you can devise other methods from preventing your emails from using that domain in Account Engagement any longer.
  3. Once Account Engagement emails have been stopped, update your DNS records and authenticate the same domain in Marketing Cloud Next.
    1. Be aware that late asynchronous bounces from earlier Account Engagement sends may not be processed correctly.
    2. Note that you must keep all 8 CNAME records for Marketing Cloud Next in place even after you activate the authenticated domain in Marketing Cloud Next. Failure to do so can prevent your email from sending and/or cause you send email that is not authenticated properly (which will result in email deliverability issues). 
Número del artículo de conocimiento

005461741

 
Cargando
Salesforce Help | Article