Every email a business sends falls into one of two categories: transactional or marketing. Confusing the two — or treating them identically — leads to compliance problems, deliverability issues and subscriber frustration. Understanding the distinction is foundational to a well-run email programme.
What Is Transactional Email?
A transactional email is sent in direct response to an action the recipient has taken. The primary purpose is to deliver information the recipient needs — it is not promotional. Common examples:
- Order confirmation and receipt
- Shipping notification and tracking updates
- Password reset and account verification
- Subscription confirmation (double opt-in)
- Invoice and payment receipt
- Two-factor authentication codes
- Account activity alerts
- Support ticket updates
The defining characteristic of a transactional email is that the recipient triggered it by taking an action. They expect to receive it. The email fulfils an obligation or delivers information they specifically need.
What Is Marketing Email?
A marketing email is sent to promote a product, service, offer or brand. It is initiated by the sender, not triggered by a recipient action. Common examples:
- Newsletter and editorial content
- Promotional offers and discounts
- Product announcements and launches
- Re-engagement campaigns
- Event invitations
- Content marketing and thought leadership
- Abandoned cart reminders
Marketing email requires explicit consent under GDPR (for EU recipients) and must include an unsubscribe mechanism. The legal framework is significantly stricter than for transactional email.
Key Legal Differences
GDPR and consent
Under GDPR, marketing email requires a lawful basis for processing — typically consent (Article 6(1)(a)) or legitimate interests (Article 6(1)(f)) for existing business relationships. This means you generally cannot send marketing email to someone who has not opted in.
Transactional emails are generally not subject to the same consent requirements, because they are sent to fulfil a contract or comply with a legal obligation — both valid GDPR lawful bases (Article 6(1)(b) and 6(1)(c)). However:
- A transactional email cannot contain significant marketing content without triggering consent requirements
- The purpose must genuinely be transactional — not a pretence to reach non-consenting contacts
- Unsubscribing from marketing should not affect delivery of genuine transactional emails
CAN-SPAM (US)
Under CAN-SPAM, transactional messages are exempt from most requirements if the primary purpose is transactional. Marketing messages require a physical address, unsubscribe mechanism and honest subject lines. Sending marketing content under the guise of a transactional email violates CAN-SPAM.
Technical Differences
Sending infrastructure
Transactional and marketing emails should ideally use separate sending domains or subdomains. The reason: transactional emails must reach the inbox — a password reset that lands in spam is a broken user experience. Marketing emails, even well-intentioned ones, carry more inbox risk. Separating infrastructure protects transactional delivery from any reputation impact from marketing sends.
Common approach: use mail.yourdomain.com for transactional email and news.yourdomain.com for marketing email. Each has its own DKIM key, SPF record and sender reputation.
Authentication requirements
Both transactional and marketing email require DKIM, SPF and DMARC. For transactional email, missing authentication is more damaging — a failed authentication check on a password reset email means the recipient cannot securely act on it.
Timing
Transactional emails should be sent immediately — a password reset that takes five minutes to arrive causes support tickets and abandoned sessions. Marketing emails can be batched and scheduled. NexusProMail's transactional API delivers immediately via a dedicated endpoint, while campaign sends use the standard scheduled sending engine.
When the Lines Blur: Mixed-Purpose Emails
Some emails contain both transactional and marketing content — an order confirmation that also includes a "You might like..." product recommendation, for example. The regulatory treatment depends on the primary purpose:
- If the primary purpose is transactional (delivering order information) and the marketing element is minor and clearly secondary — generally treated as transactional
- If the marketing content is prominent enough to be considered a primary purpose — treated as a commercial/marketing message and subject to consent requirements
The safest approach: keep transactional emails purely transactional. Add marketing content only where you have clear consent. When in doubt, separate the sends.
Managing Both from One Platform
NexusProMail handles both transactional and marketing email from a single account:
- Transactional email: sent via the REST API endpoint (
/v1/transactional/send) with immediate delivery, per-send authentication and full logging - Marketing email: campaign builder with segmentation, scheduling, A/B testing and performance analytics
- Suppression enforcement: transactional sends bypass marketing suppression lists (so a customer who unsubscribed from marketing can still receive their invoice) while respecting hard bounces and complaint-based global suppressions
- Separate subdomains: configure distinct sending subdomains per use case to isolate reputation
Read the transactional email API documentation or the GDPR compliance guide for further detail.
Summary: Transactional vs Marketing
| Factor | Transactional | Marketing |
|---|---|---|
| Trigger | Recipient action | Sender initiated |
| GDPR consent | Not required (contract/legal basis) | Required (consent or LI) |
| Unsubscribe required | No (for purely transactional) | Yes — always |
| Timing | Immediate | Scheduled or batched |
| Infrastructure | Dedicated subdomain recommended | Separate subdomain recommended |
| Content | Information recipient needs | Promotional or editorial |