This guide shows BigCommerce store owners how to add the WiserReview email authentication records (DKIM, SPF, and MX) directly inside BigCommerce. BigCommerce hosts your DNS by default, so you add these records in the store admin instead of an external DNS provider like Cloudflare or GoDaddy.
WiserReview gives you 6 records in two groups: 4 DKIM records (1 TXT and 3 CNAME) and 2 SPF records (1 MX and 1 TXT). Five of them go on the BigCommerce Web Hosts tab, and the MX record goes on the Mail Servers tab.
Before you start, verify your sender email in WiserReview first. The steps below walk through it, and you can also read the Email Sender DKIM/SPF Setup Guide for the general version.
Step 1: Get Your DNS Records From WiserReview
In your WiserReview dashboard, go to Settings → Email Sender and choose Configure and verify your own store email. This screen has three parts:
- Enter email: Type the address you want to send review requests from, such as
[email protected]. Use a domain-based email, not Gmail or Outlook. - Verify email: Amazon SES sends a verification email to that address. Open it and click the verification link to confirm you own the inbox.
- Configure DNS: WiserReview then shows the 6 DNS records, split into a DKIM group and an SPF group. Keep this screen open, you will copy each value into BigCommerce.
The Name and Value on this screen are unique to your account. Always copy your own records from here. Do not reuse the values in the screenshot.
Step 2: Open Email & DNS Records in BigCommerce
Log in to your BigCommerce store admin and go to Settings. Scroll to the Domain section and click Email & DNS records.
Step 3: Add the DKIM and SPF Records on the Web Hosts Tab
At the top of the Email & DNS records page, click the Web Hosts tab. This tab holds CNAME and TXT records, which is 5 of your 6 records: the 1 DKIM TXT, the 3 DKIM CNAME, and the 1 SPF TXT.
When you copy from WiserReview into BigCommerce, the columns line up like this:
- WiserReview Name goes into the BigCommerce Fully Qualified Host field
- WiserReview Value goes into the BigCommerce Value field
Click Add another for each record and add all five:
- DKIM TXT (1): Type
TXT, host like_amazonses.yourstore.com, value is the long quoted string from WiserReview - DKIM CNAME (3): Type
CNAME, host ends in._domainkey.yourstore.com, value ends in.dkim.amazonses.com - SPF TXT (1): Type
TXT, host is the MAIL FROM subdomain such aswr.yourstore.com, valuev=spf1 include:amazonses.com -all
Leave Time to live at the default. Copy and paste each value exactly, with no extra spaces.
Step 4: Add the MX Record on the Mail Servers Tab
The sixth record is an MX record, and it goes on the Mail Servers tab, not Web Hosts. Click the Mail Servers tab and select “I’m setting up an external email hosting solution.” This shows the MX record table.
Click Add another and add the MX record from WiserReview:
- Set Type to
MX - In Fully Qualified Host, enter the MAIL FROM subdomain such as
wr.yourstore.com - In Value, enter the mail server shown in WiserReview, such as
feedback-smtp.ap-south-1.amazonses.com(your region may differ, so copy what WiserReview shows) - Set the Priority to
10
This MX sits on the dedicated wr. subdomain, so it does not affect your main domain’s existing email. Any MX records you already use for your inbox (for example, Google Workspace) stay as they are. Save your changes.
Step 5: Check Verification in WiserReview
- Return to the WiserReview Configure DNS screen and click Check status.
- Each record moves from Pending to verified once it is detected.
- BigCommerce DNS changes are usually fast, but full propagation can take a few minutes. Until everything is verified, WiserReview keeps sending from the default address.
Tips
- The records split across two tabs: 5 TXT and CNAME records on Web Hosts, and 1 MX record on Mail Servers.
- Copy each value one by one and check for trailing spaces, which are the most common cause of a failed check.
- The SPF and MX records use a dedicated subdomain (such as
wr.yourstore.com), so they do not touch the email setup on your main domain. - Use dnschecker.org to confirm each record is live before you re-check status.