Learn how to customize the sender for your email notifications in the Joy Loyalty Program. Use our shared domain or configure your own SMTP, with options like Amazon SES.
Introduction to Email Sender Customization
Email sender customization is your opportunity to extend your brand's professional identity directly into your customers' inboxes. It's more than just a technical setting – it's a communication strategy.
Why do you need to customize the sender for your email notifications?
Customizing the sender of your email notifications is a great way to reinforce your brand and ensure consistent communication with your customers. With Joy, you can either use a custom sender email through our shared domain or configure your own SMTP for complete control over your email delivery.
How to customize the sender for your email notifications
This guide will walk you through setting up both options, allowing you to tailor your email sender settings to best suit your business needs.
Verify sender
Even if you use a shared domain or custom SMTP, you both need to verify that your email sender is a valid email address. First, fill in the email address and the name of the sender (which shows in the email).

Click on the Verify button to send a verification email to your email address > check your mailbox and find the verification email.

Re-check the email status in Settings> Enable to activate the new email sender.

Custom sender with our shared domain
Once you verify your custom sender, by default, you will be sending emails via our shared domain. When using our shared domain send.avada.io, you can customize the display name and email address. This allows you to easily manage email communication without the need for a complex setup. However, because the sending domain will be send.avada.io, SPF alignment won’t be possible if your custom email domain differs from ours. Despite this, our domain has a strong reputation for reliable delivery.
Custom sender with your own STMP
For full control over your email delivery and authentication, you can configure your own SMTP server. This option allows you to send emails directly from your own domain, ensuring SPF and DKIM alignment for better email authentication.
Recommended SMTP services:
Amazon SES: A highly scalable and cost-effective option for sending transactional emails.
SendGrid: Known for its reliable delivery and user-friendly interface.
Mailgun: Great for developers who need flexibility and detailed analytics.
Google Workspace SMTP: Ideal if you already use Google Workspace for business email.

For ease of setup and reliable delivery, using our shared domain is a great option. However, if you want full control over email authentication and domain alignment, configuring your own SMTP server—such as Amazon SES or SendGrid—will provide that flexibility.
Wrap up
Customizing your email sender helps reinforce your brand and ensure reliable communication. Whether you choose Joy’s shared domain for simplicity or your own SMTP for full control and authentication, both options allow you to tailor email delivery to your business needs. Verify your sender, set up the configuration, and start sending branded, professional emails your customers can trust.
FAQs
What if my email provider is not on your provider list?
It is okay. The list is just a template for you to start more easily. If your SMTP provider gives you a host, port, username, and password, then you can just fill them in. Then you are good to go.
Why cannot I see my test email in the inbox or spam box, even though I added the customer sender as verified in your app?
Most of the time, it is because your domain already has an SPF record. Our email was sent using the shared domain of our app, with the from sender is your domain. But if the sender domain (from domain) has a strict SPF like v=spf1 include:_spf-eu.ionos.com ~all
then our email would be unauthenticated. You can go to MX toolbox, use the SPF tool to check your domain's SPF record:

In order to allow our app to send the email on your behalf, please add our domain mailgun.org to your existing SPF record, like: v=spf1 include:_spf-eu.ionos.com include:mailgun.org ~all
Last updated
Was this helpful?