How to Set Up Your Personalized Email Sender & DNS

When you send email campaigns, appearing as coming from your own Brand domain builds trust and improves deliverability. We make it as easy as possible to set up your custom email in 3 steps.

Why set up a custom sending domain?

Until you verify a custom domain, your emails send from campaigns@getshouting.app. That works, but setting up your own domain provides several advantages:

  • Deliverability — SPF and DKIM records prove to inbox providers that your mail is legitimate, reducing spam placement.
  • Brand trust — Recipients see your domain in the From address instead of a shared platform address.
  • Click tracking — A tracking CNAME record enables accurate click-through attribution on your campaigns.
1

Sender Identity & Reply-To

Open Account → Brand Settings → Email Sending.

Email Sending — Step 1: Sender Identity and Reply-To in Get Shouting

Save with Save & Continue (use From Mailbox → when you’ve already saved and want to continue without submitting again).

  • From Name — Display name in the inbox preview line.
  • Reply-to Email — Where replies route; independent of sending domain.
  • Physical Address — CAN-SPAM / CASL postal line in footer.

Until the physical address is saved, steps 2 and 3 remain disabled.

2

Sending Email Address

Enter the email address you want your emails to come from; e.g. hello@yourbrand.com. Only use a domain you control. The next step requires you add some entries on your hosting service.

Email Sending — Step 1: Sender Identity and Reply-To in Get Shouting

Add domain registers DNS with our provider and jumps you straight to circle 3 for verification. Navigate back anytime with circle 2 or ← Mailbox from Step 3.

Note: The mailbox field locks after registration — use Remove Domain here or on Step 3 to clear it before changing address.
3

DNS Records & Verification

This is both the registrar checklist and verification. Each DNS record is created specifically for your domain and is unique to your Brand.

Email Sending — Step 1: Sender Identity and Reply-To in Get Shouting

Add each record at your registrar

Log in wherever you host your site or manage DNS settings. If you're unsure, search your email for your domain purchase confirmation. We've added helpful links below.
It is very important that you copy and paste the exact values from the table into your registrar including the TYPE, NAME, and VALUE.

Go directly to your registrar's DNS settings

GoDaddy Namecheap Cloudflare Google Domains / Squarespace Name.com Hover Porkbun AWS Route 53

Not listed? Search your email for “domain registration” or “DNS settings” to find your provider.

  1. Open DNS settings for your zone — sections may be labelled DNS, DNS Management, DNS Records, or Advanced DNS.
  2. For each row from the Get Shouting table: pick Type (MX, TXT, CNAME…), paste Name / Host and Value. Leave TTL as Auto or 3600.
  3. Important — Name / Host: enter only the prefix (e.g. send, links, abc123._domainkey). Never paste .yourdomain.com — registrars append the zone automatically.
  4. Back in Step 3, click Verify Domain to ask Resend to rescan immediately, then use Check status any time you just need the freshest snapshot displayed. Remove Domain appears on Step 3 to the right of Check status whenever you might need to unregister.

Registrar-specific tips

  • Cloudflare: When adding CNAME records, make sure the proxy toggle is set to DNS only (gray cloud icon, not orange). Proxied CNAMEs break DKIM.
  • GoDaddy: Go to DNS > Add New Record. The “Host” field is the Name column. Do not add your domain to the end.
  • Namecheap: Go to Advanced DNS on your domain. Use “Add New Record”. For CNAME values that end in a period (.), you can omit the trailing period.
  • Google Domains / Squarespace: Go to DNS > Manage custom records. Add each record type individually.
  • AWS Route 53: In your hosted zone, create each record. For CNAME values ending in a period, include it.

Verify & read status

DNS propagation can take a few minutes to 48 hours worldwide — most registrars converge in 15–30 minutes. While you wait:

  • Use Verify Domain right after publishing records to force another scan.
  • Use Check status any time just to reload the newest known state.
  • Remove Domain also lives on Step 3 for quick teardown next to primary actions.
Status shown in app What it means Action
Not started No domain registered yet Enter mailbox address and click Add domain
Pending DNS records not yet detected Wait and use Check status to re-poll
Verified All records confirmed; sending is enabled No action needed — campaigns will send from your address
Failed One or more records are wrong or missing Fix records at registrar, Verify Domain again, Check status
  • Double-check every Type, Name, and Value copied from Step 3.
  • On Cloudflare, keep DKIM-related CNAMEs on DNS only (grey cloud).
  • If MX host conflicts arise, confirm your registrar permits multiple MX entries with differing priorities.

Understanding the DNS records

Get Shouting generates up to four record types for your domain. All are required for full functionality except DMARC, which you configure independently.

SPF (TXT record)

Specifies which mail servers are allowed to send email for your domain. Inbox providers reject or flag messages from servers not listed in your SPF record.

DKIM (CNAME record)

Adds a cryptographic signature to outgoing mail so recipients can confirm the message was not altered in transit and was sent by an authorised server.

Tracking (CNAME record)

Routes click-tracking links through your domain rather than a shared sending domain. This improves deliverability and enables accurate open and click reporting in your campaign analytics.

DMARC (TXT record) — optional

DMARC instructs inbox providers what to do when an email fails SPF or DKIM checks (e.g. quarantine or reject it) and sends you aggregate reports. DMARC is not generated by Get Shouting — it is an additional record you may add to your DNS independently if you want reporting or a stricter policy. A minimal starting policy looks like:

Type: TXT
Name: _dmarc
Value: v=DMARC1; p=none; rua=mailto:you@yourdomain.com

After verification

Once your domain status shows Verified:

Send a test campaign to yourself and to a personal address on a different provider (e.g. Gmail if you use Outlook, or vice versa) before your first live send to confirm correct display name, reply-to, and footer address.

Removing or changing your sending domain / mailbox

Because the From mailbox field is locked once a domain is registered, changing your address requires removing the existing registration first.

  1. Open Email Sending (Step 2 — Sending mailbox or Step 3 — DNS Records & Verification).
  2. Click Remove Domain — on Step 2 near the mailbox, and on Step 3 beside Check status — then confirm.
  3. Your campaigns revert to campaigns@getshouting.app immediately.
  4. Optional: enter the new mailbox in Step 2, Add domain, and repeat Step 3 (DNS rows + verification).

If you want to revert permanently to the platform address and stop using a custom domain, simply remove the domain and leave the field empty — campaigns will continue sending from campaigns@getshouting.app.

Troubleshooting

Symptom Likely cause Fix
Status stuck on Pending after 2+ hours Record not saved, wrong Name, or slow TTL Re-check each record in your registrar; ensure Name does not include your domain suffix
DKIM fails; SPF passes Cloudflare proxy enabled on CNAME Set CNAME to DNS only (gray cloud) in Cloudflare
MX record conflict Existing MX record at the same host Some registrars allow multiple MX records with different priorities; check your registrar's docs
CNAME value appears wrong (extra dot) Trailing period included by some registrars For Namecheap you can omit the trailing period; for Route 53 include it
Emails still sending from campaigns@getshouting.app after verification Domain not yet fully verified Confirm status shows Verified in Email Sending settings; if Pending, use Check status

Next steps