Below are some frequently asked questions about the Dynamic From/Reply feature.
Yes. The feature resolves From and Reply-To addresses per recipient at send time, based on the provided
No. The feature cannot dynamically build or transform email addresses at send time (e.g., converting a.w@domain.com → a.w@my.domain.com). This is a common request for customers whose CRM User records contain root domain addresses but want to send from an authenticated subdomain address.
There two options for this use case:
jsmith@mktg.example.com) which can be selected in the Dynamic From Address field selector, as long as that subdomain is configured as an Authenticated Domain in Unified Messaging > Email > Authenticated Domains.No — but domain authentication is required. The sender (From) address must use an Authenticated Domain, but the full address does not need to pre-exist in CRM. Similarly, the Reply-To address must contain an Authorized Domain, but the full address does not need to exist in the Data Graph or CRM.
Yes, depending on the use case. Multiple authenticated sending domains can be supported within the same Flow/send activity. However, dynamic construction of domain-transformed addresses is not supported (see above).
Yes. Emails can be configured so that replies go back to the assigned sales representative's email address, as long as the correct email can be mapped in CRM and/or via the Data Graph, and the sales rep's email address domain is set up as an Authorized Domain.
As of Summer '26 release, Marketing Cloud Next supports per-recipient From/Reply addresses resolved from CRM/Data Graph, but does not support AMPScript-style domain transformation at send time. The recommended path is:
Currently when running the flow in Debug Mode, the dynamic from and dynamic reply will not resolve correctly and will always use a fallback. You must activate the flow normally to determine if the dynamic from and dynamic reply resolve as expected.
Currently when using the Preview and Test feature, the dynamic from and dynamic reply will not resolve correctly. The test email will send from the From Name and Address specified on the Preview and Test pop-up and the reply will be the standard Reply Mail Management address.
SELECT "ssot__SendtimeEmailAddress__c", "ssot__EmailFromName__c", "ssot__EmailFromAddr__c", "ReplyToName__c", "ReplyToAddress__c", "ssot__BulkEmailMessageId__c", "ssot__IndividualId__c", "ssot__EmailRecipientSendStatus__c", "ssot__EngagementActionReasonText__c", "ssot__EngagementChannelActionId__c", "ssot__EngagementChannelId__c", "ssot__EngagementChannelTypeId__c", "ssot__EngagementDateTm__c", "ssot__FlowElementRunId__c", "ssot__Id__c", "ssot__RecipientMessageId__c" FROM "ssot__EmailEngagement__dlm"
WHERE"ssot__EngagementDateTm__c" >= TIMESTAMP '2026-07-01 00:00:00.000Z'AND "ssot__EngagementDateTm__c" < TIMESTAMP '2026-07-02 00:00:00.000Z'
AND "ssot__SendtimeEmailAddress__c" = 'recipient@customer.com'
ORDER BY "ssot__EngagementDateTm__c" ASC LIMIT 100
The below table provides a few specific scenarios to better understand behavior for From Address when either Dynamic Display Name or Dynamic From Address are used. The example assumes that you have:
marketing.example.com set up as an authenticated domain
example.com is NOT set up as an authenticated domain.
|
Scenario |
What You Provide |
Fallback Configured |
What the Recipient Sees |
|
Dynamic Display Name + Static From Address |
John Smith |
N/A |
John Smith |
|
Dynamic Display Name pointing toward an empty/null field + |
<static@marketing.example.com> |
N/A |
Marketing |
|
Dynamic Display Name + |
John Smith |
Marketing <fallback@marketing.example.com> |
Marketing <fallback@marketing.example.com> |
The below table provides a few specific scenarios to better understand behavior for Reply Address when either Dynamic Display Name or Dynamic Reply Address are used. The example assumes that you have:
marketing.example.com set up as an authorized domain
example.com is NOT set up as an authorized domain.
|
Scenario |
What You Provide |
Fallback Configured |
What the Recipient Sees |
|
Dynamic Display Name + Dynamic Reply Address with a domain that is not authorized |
Mary Jones |
<replyfallback@marketing.example.com> |
<replyfallback@marketing.example.com>
|
|
Dynamic Display Name pointing toward an empty/null field |
<mary@marketing.example.com> |
<replyfallback@marketing.example.com> |
<replyfallback@marketing.example.com>
|
005393499

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.