Authorize your own email domain for sending campaigns. Once DKIM is set up, any address on that domain (e.g. alerts@yourcompany.com, noreply@yourcompany.com) can be used as the “from” address.

Who can do this

Organization admins on Professional or Enterprise plans. DKIM is verified once per organization and can then be shared with any team in your workspace.

What DKIM does

DKIM (DomainKeys Identified Mail) cryptographically signs your outbound emails so receiving servers like Gmail, Outlook, and Yahoo trust they came from your domain. Without DKIM, campaigns from your domain land in spam or get rejected outright.

What you need

• Access to your DNS provider for the email domain.
• Three CNAME records to add — we provide them when you start onboarding.

Step-by-step setup

1. Go to Account → Organization → My Domains → Sending Domains.
2. Enter your email domain — just the domain, not a full address (e.g. yourcompany.com, not alerts@yourcompany.com).
3. Click Add Domain. The card expands with three CNAME records.
4. Copy each row into your DNS provider. The Name ends with ._domainkey — do not append your domain manually; most providers add it automatically.
5. Save DNS. Click Reload on the card every few minutes until the badge flips to DKIM Verified. Propagation takes 15 minutes to 24 hours depending on your provider.
6. Once verified, the Teams selector unlocks. Pick the teams allowed to send from this domain. Click Save.
7. The domain now appears in every team member’s From dropdown when composing a campaign.

Example DNS records

The actual tokens are unique to your domain. Yours will look like:

Type	Name	Value
CNAME	a1b2c3..._domainkey	a1b2c3....dkim.amazonses.com
CNAME	d4e5f6..._domainkey	d4e5f6....dkim.amazonses.com
CNAME	g7h8i9..._domainkey	g7h8i9....dkim.amazonses.com

Provider-specific gotchas

• Cloudflare — CNAME proxying is not supported for DKIM; set the proxy toggle to DNS only (grey cloud).
• GoDaddy — when asked for the host, enter just a1b2c3..._domainkey (without .yourcompany.com). GoDaddy auto-appends.
• AWS Route 53 — paste the full a1b2c3..._domainkey.yourcompany.com as the record name.
• Google Workspace DNS — use “Custom resource records”; do not confuse with Google Workspace’s own DKIM (they can coexist safely).

Troubleshooting

• Still pending after 24 hours — from any terminal run dig CNAME a1b2c3..._domainkey.yourcompany.com. If no answer comes back, DNS didn’t save the record. If the answer is wrong, the value was copied incorrectly (a missing trailing segment is the usual culprit).
• Multiple orgs, same domain — only one SurveyAnalytica organization can own DKIM verification for a domain. Contact support to consolidate.
• Emails still landing in spam — DKIM alone is enough for most inboxes, but for enterprise sending volume, also add an SPF record: v=spf1 include:amazonses.com ~all. For the strictest deliverability, add a DMARC record too.

Revoking access

Organization admins can remove team access at any time from the domain card’s team selector. Revoking does not remove the DKIM setup — the domain stays registered at the org level and can be re-shared. To fully deregister the domain, click Delete on the card.