ActiveCampaign
How to set up SPF, DKIM and DMARC for ActiveCampaign
Authenticate your sending domain in ActiveCampaign with two DKIM CNAMEs, a Mailserver Domain and a DMARC record, then confirm that DMARC passes.
Check your current setup:
How ActiveCampaign authenticates your mail
To set up SPF, DKIM and DMARC for ActiveCampaign, you authenticate a Sending Domain with two DKIM CNAME records and a Mailserver Domain CNAME, then publish a DMARC record. DMARC passes when SPF or DKIM passes on a domain that matches your From address. That match is called alignment, and RFC 9989 describes it in section 4.4.
When you set up a Sending Domain in ActiveCampaign, three domains line up: your From address, the Return-Path and the DKIM signature. The Return-Path is the bounce address that SPF checks, and ActiveCampaign calls that domain the Mailserver Domain. ActiveCampaign calls this result full domain alignment.
DKIM uses two CNAME records, one for each selector. A selector is the label that tells receivers where to find the signing key. Here the selectors are acdkim1 and acdkim2. ActiveCampaign moved from a single TXT record to CNAMEs in February 2023.
You don't need to change the SPF record on your root domain for ActiveCampaign to work.
Step 1: Add your sending domain
- In ActiveCampaign, click Settings, then Advanced.
- Add the domain from your From address. Enter only the bare domain in lower case, such as
example.com. Leave outwww, the protocol and any path. - Choose Configure Domain or Set up manually.
Configure Domain connects to your DNS provider and creates the records after you authorize access. It doesn't support every DNS provider. Set up manually sends a verification link by email and then shows the records for you to create.
Step 2: Publish the two DKIM records
Create both CNAME records exactly as ActiveCampaign shows them. Their names are acdkim1._domainkey and acdkim2._domainkey. ActiveCampaign generates the targets for your account, so copy them from the screen.
Some DNS providers add your domain to the name automatically. Use the short form with those providers. Use the full name, ending in your domain, with the others. You can check the result with our DKIM checker using either selector.
Step 3: Publish the Mailserver Domain
The manual setup also gives you a CNAME record for the Mailserver Domain. It points a subdomain of yours to ActiveCampaign so that subdomain can serve as the Return-Path and pass SPF on your own domain.
With a Mailserver Domain configured, ActiveCampaign serves SPF through that CNAME, so its help says no extra SPF record or change to your existing SPF is needed for ActiveCampaign. Keep the SPF entries your other sending services need.
Step 4: Publish a DMARC record
Google requires DKIM and DMARC from senders of more than 5,000 messages daily to personal Gmail accounts. Yahoo requires them for bulk senders but publishes no fixed numerical threshold. Configure both for your sending domain.
A basic DMARC record is part of adding a Sending Domain. Configure Domain won't create a second one if your domain already has a record. With the manual setup, check first whether your domain already has a DMARC record. If it does, keep that record and add your reporting address to its rua tag, because a domain can only have one DMARC record. If it doesn't, publish a TXT record named _dmarc:
Use this starter value only if no DMARC policy exists at this name. Otherwise edit the existing record, preserving its p=, alignment settings and report addresses; add your monitored rua destination there. Never create a second policy record.
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Replace the rua address with your DMARC Pulse reporting address. Keep p=none while you read the reports. The policy tags are defined in RFC 9989, section 4.7.
Preserve existing policy, alignment and report destinations. Confirm aligned DKIM before relying on enforcement. A first policy may monitor at p=none; after all legitimate senders align, assess quarantine. Reject is optional and needs a separate mailing-list risk assessment.
Step 5: Check, then enforce
Go back to Settings, then Advanced, and click Check DNS for the domain. The status Authenticated means the domain passed ActiveCampaign's DNS checks and DKIM is set up correctly.
Send a test and paste the headers into the Email Header Analyzer. In the Authentication-Results field, look for dkim=pass with your domain and dmarc=pass.
Then confirm the record with our DMARC checker and tighten the policy step by step, only after your reports show your ActiveCampaign mail and every other service that sends from your domain passing.
Common problems
"Only one of your CNAME records is set up. Please check your DNS records for typos." One of the two DKIM records is missing or wrong at your DNS provider. Confirm that both exist, then look for typos in the names and targets.
The record name has your domain twice. Your DNS provider added the domain to a full name you typed. Use the short form, such as acdkim1._domainkey.
The legacy TXT record notice. Domains that set up DKIM with a TXT record before February 23, 2023 can see it. The old setup still works. Click Check DNS to get the CNAME records.
The domain won't verify right after you add the records. Records usually appear in 5 to 10 minutes. ActiveCampaign's help allows up to 24 hours in rare cases, and newly purchased domains may take up to 48 hours. If Configure Domain can't finish, a Resolve Issues button runs it again.
The Mailserver Domain and the link tracking domain got mixed up. They are two different CNAME records, and each one needs its own subdomain. A custom domain for links does nothing for SPF.
Reports show SPF passing but not aligned. Without a Mailserver Domain, SPF passes on ActiveCampaign's domain and that domain doesn't match your From address. DMARC still passes if DKIM is aligned.
Open rates fall after you turn on DKIM. ActiveCampaign explains that signing with your own domain makes you look like a new sender, so mailbox providers need time to learn your pattern. Check that the domain shows Authenticated before you look for other causes.
You tried the public checker on another service. ActiveCampaign's DNS checker only covers domains you send from with ActiveCampaign. Records for services like Google Workspace or Microsoft 365 need their own checks.