Skip to main content

How to set up a custom email sender domain

Send customer notification emails from your own domain instead of the default Clay sender

S
Written by Shubham Nandeshwar

Send customer notification emails from your own domain instead of the default Clay sender.

Overview

By default, customer notification emails sent by Clay: B2B Wholesale come from a generic Clay sender address. Setting up a custom email domain lets those emails come from an address on your own domain (for example, noreply@examplestore.com), which improves deliverability and looks more professional to your wholesale customers.

Clay uses Brevo to send transactional email. To prove that your domain is allowed to send mail through Brevo, you add four DNS records (two DKIM CNAME records, one Brevo TXT verification record, and one DMARC TXT record) to your domain provider. Once those records are in place, Clay verifies them and starts sending from your domain automatically.

What you will need

  • Admin access to your Shopify store and the Clay: B2B Wholesale app.

  • Access to the DNS settings for the domain you want to send from (Cloudflare, GoDaddy, Namecheap, Shopify domains, Route 53, etc.).

  • About 10 minutes to add the records, plus up to 24 hours for DNS propagation (usually much faster).

At a glance

  1. Open the Email domain page in the app and submit your domain and sender details.

  2. Copy the four DNS records Clay generates and add them at your domain provider.

  3. Wait for verification. Once active, all customer notifications will be sent from your sender address.

⚠️ Heads up — use the same domain everywhere. The sender email must be on the domain you entered above (for example, if your domain is examplestore.com, your sender email must end in @examplestore.com). You cannot use a free email service like gmail.com or outlook.com as the sender domain.

Step 1: Enter your domain and sender details

In your Shopify admin, open the Clay: B2B Wholesale app and go to Settings → Email domain. You will see the setup form.

  1. Domain — enter the bare domain you want to send from, with no protocol or path. For example: examplestore.com. Do not include https:// or a trailing slash.

  2. Sender email — the address customer notifications will be sent from. It must use the domain you entered above. A common choice is noreply@examplestore.com or orders@examplestore.com.

  3. Sender name (optional) — the friendly name customers see in their inbox next to the sender address. If you leave this blank, your store name is used.

  4. Click Set up custom domain. Clay will create the records you need at Brevo and take you to the DNS records page.

💡 Tip. Most stores use a dedicated subdomain for transactional mail (for example send.examplestore.com or mail.examplestore.com) so that the DNS records do not affect the email setup of the rest of the company. Either approach works — pick whichever fits your existing email setup.

Step 2: Add the DNS records to your domain provider

After you submit the form, Clay shows four DNS records that you need to add at your domain provider: two DKIM CNAME records, a Brevo TXT verification record, and a DMARC TXT record. Each record has a Type, a Host / Name, and a Value. Use the Copy buttons next to each value to avoid typos.

The records you need to add

The exact values shown in your app will use your own domain. The format is summarised below:

Field

Value

DKIM 1 — Type

CNAME

DKIM 1 — Host / Name

brevo1._domainkey

DKIM 1 — Value

b1.examplestore-com.dkim.brevo.com

DKIM 2 — Type

CNAME

DKIM 2 — Host / Name

brevo2._domainkey

DKIM 2 — Value

b2.examplestore-com.dkim.brevo.com

Brevo verification — Type

TXT

Brevo verification — Host / Name

@

Brevo verification — Value

brevo-code:<unique code shown in the app>

DMARC — Type

TXT

DMARC — Host / Name

_dmarc

DMARC — Value

v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com

How to add them

  1. Open the DNS settings for your domain at your registrar (Cloudflare, GoDaddy, Namecheap, Shopify Domains, AWS Route 53, etc.).

  2. Add a new record for each row above. Match the Type, paste the Host / Name into the Name (or Host) field, and paste the Value into the Value (or Target) field.

  3. For the TXT record, the Host / Name is @ which means "the domain itself" (sometimes shown as the bare domain name in your registrar UI).

  4. Save each record. If your registrar asks for a TTL, you can leave it at the default (usually 1 hour or "Auto").

  5. Back in the app, click Authenticate domain. Clay will check the records with Brevo. If you need to start the setup over, use Start over to clear the current configuration.

Common pitfalls

Some registrars automatically append your domain to the Host / Name. If you paste brevo1._domainkey and the registrar saves it as brevo1._domainkey.examplestore.com.examplestore.com, remove the duplicated domain.

Do not wrap the values in quotes. The Value should be the bare hostname for CNAMEs and the bare verification string for the TXT record.

Step 3: Wait for verification

Once the records are saved at your registrar, Clay will check them in the background. DNS changes usually propagate within a few minutes, but they can take up to 24 hours. You do not need to keep the page open — refresh the Email domain page after a few minutes to see the current status.

When verification succeeds, the page changes to the confirmation view, and customer notification emails will start being sent from your sender address.

What happens after activation

  • Customer notification emails (such as form submissions, group changes, and approval emails) are sent from your sender email and display your sender name.

  • Replies from customers go to the sender address you configured. Make sure that mailbox is monitored, or use a noreply address and tell customers how to reach you in the email body.

  • You can change the sender name at any time. To change the domain or sender email, remove the current setup and run through the steps again.

Removing the custom domain

If you ever want to revert to the default Clay sender, click Remove custom domain on the Email domain page. After confirmation, future customer notifications will be sent from the default address until you set up a new domain.

Troubleshooting

Verification is taking a long time

DNS propagation can take up to 24 hours, but is usually much faster. Refresh the Email domain page periodically. If you are still not verified after a few hours, double-check that each record at your registrar exactly matches the Host / Name and Value shown in the app.

My registrar appended the domain to the host

Some registrars automatically append your domain to CNAME and TXT host fields. If you see something like brevo1._domainkey.examplestore.com.examplestore.com in your records list, edit the record and remove the duplicated domain so it ends in just .examplestore.com.

I get an "invalid domain" error when submitting the form

The Domain field expects only the bare domain — no https://, no www., and no trailing slash. Use examplestore.com, not https://www.examplestore.com/.

You already have a DMARC record on the domain

A domain can only have one DMARC record. If your domain already has a DMARC record at _dmarc, adding a second one will cause both to be ignored and authentication will fail. Check your DNS records first:

  • If you find an existing DMARC record with only v=DMARC1; p=none; (the "do nothing" default), it is safe to delete and replace it with the value Clay shows in the app.

  • If you find a stricter DMARC record (for example one with p=quarantine or p=reject, or one with existing rua= reporting addresses), do not blindly overwrite it. Coordinate with whoever owns email at your company before changing it, since DMARC affects all mail sent from the domain — not just Clay's notifications.

After resolving the duplicate, click Authenticate domain again to re-check.

I want to use a subdomain

You can. Enter the subdomain you want (for example send.examplestore.com) as the Domain. The DNS records will then be added under that subdomain — for example, the DKIM 1 host becomes brevo1._domainkey.send at your registrar (the registrar will append the rest of the domain).

Still stuck?

Reach out to Clay support from the in-app help widget at the bottom-right of the admin, and include a screenshot of the Email domain page along with the records you added at your registrar. Support can verify that the records look correct and trigger a manual re-check.

Did this answer your question?