Email senders
Pipedrive DMARC setup: SPF, DKIM and alignment
How Pipedrive Campaigns authenticates your domain with three CNAME records and a DMARC TXT record, and what commonly goes wrong during setup.
SPF include for Pipedrive
Pipedrive does not document an SPF include.
DKIM for Pipedrive
- Selectors
- Pipedrive does not document this.
- How to enable it
- For Campaigns, publish the two DKIM CNAME records shown in Campaigns > Settings > Domain authentication. Copy the names and values from your account.
Pipedrive does not document which domain it signs with
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Pipedrive’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- Pipedrive does not document this.
Sending ranges of Pipedrive
Use these to recognize Pipedrive in your reports. They change over time, so do not copy them into your SPF record.
Pipedrive does not document this.
Does your domain authorize Pipedrive?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Pipedrive documentation
- Pipedrive Knowledge Base: Campaigns email domain authentication
- checked 2026-11-09
- Pipedrive Knowledge Base: Campaigns DMARC and email deliverability
- checked 2026-11-09
- Pipedrive Knowledge Base: Campaigns how to edit DNS records
- checked 2026-11-09
- Pipedrive Knowledge Base: Campaigns sender email FAQ
- checked 2026-11-09
- Pipedrive Knowledge Base: Email senders in automations
- checked 2026-11-09
How it authenticates
Pipedrive DMARC setup happens in Campaigns, the feature that sends your email marketing. Open Campaigns > Settings > Domain authentication, click + Domain and enter your domain. Pipedrive then lists four DNS records.
Three are CNAME records. One covers SPF (Sender Policy Framework, the list of servers allowed to send for you) and the return path, the bounce address that SPF checks. Two are for DKIM (DomainKeys Identified Mail), the signature on each message. The fourth is a DMARC TXT record.
Pipedrive's Campaigns articles name no SPF include and no fixed DKIM selector. Copy the records from your account. Copy the names and values from your account.
Pipedrive says authentication lets campaigns pass the DMARC check. It does not say which domain signs the mail or which bounce domain SPF checks. DMARC alignment needs one passing result, SPF or DKIM, on a domain that matches your From address. Read the SPF and DKIM domains in your reports to see which one aligns.
What to watch for
- A second DMARC record. If your domain already has DMARC, keep one record and preserve its policy and report addresses. Compare
p=andruabefore changing it, then confirm with the DMARC checker. - The domain field. Enter
example.com, withoutwww,http://orhttps://. - Free addresses. Campaigns refuses free and disposable senders. Pipedrive warns that
@yahoo.comand@aol.comsenders get blocked because those domains use DMARC. - The sender address. After authenticating the domain, you still verify the sender email through a link, then choose that address in the campaign.
- Waiting on DNS. The status stays pending until the records propagate, which can take 48 hours. Click Refresh status to check again.
- Other Pipedrive mail. These records apply to Campaigns. Automated emails go out from an account connected through email sync, and Pipedrive's article on them does not mention DNS. Check that mailbox's own authentication.
Preserve existing DMARC and report addresses. For a first policy, monitor at p=none before you tighten the policy.