Before you add your domain, we recommend that you first do the following:
If you’re adding your very first domain, note that email setup is a three-part process where you add your domain, configure your DNS records, wait for it to be verified, and then add your email addresses.
Remember that newly added domains will carry an “Unverified” status during the setup process until your DNS provider can confirm your domain SPF and DKIM records.
You only need to add a particular domain once unless you have another domain to add.
Watch Out – Use lowercase letters only when adding Email domain(s)
When using Email domain(s) please use only lowercase letters. If you accidentally add an Email domain with uppercase letters, contact Gladly Support with a P4 designation to assist you with updating the domain. This will also change the DKIM & SPF records you will need to install.
Before proceeding to add a new domain, remember that a domain cannot be deleted or changed once added.
From the Add a sending domain to get started with email prompt, enter your domain name (e.g., retale.com) and click Save and Continue.
Next, you’ll be asked to update your DNS records using the SPF and DKIM values in this section.
[A] – SPF: Copy and paste this value into your domain provider’s DNS setting as TXT type.
[B] – DKIM: Copy and paste this value into your domain provider’s DNS setting as TXT type.
Go to your DNS provider’s DNS settings page in a new browser tab and paste the SPF and DKIM as TXT (type) values you copied from Gladly. This step is required to verify your domain. We’re unable to see which DNS provider you have, so below is a list of several common providers with a link on how to update the SPF and DKIM records:
Once your DNS records are updated, return to Gladly and click Next.
You’ll see a notice stating you must wait for your DNS provider to confirm the SPF and DKIM records you added, which can take up to 72 hours. Until it’s approved, the domain will have an “Unverified” status.
Unverified – The DNS records for your sending domain have not been verified and updated.
Verified – The DNS records have been verified, and the domain is ready for use.
Click Add Another Domain to add another domain. Otherwise, click Done. This will take you back to the Email screen. You should now see the domain you added with an “Unverified” status.
Check back in 72 hours to see if the SPF and DKIM records have been verified. Once verified, SPF and DKIM should have a “Verified” status. Now, you can add email addresses associated with the added domain.
Tip – You only need to set up a domain once
Once a sending domain is added (e.g., @retale.com), you can add related email addresses like [email protected] or [email protected]. You only need to set up a new domain if you want to add email addresses containing a different sending domain (e.g. retale.biz instead of retale.com).
To view a list of existing domains, click on the Domains tab.
Enter your domain name (e.g., retale.com) and click Save and Continue.
Note – Domain name can’t be changed once saved.
Next, you’ll be asked to update your DNS records using the SPF and DKIM values in this section.
[A] – SPF: Copy and paste this value into your domain provider’s DNS setting as TXT type.
[B] – DKIM: Copy and paste this value into your domain provider’s DNS setting as TXT type.
Go to your DNS provider’s DNS settings page on a new browser tab and paste the SPF and DKIMTXT (type) values you copied from Gladly. Since we’re unable to see which DNS provider you use, here’s a list of several common providers with instructions on how to update the SPF and DKIM records:
Once your DNS records are updated, return to Gladly and click Next.
You’ll see a notice stating you must wait for your DNS provider to confirm the SPF and DKIM records you added, which can take up to 72 hours. Until these records are verified, the domain will have an “Unverified” status.
Unverified – The DNS records for your sending domain have not been verified and updated.
Verified – The DNS records have been verified, and the domain is ready for use.
Click Done. This will take you back to the Email screen. You should now see the domain you added with the “Unverified” status.
Check back in 72 hours to see if the SPF and DKIM records have been verified. Once verified, SPF and DKIM should have a “Verified” status. You can then proceed to add email addresses associated with the domain.
Once the domains are set up, contact Gladly Support to set up the reply-to address.
Once the sending email domain is set up, create a reply-to email address so that replies are sent to the desired reply-to address regardless of the domain address used to send outbound emails. For example, suppose outbound emails will technically come from [email protected], the reply-to address can be set so replies are sent to [email protected] instead.
Contact Gladly Support to set up the reply-to address. Once the reply-to address is set up, set up email forwarding using the Gladly-generated address, so email replies are forwarded to Gladly.
You can manually check the status of your SPF and DKIM records by forcing an update request.
From the Email page, hover over the domain you want to check the status and clickon the right side of the domain, then click Check Verification Status.
Wait a few seconds, and you’ll see a message either showing if the records have been verified or are still waiting to be verified. Verifying the domain may take up to 72 hours, even if you request an update.
If you already have an existing SPF record for your domain, you can append the Gladly provided SPF record to the existing record. The SPF recording should follow the format below.
Be sure that v=spf1, include:mailgun.org, and -all exist in your SPF record by appending what is needed.
Configure DMARC to prevent phishing and spoofing #
Domain-based Message Authentication, Reporting, and Conformance (DMARC) helps protect against phishing and spoofing while preventing messages from being marked as spam.
You can use tools like mxtoolbox and dmarcian first to confirm if DMARC Policy and Reports are already set up for your domain. If not, see instructions below from popular providers on how to set up DMARC.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__cf_bm
29 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_wpfuuid
1 year 1 month 4 days
This cookie is used by the WPForms WordPress plugin. The cookie is used to allows the paid version of the plugin to connect entries by the same user and is used for some additional features like the Form Abandonment addon.
BIGipServer*
session
Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category.
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
PHPSESSID
session
This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
li_gc
5 months 27 days
Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
1 year 1 month 4 days
Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_gd_session
4 hours
This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded.
_gd_visitor
1 year 1 month 4 days
This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads.
_sp_id.*
1 year 1 month 4 days
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
_sp_ses.*
30 minutes
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
AnalyticsSyncHistory
1 month
Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie.
mf_user
3 months
Mouseflow sets this cookie to identify whether a visitor is new or returning.
vuid
1 year 1 month 4 days
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
_mkto_trk
1 year 1 month 4 days
This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo.
bcookie
1 year
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.
bscookie
1 year
LinkedIn sets this cookie to store performed actions on the website.
li_sugr
3 months
LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant.