A password reset email and a Friday afternoon sale announcement look similar in an inbox - both are just email. To a spam filter, and to the person who has to explain a missed order confirmation, they could not be more different. One is expected, urgent, and almost always wanted. The other is optional, sent in bulk, and only wanted by some of the people who receive it. Treating them the same, technically or strategically, creates problems that show up as symptoms in the wrong place.
Businesses that build their own websites and tools often discover this the hard way: a newsletter blast goes out, complaint rates tick up, and suddenly booking confirmations from the same domain start landing in spam too. The fix is not better copywriting. It is separating two jobs that were never meant to share the same reputation.
What counts as transactional email
Transactional mail exists because a specific person did a specific thing a moment ago, and expects a reply. It is one-to-one in spirit even when it is automated.
- Order confirmations and shipping updates.
- Password resets and account verification codes.
- Booking or appointment confirmations.
- Invoices and payment receipts.
- Form submission acknowledgements.
These messages should be fast, short, and free of heavy sales language. Recipients expect them within seconds, not hours, and a delay reads as a broken system rather than a marketing choice.
What counts as marketing email
Marketing mail exists because your business chose to promote something to a list of people who opted in at some point, not because any one of them just triggered an action.
- Newsletters and product announcements.
- Promotional offers and seasonal campaigns.
- Re-engagement or win-back sequences.
- Event invitations and webinar reminders.
This mail lives and dies by consent, list hygiene, and complaint rates. A single send can go to thousands of people at once, which means a small percentage of unhappy recipients still adds up to a meaningful signal against your domain.
Why mailbox providers judge them by different rules
Providers expect transactional mail to be low-volume, highly relevant, and rarely reported as spam - because recipients asked for it in the most direct way possible, by taking an action. Marketing mail is expected to have higher volume, some unsubscribes, and a nonzero complaint rate. Providers tolerate that only when it stays within a low band. The moment your systems blur the line, a bad marketing send can drag transactional deliverability down with it, or the reverse: sloppy transactional volume can taint a domain a newsletter tool is trying to warm up.
What happens when you mix them on one domain
Picture a company sending order confirmations and a monthly newsletter from the exact same domain and IP pool. A single overly aggressive promotional campaign - bought list, unclear unsubscribe, misleading subject line - spikes complaints. Providers do not know that the order confirmations are a separate concern; they see one domain with a rising complaint rate and start filtering everything from it more aggressively, including receipts customers are actively waiting for.
A concrete example of the fallout
An online retailer runs a Black Friday campaign to a purchased list alongside its regular order confirmation and shipping-update emails, all from the same domain. The campaign draws a wave of spam complaints within hours. By the following Monday, customers who placed real orders that weekend report never receiving shipping confirmations - the entire domain's reputation dropped, and providers began throttling everything from it, transactional mail included. The campaign gets paused, but the damage to the domain's sending reputation takes weeks to recover, well after the sale itself is forgotten.
How to separate them properly
- Use distinct subdomains for each purpose - for example mail. or transact. for transactional traffic, and news. or updates. for marketing sends.
- Set up SPF, DKIM, and DMARC independently for each subdomain so a problem on one does not automatically implicate the other.
- Use a dedicated transactional provider (or your CRM/booking tool's built-in sender) for time-sensitive mail, and a purpose-built newsletter platform for campaigns.
- Keep marketing lists opt-in only, and make unsubscribing a one-click action rather than a multi-step form.
- Monitor complaint and bounce rates for each stream separately so a spike is easy to trace to its source.
Common mistakes
- Sending a newsletter from the same address customers associate with receipts and confirmations.
- Letting a CRM's default sending domain double as the marketing sender without review.
- Ignoring unsubscribe requests or making them hard to find, which converts a quiet opt-out into an angry spam complaint.
- Assuming one authentication setup covers every use case, instead of reviewing SPF and DKIM whenever a new sending tool is added.
- Running a promotional send to a purchased or scraped list right after a product launch, when transactional volume from new customers is already at its highest.
A short checklist before your next campaign
- Map every message type your business sends and label it transactional or marketing.
- Confirm each type has its own sending domain or subdomain.
- Verify authentication independently for each.
- Review complaint and bounce data by stream, not just in aggregate.
None of this requires exotic infrastructure - most CRMs, booking tools, and newsletter platforms already support subdomain sending; it just has to be configured on purpose rather than left on a shared default. At Killer Click we map transactional versus promotional mail during every website build, then choose tools and DNS so a marketing campaign can never quietly take down a customer's order confirmation.