Custom newsletter sender email allows you to send newsletters from your own company email address instead of the default Frontify email domain.
This enhances brand consistency and improves email deliverability by using your organization's verified domain.
Contents:
Benefits of Newsletter custom sender email
Enhanced Email Deliverability
Configuring your own domain for newsletter sending significantly improves inbox placement rates. Without this setup, newsletters may be filtered into spam folders by recipient email servers, reducing the effectiveness of your communications.
Brand Consistency & Professional Communication
Sender addresses display your organization's domain, maintaining brand consistency.
Security & Control
All custom sender emails use industry-standard authentication protocols:
DKIMsignatures are automatically added to outgoing newslettersSPFvalidation ensures only authorized servers send on your behalfDMARCpolicies protect your domain from spoofing and phishing attempts
Newsletter Sender Email setup overview
In order to change the Newsletter sender email address, Frontify needs to verify your email domain with AWS.
There are two ways to configure your custom newsletter sender email:
Domain verification (recommended)
Verify your entire domain with a DNS record for maximum flexibility, scalability and security, and on brand experience.
For extra security, there is an option of a subdomain setup to isolate one sender email domain.
Email verification
Verify only a specific email address for quick setup with less scalability and on-brand feel.
Option 1: Domain verification (recommended)
Option 1: Domain verification (recommended)
Domain verification allows you to verify an entire email domain.
This requires DNS records to be added to your name servers - your IT team needs to be involved to complete this.
Advantages
Email deliverability: ensures all the recipients in your organization receive the emails and allows your IT team to whitelist the sender email.
Scalability: use different sender email address (e.g., brand@company.com, updates@company.com, etc.) that can be changed easily as long as the verified email domain (@company.com) stays the same.
Security: full control and enhanced setup options (as separate subdomain for newsletter emails)
On-brand look: The 'from' address is your dedicated sender email, no additional suffixes or confusing details.
Disadvantages:
Requires access to DNS
Extra option:
For enhanced security, you can set up a subdomain for emails from Frontify. This means your IT creates a separate email subdomain that can be used to send emails from Frontify, for example: @brand.company.com. This way, you are not verifying the entire corporate domain for newsletter sender setup, but only a specific subdomain. This might be important if you plan to send a lot of Newsletter updates and make sure that it does not impact the main email domain reputation from a security or deliverability perspective. To set this up, the process is the same but requires your IT team to set up the email subdomain first, and then inform us about it as described in the setup instructions below.
Option 2: Email verification (fallback option)
Option 2: Email verification (fallback option)
Email verification allows you to verify a single email address by clicking a confirmation link sent to that address. No DNS configuration is required.
This is a fallback option if you can't configure your DNS records.
We highly recommend going with Option 1, though.
Advantages
Quicker setup: verification completed by clicking a verification link sent over email that has to be set as a sender.
No DNS access needed
Only one email validated, not the entire email domain.
Disadvantages
'Via' suffix in the email: The 'from' address is suffixed with 'via amazonses.com'
Less professional & secure appearance: may reduce trust or brand perception
Single address only: each new sender email requires separate verification
Limited scalability: not ideal for multiple senders
FAQs & Limitations
What are the specifics of secure email authentication supported by Frontify?
DKIM (DomainKeys Identified Mail)
Frontify provides the required TXT or CNAME DNS records for DKIM. Once added to your DNS, these records allow emails sent from Frontify to be signed via AWS SES and verified by receiving mail servers.DMARC (Domain-based Message Authentication, Reporting & Conformance)
Since emails are sent using your company’s domain, your team is responsible for configuring the DMARC record according to your internal email policies. Frontify cannot define a recommended DMARC policy, as we do not have visibility into all other systems that may send emails from your domain.SPF (Sender Policy Framework)
No additional SPF record is required for Frontify emails. Messages are sent using an@amazonses.comenvelope sender, which is already authorized by AWS.
Known limitation:
Changing the newsletter email sender is only possible at the level of your whole instance. This means each instance can have only one designated sender email domain. If you have sub-accounts, those can't have their own newsletter sender email domain.
How to request the implementation of custom Newsletter sender email
Reach out to your Customer Success Manager to initiate the process. Your CSM will inform you about the typical process and request the setup internally.
Customer Support will handle the implementation directly with your IT contact and will keep your CSM updated once the new sender email is in place.
Setup process overview
Contact your CSM to inform us about desired email address or email domain and verification option of your choice.
Support sends DNS records needed for email domain validation
Your IT team creates records on your end
Once verified, emails can be sent using any email address with that domain