Salesforce Pardot Email Deliverability Guide

Google says bulk senders should keep spam complaint rates below 0.3% in Google Postmaster Tools. That single number is useful for Pardot teams because it shifts the conversation from, “Did the send go out?” to, “Did the send build or damage mailbox trust?”

In Salesforce Pardot, now Account Engagement, deliverability usually breaks down in a few predictable places: weak domain setup, inconsistent sending patterns, aging or over-mailed segments, and reporting that leans too heavily on opens. The fix is not one setting. It is a sending system that makes good reputation the default.

What deliverability means in Salesforce Pardot

For Pardot users, deliverability is the combined result of technical authentication, sender reputation, list quality, message relevance, and how major providers interpret recipient behavior after delivery. A message can be accepted by Gmail or Outlook and still land in Promotions, Other, or spam. That is why delivery rate alone is not a decision metric.

The practical goal is not a mythical 100% inbox rate. The goal is stable placement for the right audiences, low complaint pressure, and a feedback loop that helps RevOps, lifecycle, and demand gen teams decide what to change before reputation slips.

Start with authentication and domain alignment

Authenticate the domain you actually send from

If your Pardot programs send from marketing.yourcompany.com, but your DKIM signing and visible From address point elsewhere, you create unnecessary ambiguity for providers. Gmail, Yahoo, and Outlook all evaluate consistency. They want to see that the brand in the inbox matches the domain behavior in DNS and in message headers.

At a minimum, your Pardot setup should support SPF, DKIM, and DMARC for the domain used in marketing sends. SPF helps authorize sending infrastructure, DKIM signs the message, and DMARC tells providers how to evaluate alignment and where to send reports. DKIM usually does the heavy lifting for inbox trust because SPF often breaks alignment when messages pass through forwarding paths.

Brand your links and tracking domains

Unbranded click tracking domains are a common weak point. If the visible From address says your company, but the links resolve through a generic or inconsistent tracking domain, some filters treat that as lower trust. In Pardot, make sure your tracker domain is branded and maintained, because link reputation can influence how mailbox providers evaluate the full message.

DMARC is not just a security project

DMARC matters for deliverability because it forces inventory. You find the services sending on your behalf, align the legitimate ones, and shut down or quarantine the rest. For B2B teams with Salesforce, webinar tools, SDR platforms, and customer messaging tools all touching the same domain, that cleanup prevents reputation fragmentation.

Use the right sending architecture for your volume and risk

Shared IP versus dedicated IP

If your Pardot volume is modest and steady, a reputable shared IP can perform well because it pools stable behavior across senders. If your volume is high, your sending pattern is predictable, and you can consistently control list quality, a dedicated IP gives you more isolation and more direct ownership of reputation.

The mistake is choosing a dedicated IP before you can support it. A dedicated IP with uneven volume, irregular campaigns, or stale database segments often performs worse than a healthy shared pool because mailbox providers struggle to establish a stable baseline.

Warm up when your profile changes

You do not only warm up new infrastructure. You also warm up after large list imports, long sending gaps, domain changes, or major cadence increases. For Gmail and Yahoo, sudden volume jumps paired with low recent engagement can look like a reputation event. For Outlook, the same pattern often shows up as temporary deferrals and uneven inboxing across Microsoft-hosted domains.

A practical approach is to ramp volume through your best recent engagers first, then expand by engagement age and business importance. That gives providers positive user signals before you ask them to trust a wider audience.

List quality is where most Pardot programs win or lose

Stop mailing the entire mailable database

Pardot makes it easy to suppress hard bounces and unsubscribes. That is necessary, but not sufficient. The bigger issue is over-mailing contacts who never click, never reply, and have not shown recent intent. A large “mailable” audience is not the same as a healthy audience.

For most B2B programs, segmenting by recency of engagement is the fastest way to improve inbox placement without changing creative. Start with contacts who clicked or converted in the last 30 to 90 days. Then create separate rules for 90 to 180 days, and treat anything older as a reactivation or sunset decision, not a standard campaign audience.

Complaints matter more than marketers usually think

A complaint rate that feels small in a campaign dashboard can still be large to Gmail. If 4 out of 1,000 recipients hit spam, that is 0.4%, already above Google’s stated 0.3% threshold for bulk senders. That is enough to drag down future placement, even if the campaign also generated pipeline.

Complaint control starts before the send. Tighten opt-in language, suppress role accounts where appropriate, keep frequency predictable, and match the message to the stage of the buyer. A top-of-funnel ebook offer sent to late-stage prospects or customers often creates the kind of mismatch that drives spam clicks.

Engagement signals differ by provider, so read them correctly

Gmail and Yahoo care about post-delivery behavior

Gmail and Yahoo heavily weight user behavior after delivery. Deletes without reading, low read time, no clicks, no replies, and spam complaints all shape future placement. That means your first audience decision often matters more than your subject line test.

In Pardot, use dynamic lists and automation rules to separate high-intent prospects from low-intent names instead of blasting both with the same cadence. The send plan should reflect the engagement profile of the segment, not just the campaign deadline.

Outlook is often more reputation-sensitive

Outlook and other Microsoft-hosted mailboxes can react sharply to sender reputation changes, especially when volume rises quickly or complaint signals worsen. You may see more throttling, delayed delivery, or inconsistent placement by tenant. If Gmail looks stable but Outlook performance drops, check reputation, list source, and frequency before rewriting creative.

Apple Mail changes how you interpret opens

Apple Mail Privacy Protection preloads many tracking pixels, which inflates open rates. In a Pardot dashboard, that can make weak segments look healthier than they really are. If you optimize solely on opens, you risk expanding sends to contacts who are not actually engaged.

For lifecycle and RevOps teams, better health signals are clicks, form fills, replies, demo requests, conversion rate by segment, hard bounce rate, unsubscribe rate, and complaint rate where available.

Operational habits that protect reputation in Pardot

Keep cadence consistent

Mailbox providers prefer predictable senders. If your team disappears for three weeks and then sends four large campaigns in two days, filters see volatility. Build a calendar that smooths volume across the week and avoids stacking multiple broad sends to the same audience.

Separate promotional, nurture, and operational intent

A prospect who tolerates a webinar reminder may not want a weekly thought-leadership roundup plus product launch plus regional event invite. In Pardot, use segmentation and suppression logic so contacts are not exposed to overlapping campaign pressure from multiple teams.

Make reactivation a controlled experiment

If you want to wake up older leads, do not drop them into business-as-usual sends. Use a separate re-engagement program, smaller batches, a clearer value proposition, and a firm stop rule. If older segments do not respond, continued mailing does more reputational harm than pipeline good.

How to diagnose common Pardot deliverability problems

What a healthy Pardot review cadence looks like

Review deliverability weekly, not only after major incidents. Look at performance by mailbox provider, by segment age, by campaign type, and by domain. Compare clicks, replies, bounces, unsubscribes, and complaints against the previous four to eight weeks. That is how you catch a slow reputation decline before Gmail or Outlook makes the decision for you.

Also, align sales and marketing on what should happen to cold leads. If SDRs and marketers keep re-mailing the same non-responders because they are still “mailable,” you build a reputation problem that no technical setting can solve.

Related reading: email deliverability tools and spf and dkim deliverability.

Run your first deliverability test with Mailora

FAQs

Is Pardot deliverability mainly a Salesforce setup issue?

No. Setup matters, especially SPF, DKIM, DMARC, and branded links, but ongoing deliverability is mostly driven by audience quality, cadence, and recipient behavior at Gmail, Outlook, Yahoo, and Apple Mail.

Should B2B teams use a dedicated IP for Pardot?

Only if volume is high enough and consistent enough to support it. Many teams do better on a healthy shared pool than on a dedicated IP with uneven sends and stale segments.

How quickly can deliverability improve after cleanup?

Technical fixes can help immediately, but reputation recovery usually takes multiple sends. Expect clearer signal after several weeks of disciplined segmentation, lower complaint pressure, and steadier volume.

Do open rates still matter in Pardot?

They still provide directional context, but they are not reliable enough to drive major decisions on their own because Apple Mail inflates many opens. Clicks, replies, conversions, and complaints are better decision signals.

What is the fastest way to reduce risk in a Pardot program?

Send less broadly. Start with recently engaged contacts, tighten suppression rules, smooth your cadence, and make sure your sending domain and tracking links are fully aligned.