Transactional vs Marketing Email: Different Rules, Different Deliverability

8 min read

Transactional vs Marketing Email — Why They Have Completely Different Deliverability Rules

Your password reset emails are landing in spam. But your weekly newsletter delivers fine to the same addresses. Or the opposite—your marketing emails work perfectly, but critical account notifications never arrive.

The reason: transactional and marketing emails have fundamentally different deliverability rules. Mixing them together is one of the fastest ways to destroy deliverability for both.

What Transactional Email Actually Is

Transactional emails are messages triggered by a user's action or account status. They're expected, often time-sensitive, and functionally necessary.

Examples of transactional email:

Account-related:

Purchase-related:

Service-related:

Key characteristic: The user did something that directly triggered this email. They're waiting for it.

Test your transactional email setup → checkyouremail.online

What Marketing Email Actually Is

Marketing emails are promotional messages sent to multiple recipients. They're not triggered by immediate user actions.

Examples of marketing email:

Promotional:

Educational/Content:

Engagement:

Key characteristic: You decided to send this, not the recipient's immediate action.

Why ISPs Treat Them Differently

Email providers apply completely different standards to transactional and marketing email.

Transactional Email Expectations

Expected deliverability: 95-99% inbox placement

Why ISPs are lenient:

Authentication requirements:

If transactional email fails: Serious business impact. Users can't log in, can't complete purchases, can't use services.

Marketing Email Expectations

Expected deliverability: 75-85% inbox placement (much lower)

Why ISPs are strict:

Authentication requirements:

If marketing email fails: Business impact, but not critical functionality.

The core difference: ISPs assume transactional emails are wanted. They assume marketing emails might not be.

The Deliverability Comparison

| Factor | Transactional | Marketing | |--------|---------------|-----------| | Inbox placement rate | 95-99% | 75-85% | | Authentication strictness | Moderate | Strict | | Content filtering | Minimal | Heavy | | Volume sensitivity | Low | High | | Engagement importance | Low | Critical | | Spam complaint tolerance | High | Very low | | Reputation weight | Lower | Higher | | Sending frequency | As needed | Regular schedule |

Translation: Transactional email gets the benefit of the doubt. Marketing email doesn't.

Why Mixing Them Is Dangerous

Many companies send transactional and marketing emails from the same domain and IP address. This creates problems.

Problem 1: Marketing Reputation Hurts Transactional

Your marketing emails get spam complaints. This damages your domain/IP reputation. Now your critical password reset emails land in spam too.

Real-world scenario:

Problem 2: Transactional Volume Spikes Trigger Filters

You normally send 10,000 marketing emails per day. Suddenly, you send 100,000 password reset emails because of a security incident.

ISPs see massive volume spike from your IP. They throttle or block, assuming it's spam.

Problem 3: Marketing Best Practices Break Transactional

Marketing emails should have unsubscribe links. Transactional emails don't need them (and shouldn't have them for critical account emails).

If you use the same sending infrastructure, you might add unsubscribe links to password resets. This looks unprofessional and confuses users.

Problem 4: Different Warmup Requirements

New marketing campaigns need gradual volume warmup. Transactional emails need to work immediately at any volume.

If they share infrastructure, you can't warm up one without affecting the other.

Test your current setup → checkyouremail.online

The Separate Infrastructure Approach

The solution: separate sending infrastructure for transactional and marketing email.

Separate Sending Domains

Marketing subdomain: news.yourcompany.com

Main domain: yourcompany.com

Why this works:

Implementation:

1. Choose a marketing subdomain: news.yourcompany.com or mail.yourcompany.com 2. Set up separate SPF, DKIM, DMARC for subdomain 3. Configure marketing ESP to send from subdomain 4. Keep transactional on main domain

Separate IP Addresses

If you send high volume (100,000+ emails/month), use separate dedicated IPs.

Transactional IP:

Marketing IP:

Why this works:

When you need separate IPs:

Separate Email Service Providers

Consider using different ESPs for each type.

Transactional ESP options:

Marketing ESP options:

Why this works:

How to Separate If Currently Mixed

You're currently sending both from the same infrastructure. Here's how to split them.

Phase 1: Audit (Week 1)

Categorize all emails:

Check current reputation:

Document current setup:

Phase 2: Set Up Marketing Infrastructure (Week 2)

Choose marketing subdomain: 

news.yourcompany.com

Add DNS records:

SPF: 

v=spf1 include:spf.yourmktgesp.com -all

DKIM (provided by your marketing ESP): 

Add TXT record at: mail._domainkey.news.yourcompany.com

DMARC: 

_dmarc.news.yourcompany.com TXT v=DMARC1; p=quarantine; rua=mailto:dmarc-marketing@yourcompany.com

Configure marketing ESP:

Warm up the subdomain:

Phase 3: Keep Transactional on Main Domain (Week 2)

Main domain: yourcompany.com

Verify authentication:

Keep transactional ESP separate:

Phase 4: Migrate Gradually (Weeks 3-6)

Don't switch everything at once.

Week 3: Move non-critical marketing emails to new subdomain

Week 4: Monitor deliverability of subdomain sends

Week 5: Move remaining marketing to subdomain if metrics are good

Week 6: All marketing from subdomain, all transactional from main domain

Test at each stage → checkyouremail.online

Authentication Requirements for Each Type

Both need SPF, DKIM, and DMARC. But the policies can differ.

Transactional Authentication

SPF: 

v=spf1 include:_spf.transactional-esp.com -all

Use -all (hard fail). Transactional emails should only come from authorized servers.

DKIM:

Always sign transactional emails. No exceptions.

DMARC:

Start with p=quarantine or p=reject: 

v=DMARC1; p=reject; rua=mailto:dmarc@yourcompany.com

Transactional infrastructure should be so tight that strict DMARC is safe.

Marketing Authentication

SPF: 

v=spf1 include:_spf.marketing-esp.com -all

DKIM:

Always sign. But use different selector than transactional:

DMARC:

Can be more lenient during warmup: 

v=DMARC1; p=none; rua=mailto:dmarc-marketing@yourcompany.com

Then upgrade to quarantine/reject once confident.

Content Guidelines for Each Type

Transactional Email Content

Keep it functional:

Example password reset:

Subject: Reset your password
Hi John,
You requested a password reset for your account.
Click here to reset your password: [link]
This link expires in 1 hour.
If you didn't request this, ignore this email.
—
YourCompany Support Team

Don't add marketing to transactional emails. It's tempting, but it hurts deliverability and looks unprofessional.

Marketing Email Content

Make it engaging:

Example newsletter:

Subject: 3 email deliverability tips for this week
Hi John,
Here are 3 things we learned about email deliverability this week:
1. SPF records with more than 10 lookups break silently...
   [Read more]
2. Gmail Promotions tab placement isn't always bad...
   [Read more]
3. Sender Score below 70 means serious problems...
   [Read more]
—
Sarah
Founder, EmailTool
Unsubscribe | Update preferences

Volume Patterns and What's Normal

Transactional Volume Patterns

Characteristics:

Example SaaS app:

ISPs expect this: Variable volume is normal for transactional.

Marketing Volume Patterns

Characteristics:

Example newsletter:

ISPs expect this: Consistency is key for marketing.

The Case Study: SaaS With Broken Password Resets

Company: B2B SaaS, 10,000 active users

Problem: Password reset emails landing in spam. Support tickets spike.

Investigation:

Checked their email setup:

The issue:

Marketing newsletter had 0.25% spam complaint rate. Not terrible, but enough to gradually damage reputation.

Transactional emails (1,000/day) were caught in the reputation damage.

The fix:

1. Set up transactional subdomain: mail.theircompany.com 2. Moved password resets, notifications to subdomain 3. Kept marketing on main domain initially 4. Separate ESP for transactional (switched to Postmark) 5. Monitored for 2 weeks

Results:

Lesson: Separation fixed both types.

Test your separation strategy → checkyouremail.online

When You Can Use Same Infrastructure

You probably can use the same setup if:

Even then, best practice is separation. But the risk is lower.

When You Must Separate

Separation is critical if:

Don't wait for a problem. Set up separation proactively.

The Complete Separation Checklist

Planning:

Infrastructure Setup:

Testing:

Migration:

Ongoing:

Transactional and marketing emails have fundamentally different jobs. They need fundamentally different infrastructure. Separate them, and both perform better.

Run a free deliverability check right now at checkyouremail.online — no signup, results in 30 seconds.