Why is the From Email Address showing instead of From Name in SFMC?

Key findings

• Client-side rendering: The way the 'From' information is displayed is heavily dependent on the recipient's email application (client), which may prioritize the email address over the friendly name.
• Email authentication: Strong email authentication (SPF, DKIM, DMARC) plays a role in building trust, which can influence how a mail client displays sender details. If authentication is weak or failing, some clients might default to showing the email address to flag potential spoofing.
• Recipient's address book: When a sender's address is saved in the recipient's address book, email clients are more likely to display the preferred 'From Name'.
• Header inspection: Verifying the actual email headers can confirm whether both the 'From Name' and 'From Email' are correctly included at the sending stage.

Key considerations

• Sender profile configuration: Ensure your SFMC sender profile and send classifications are correctly configured with the desired From Name and From Email.
• Email client variations: Understand that different email clients (e.g., Gmail, Outlook, Apple Mail) may render the 'From' field differently, even when correctly configured.
• Personalization: Consider implementing dynamic sender profiles for more granular control over sender display based on recipient data.
• Troubleshooting: If the issue persists, investigate whether email authentication issues or specific recipient client settings are at play.

Key opinions

• Client-side behavior: Many marketers find that the display is largely controlled by the email application the recipient uses, which can override sender preferences.
• Configuration checks: Initial troubleshooting often involves re-checking send classifications and sender profile settings within SFMC.
• Address book impact: A common observation is that once the sender is added to the recipient's address book, the friendly From Name typically appears as intended.
• Authentication role: Some marketers suspect that strong email authentication and sender reputation can influence whether the friendly name is displayed consistently.

Key considerations

• Comprehensive setup: Beyond sender profiles, ensure other SFMC elements like delivery profiles and sender authentication packages are correctly implemented.
• Testing across clients: Always test emails across a variety of email clients and devices to see how the From Name renders in different environments.
• Org-wide email addresses: If using Salesforce for general email, ensure org-wide email addresses are set up to properly handle display and replies.
• Best practices: Adhering to sender email address best practices can improve overall deliverability and display consistency.

Key opinions

• Authentication importance: Experts agree that robust email authentication (SPF, DKIM, DMARC) is foundational for instilling trust with email clients, thereby increasing the likelihood of the friendly From Name being displayed.
• Client-specific rules: Many email clients have proprietary algorithms that determine how sender information is rendered, often prioritizing security and sender reputation over a specified friendly name.
• Header integrity: It is critical that the email headers themselves contain both the friendly From Name and the From Email Address for the client to even have the option to display the name.
• Anti-abuse measures: Some clients may intentionally hide the friendly From Name until a sender is whitelisted or added to contacts, as an anti-phishing mechanism.

Key considerations

• DMARC policy: Ensure your DMARC policy is correctly implemented and aligned, as a strict policy can impact how your sender details appear. Get a simple guide to DMARC.
• Sender reputation: Maintain a high sender reputation, as mail clients are more likely to trust and display the friendly From Name for reputable senders. Learn why Gmail may show your email address.
• Header verification: Always examine the full email headers of received messages to diagnose whether the From Name is correctly present before delivery to the inbox. More details are available on the Trailhead community.

Key findings

• Sender profile purpose: SFMC documentation confirms that the 'From Name' in a sender profile is designed to be the friendly displayed name for recipients.
• Org-wide addresses: Salesforce allows for sending from aliases (org-wide email addresses), which are distinct from individual user emails and affect how the sender is presented.
• Reply-to behavior: Using an individual user in the 'From Name' can lead to replies not routing correctly, which implies a system preference for a consistent, formal 'From Email'.
• Dynamic content: Documentation shows that sender details can be dynamically personalized based on data extensions, providing flexibility in display.

Key considerations

• Standard terms: Familiarize yourself with the standard terms for friendly From fields and sending domains to ensure accurate configuration.
• Authentication alignment: Pay attention to how SPF and other authentication protocols interact with your sender addresses, especially if return paths and sender From addresses differ.
• System settings: Be aware that certain system-level configurations, like using a no-reply email address, might inherently display the email address rather than a name.