Skip to content
DMARC Pulse

Email senders

Customer.io DMARC setup: SPF, DKIM and alignment

How Customer.io signs from an account subdomain, which DNS records it asks for, and why strict DMARC alignment makes its mail fail.

SPF include for Customer.io

Customer.io does not need an SPF include on your domain.

DKIM for Customer.io

Selectors
cio
How to enable it
One TXT record at cio._domainkey.cio#####.yourdomain.com, where ##### is your account number, holding a 2048-bit key by default. Customer.io signs with that account-specific subdomain of your domain, so DKIM aligns with your From domain only under relaxed alignment.

Customer.io signs with your domain

The signature carries your domain in d=, so DKIM can align with your From address and pass DMARC on its own.

Envelope-from and SPF alignment

SPF counts for DMARC only when this domain matches the domain in your From address. If it is Customer.io’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.

Envelope-from (Return-Path)
cio#####.yourdomain.com, a subdomain specific to your account, where ##### is your account number

Sending ranges of Customer.io

Use these to recognize Customer.io in your reports. They change over time, so do not copy them into your SPF record.

Customer.io does not document this.

Does your domain authorize Customer.io?

Enter your domain. The SPF Checker reads your record and names the senders it authorizes.

Customer.io documentation

How it authenticates

Customer.io DMARC setup centers on a subdomain created for your account, in the form cio#####.example.com, where ##### is your account number. You add the sending domain under Settings > Workspace Settings > Email, and Customer.io shows the DNS records to publish.

An MX record creates the bounce Return-Path on that subdomain. A TXT there holds SPF (Sender Policy Framework). Another TXT at cio._domainkey.cio#####.example.com holds the DKIM (DomainKeys Identified Mail) public key. The fourth record is DMARC at _dmarc.example.com. Preserve an existing policy; otherwise start with monitoring and a report mailbox:

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

Customer.io will not send from the domain until SPF and DKIM both verify. Because SPF lives on the subdomain, your root record gains no extra lookups.

What to watch for

Alignment depends on relaxed mode. The Return-Path and the DKIM signature both use the account subdomain, and relaxed mode accepts a subdomain of your From domain. Relaxed mode is the default. If your record sets the aspf tag and adkim both to s, neither identifier aligns, so mail from the built-in servers can bounce under p=reject or land in spam under p=quarantine. With only one set to s, DMARC depends on the other mechanism alone. Customer.io asks for relaxed values on both. See DMARC alignment for the rule itself.

Customer.io checks DNS only when you click Verify domain. A record you remove later goes unnoticed there, and mail can bounce or be filtered as spam.

The DKIM key is longer than one DNS string can hold. Split it into quoted strings inside one TXT record, without line breaks.

Apple Private Email Relay is the SPF exception. Apple checks the From domain, so built-in delivery needs include:mailgun.org there. Merge it into the existing single SPF record and check the combined total stays within ten DNS lookups before saving.

Test selector cio on the account subdomain with the DKIM checker. Preserve existing DMARC and report addresses. For a first policy, monitor at p=none before you tighten the policy.

Check it now

Find and validate DKIM keys

Frequently asked questions

Do I add Customer.io to my root domain SPF record?
Not for normal sending. The SPF record goes on your cio#####.example.com subdomain, so it does not count toward the lookup limit of your root record. Apple Private Email Relay is the documented exception.
Which DKIM selector does Customer.io use?
The documented record name is cio._domainkey.cio#####.example.com, so the selector is cio. It sits under your account subdomain. To test it, check that subdomain and not your root domain.
Why does Customer.io mail fail DMARC with aspf=s?
aspf=s only makes SPF alignment strict. Aligned DKIM can still pass DMARC unless adkim=s also makes the signing subdomain fail strict DKIM alignment. Customer.io asks for relaxed alignment on its built-in servers.
Do I need both SPF and DKIM for Customer.io?
Yes, to send from the domain. Customer.io requires both to be verified. DMARC itself needs only one aligned pass, and both records use the subdomain that aligns under relaxed mode.
Does this apply if I use my own SMTP server?
No. With custom SMTP you do not authenticate the domain in Customer.io. Your SMTP provider's documentation tells you which DNS records to add.

Sources consulted

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.