Docs › Custom email domains
Campaign sending

Send campaign email from your own domain

Authenticate your domain once, then let campaign creators choose only the From addresses your organization has approved. Dayalogs manages sending; you publish the DNS records it provides.

Availability Team+ Team includes one ready domain; Enterprise is unlimited.

Use a domain you control

You need access to the domain's DNS records. Existing Google Workspace, Microsoft 365 or other mail remains untouched because Dayalogs uses its own survey-mail. subdomain for the technical MAIL FROM records.

This affects campaign email only. A private survey link domain is independent and does not need to use the same hostname.

Register the domain and publish DNS

Add the sending domain

Open Admin → Domains → Custom Email Domain and choose Add domain.

Copy every record

The wizard shows the MAIL FROM MX and SPF TXT immediately. Three Easy DKIM CNAME records appear after the worker finishes preparing the identity. Every record has separate copy actions for its name and value.

Wait for readiness

Background checks update the status automatically. DKIM and custom MAIL FROM must pass before the domain becomes Ready to send.

MX is required here because it lets the email provider handle bounce and complaint feedback for the custom MAIL FROM domain; Dayalogs is not creating an inbox or reading replies.

Add DMARC deliberately

DMARC is recommended but does not block activation. When no policy exists, Dayalogs suggests a TXT record at _dmarc.your-domain with v=DMARC1; p=none. Use that while validating every legitimate mail source, then move to p=quarantine when you are confident nothing valid will be rejected. Dayalogs never replaces an existing policy.

Approve the exact From addresses

A verified domain does not allow campaign creators to invent arbitrary addresses. Add each approved identity from the domain table, using a local part such as surveys or a complete matching address. Identities can be prepared while DNS is still pending, and editing them never restarts domain validation.

An identity is selectable only while it is active and its domain is ready. The shared surveys@dayalogs.com identity always remains available; its display name may be customized, but its address may not.

Try asking your AI

“List the sender identities available for campaigns right now.”

“Create this campaign using surveys@example.com and send me a test before any real recipients.”

Fix DNS before another branded send

If DKIM or required MAIL FROM records stop passing, new sends from the custom identity are blocked instead of silently weakening authentication. Restore the records and use Recheck; the shared Dayalogs sender keeps working in the meantime. An absent optional DMARC policy does not keep the normal status poll running forever.

Remove identities and domains safely

Queued, sending, partially sent or failed non-archived campaigns block removal and are named in the disabled action's tooltip. Editable campaigns fall back to the shared sender when an identity is removed. Domain deletion is asynchronous and removes its email-service identity and local approved identities only after those checks pass.