Definitions & Examples
Every email your business sends falls into one of two categories: transactional or marketing. Getting this distinction right is fundamental to both legal compliance and deliverability.
Transactional Email
Transactional emails are triggered by a specific user action and contain information the recipient needs to complete a process or use a service they've already engaged with. They are sent one-to-one, not one-to-many.
Examples:
- Order confirmation: "Your order #12345 has been placed"
- Shipping notification: "Your package is on its way"
- Password reset: "Click here to reset your password"
- Two-factor authentication code
- Account creation confirmation
- Invoice or payment receipt
- Subscription renewal confirmation
- Customer support ticket update
Marketing Email
Marketing emails are sent to multiple recipients and are primarily intended to promote products, services, or relationships. They require prior consent in most jurisdictions.
Examples:
- Promotional campaigns: "Sale ends Sunday — 30% off sitewide"
- Newsletter: weekly product updates, content, or company news
- Win-back campaigns: "We miss you — here's 20% off"
- Product announcement: "Introducing our new line"
- Abandoned cart: "You left something behind"
- Post-purchase upsell: "Customers who bought X also love Y"
The grey zone: triggered marketing emails
Some emails are triggered by user behavior but are primarily promotional — like abandoned cart emails or post-purchase upsells. These are marketing emails even though they feel transactional, because their primary purpose is to drive a commercial action. Apply marketing email rules (consent required, unsubscribe link mandatory) to these.
Legal Differences
| Requirement | Transactional | Marketing |
|---|---|---|
| Prior consent required | No (implied by the service relationship) | Yes (GDPR, CASL); opt-out only (CAN-SPAM) |
| Unsubscribe link required | Not required (CAN-SPAM exemption) | Required by all major regulations |
| Compliant even if unsubscribed | Yes — you can send order confirmations to opted-out customers | No — honor all unsubscribes |
| Subject line restrictions | Must not be misleading | Must not be misleading; must reflect commercial intent |
The key legal privilege of transactional email: you can send it to someone who has unsubscribed from your marketing list, as long as it's genuinely transactional (not promotional). An order confirmation is always expected; a "we think you'd like these products" email is not.
Why Separate Sending Streams Matter
Mixing transactional and marketing emails in the same sending infrastructure is one of the most damaging deliverability mistakes you can make. Here's why:
Reputation Contamination
Your sender reputation is tied to your sending domain and IP addresses. If your marketing campaigns generate spam complaints — which all marketing campaigns do at some rate — those complaints damage the reputation of every email sent from that domain and IP pool, including your order confirmations and password resets.
A customer trying to reset their password while your IP is temporarily blocklisted due to a campaign complaint spike is a serious problem. Transactional emails need a pristine, isolated reputation.
Deliverability Asymmetry
- Transactional email — Low volume, high engagement, highly expected by recipients. Achieves near-100% inbox placement when isolated.
- Marketing email — Higher volume, lower engagement, some recipients forget they subscribed. Inherently lower inbox placement rate.
Don't let marketing email performance drag down transactional email delivery.
Monitoring Clarity
When you separate streams, you can see performance metrics for each type independently. A spike in complaints on your marketing domain tells you something is wrong with a campaign — not your entire email operation.
BayEngage's Role: Marketing Email
BayEngage (TargetBay Email/SMS) is a marketing email platform. It's designed for campaign-based email — newsletters, promotions, drip sequences, SMS campaigns, and behavioral automations. It is not a transactional email platform.
What BayEngage Is Built For
- Promotional campaigns to subscriber lists
- Drip and nurture email sequences
- Behavioral automations (welcome series, re-engagement, win-back)
- SMS marketing campaigns
- Abandoned cart reminders and post-purchase flows
- Newsletter and content distribution
What BayEngage Is NOT Designed For
- Individual order confirmations triggered by e-commerce transactions
- Password reset emails
- Two-factor authentication codes
- Real-time payment receipts
- High-volume, API-triggered transactional sends
Attempting to use BayEngage for transactional email creates a fragile architecture that makes transactional sends dependent on your marketing platform's availability and reputation. Use a dedicated transactional ESP instead.
Pairing BayEngage with a Transactional ESP
The recommended architecture is two separate platforms: BayEngage for marketing email, and a transactional email service (TES) for one-to-one transactional sends. Common transactional email services include:
- Amazon SES — Lowest cost at scale; requires technical setup; excellent deliverability
- SendGrid — Developer-friendly with strong deliverability; scales well
- Postmark — Focused exclusively on transactional email; excellent inbox placement
- Mailgun — Good for medium-volume transactional sends
Domain Strategy
Use different subdomains for each stream to keep reputations isolated:
mail.yourdomain.comornews.yourdomain.com— marketing email via BayEngagesend.yourdomain.comortx.yourdomain.com— transactional email via your transactional ESP
Each subdomain gets its own SPF, DKIM, and DMARC records. Problems in one stream don't affect the other.
Integration Pattern
In your e-commerce platform or application, trigger transactional sends (order confirmations, receipts) via your transactional ESP's API. Use BayEngage for all campaign-based sends. The two systems operate independently — a marketing campaign issue in BayEngage never affects order confirmation delivery.
Deliverability Implications
Marketing Email Deliverability Expectations
Even a well-run marketing program will experience some inbox placement variability. This is normal — some recipients have aggressive spam filters, some emails land in Promotions tab, and complaint rates above zero are expected. The goal is to stay above 90% inbox placement on average.
Key metrics to monitor for your BayEngage marketing sends:
- Spam complaint rate (target: below 0.05% — Gmail's threshold before filtering starts at 0.1%)
- Inbox placement rate via seed testing (target: above 90%)
- Domain reputation in Google Postmaster Tools (target: HIGH)
Transactional Email Deliverability Expectations
Properly configured transactional email should achieve 98–100% inbox placement. If your transactional emails are going to spam, the most common causes are:
- Authentication not set up (SPF/DKIM/DMARC missing)
- Sending from a domain contaminated by poor marketing email practices
- Sudden volume spikes (e.g., mass password reset after a breach)
- Spam trigger content in the email body
Monitor both streams with InboxEagle
Add both your marketing and transactional sending domains to InboxEagle. Get separate inbox placement data, reputation scores, and alerts for each — so an issue in one stream is immediately visible and isolated from the other.
Setup Checklist
Domain & Authentication Setup
- ☐ Marketing sending subdomain configured in BayEngage (e.g.,
mail.yourdomain.com) - ☐ Transactional sending subdomain configured in your transactional ESP (e.g.,
send.yourdomain.com) - ☐ SPF record published for both subdomains — SPF Builder
- ☐ DKIM enabled and DNS record published for both subdomains
- ☐ DMARC at
p=nonefor both subdomains — DMARC Generator - ☐ Authentication verified with free deliverability checker
Routing
- ☐ All promotional, campaign, and nurture emails routing through BayEngage
- ☐ All transactional sends (order confirmations, receipts, password resets) routing through dedicated transactional ESP
- ☐ Abandoned cart and behavioral triggers treated as marketing (BayEngage, consent required)
Monitoring
- ☐ Both domains monitored for inbox placement (InboxEagle seed list)
- ☐ Marketing domain connected to Google Postmaster Tools
- ☐ Complaint rate tracked separately for each stream
One Dashboard for Both Streams
InboxEagle monitors inbox placement, authentication, and reputation for all your sending domains — marketing and transactional — with real-time alerts when either stream shows problems.