ActiveCampaign deliverability: domains, shared IPs, engagement

ActiveCampaign sends from shared infrastructure it maintains and monitors, which means the IP layer is largely out of your hands and mostly fine. Your levers are the sending domain, the audience and the sending pattern. Work them in that order and most spam-folder problems resolve without changing platform.

Finish domain authentication

In the account settings there is a domains area where you add your sending domain and ActiveCampaign gives you the DNS records to publish — a DKIM record on a selector it generates, plus a record for the bounce or return-path subdomain so SPF authenticates your domain rather than the platform's. Take the exact hostnames and values from that screen: they are account-specific and they change over time, so never copy them from an article.

Until that is done, your campaigns are signed by the platform's domain. SPF and DKIM pass — for ActiveCampaign. DMARC does not align with your visible From domain, and a domain publishing p=quarantine or p=reject is asking receivers to filter its own mail.

Then verify from the receiving side rather than from the settings page: send a campaign to a mailbox you control, open the raw source, and look for an Authentication-Results line that reads roughly like this, with your own domain in place of the example:

Authentication-Results: mx.recipient-provider.com;
  spf=pass smtp.mailfrom=bounce.yourdomain.com;
  dkim=pass header.i=@yourdomain.com;
  dmarc=pass header.from=yourdomain.com

All three mechanisms passing, with header.i= and header.from= both on your domain rather than ActiveCampaign's, is what alignment actually looks like. A green tick in any platform's settings page means the DNS records resolve, not that alignment is correct — this header is the only proof that counts.

While you are in DNS: keep one SPF TXT record only, and count the lookups in it. The limit is 10 per record and crossing it produces a permerror that breaks every sender on the domain at once.

Then fix the audience

Shared-pool platforms are sensitive to complaint rates, because your behaviour affects their other customers. The audience work that moves the number:

• Segment by recent engagement and stop mailing the long tail. Opened or clicked in the last 90 days is a reasonable starting definition; for ecommerce, recent purchasers are stronger still.
• Remove bounced contacts from your source of truth, not just from the campaign. Automations that re-add contacts from a form or an integration will otherwise hand them back.
• Suppress role addresses such as info@ and sales@ for marketing sends. They attract complaints and nobody on the other end opted in.
• Honour unsubscribes everywhere. If you also send from a CRM, a support tool or an ecommerce platform, the opt-out has to propagate to all of them.

Thresholds to hold: hard bounces under 2%, complaints under 0.05%, and a Gmail user-reported spam rate under 0.1% against Google's published 0.3% bulk-sender limit, which you check in Postmaster Tools per sending domain rather than in any platform's UI.

Then the sending pattern

• Automations and campaigns compete. A one-off blast on top of several running automations can double a day's volume without anyone deciding to. Look at total daily sends per domain, not per campaign.
• Spikes read as compromise. Nothing for six weeks and then 50,000 in an hour is a pattern receivers treat with suspicion. Split large sends across hours or days.
• New domains need a ramp. A newly authenticated sending domain is new to receivers regardless of how old your company is. Start with the most engaged segment and widen.
• For 5,000+ messages a day to Gmail, you need SPF, DKIM, aligned DMARC and a one-click unsubscribe header (RFC 8058). The platform adds the unsubscribe mechanics; DMARC is yours to publish.

What the reports can and cannot tell you

ActiveCampaign's deliverability and campaign reporting shows sends, a delivery figure, bounces, unsubscribes and complaints. The delivery figure is an acceptance figure — the receiving server answered 250 — and no ESP can report which folder the message landed in, because receivers never send that back.

Open rate deserves particular caution as a decision input: Apple Mail Privacy Protection pre-fetches images and proxies inflate opens unevenly across audiences. Use clicks, replies and revenue as outcome measures, and seed-based placement testing per provider to see folders.

What not to do

• Do not re-import unsubscribed or bounced contacts to re-engage them. That is the fastest route past Gmail's spam-rate threshold.
• Do not run cold prospecting lists through a marketing platform. Consent-based audiences are the expectation, and complaints land on your corporate domain.
• Do not mix transactional mail (receipts, resets) and marketing on the same subdomain.
• Do not blast a dormant two-year segment from your main sending domain. Batch it small, or leave it.
• Do not migrate platforms hoping for a reset. The domain reputation and the list come with you.

MailPilot does not integrate with ActiveCampaign, and we are not going to imply otherwise. What it covers is the layer underneath: SPF, DKIM and DMARC verification for your sending domains, warm-up for mailboxes connected over OAuth (Gmail, Outlook) or SMTP and IMAP (SendGrid, Amazon SES, Mailgun, Postmark, custom SMTP), real per-provider inbox placement measurement, and daily per-mailbox reputation tracking.