Setting up your sending domain

Your campaigns and automations go out from your own subdomain, such as mail.yourcompany.com. Emails are signed as you, so the sending reputation is yours alone.

1. Add a subdomain

Go to Settings › Email and add a domain under Sending domain.

• Use a subdomain, such as mail.yourcompany.com or news.yourcompany.com.
• Don't use the root domain your company mailboxes are on. UserSignal refuses a domain that already receives email.

2. Add the DNS records

UserSignal shows the records to add where your domain's DNS is managed (Cloudflare, GoDaddy, Namecheap and so on):

• Three CNAME records that sign your emails (DKIM).
• An MX and a TXT record on a subdomain of your sending domain, used to process bounces.

Copy each one exactly as shown. If you use Cloudflare, switch the proxy off (grey cloud) for these records.

3. Wait for verification

UserSignal checks every 10 minutes for up to 72 hours. You can also press Check now. The status changes from Waiting for DNS to Verified. Keep the records in place afterwards: removing them stops your sending.

4. Choose your sender

• From name — what people see in their inbox.
• From address — an address on your verified domain, such as news@mail.yourcompany.com.
• Replies go to — a mailbox your team reads. The sending subdomain itself receives no mail.
• Postal address — optional. When set, it is shown in every email's footer. Anti-spam law asks for one in some countries, the United States among them.

5. Add DMARC

Gmail and Yahoo require a DMARC policy from bulk senders. If your main domain has none, Settings › Email shows the record to add. A policy of p=none changes nothing about delivery; it only lets mailbox providers check your mail.

Warm-up

A new sending domain earns trust by starting small: 1,000 emails on its first day, doubling each day. A campaign larger than the day's allowance continues the next day, most active people first. You don't need to do anything.