Solution — Transactional and marketing email

Manage marketing and transactional email from one platform.

Marketing campaigns and transactional messages are different types of email with different requirements. AledaMail handles both in one platform while keeping them on appropriate infrastructure — separate domains, streams, and suppression lists where it matters for deliverability.

Start free → Transactional email features

Two different types of email

Marketing email and transactional email are not the same thing.

They have different purposes, different compliance requirements, different deliverability characteristics, and different suppression rules. Understanding the distinction matters before deciding how to manage both.

Marketing email

Newsletters and product updates
Promotional campaigns
Lifecycle sequences (onboarding, trial conversion)
Re-engagement campaigns
Nurture and educational content
Requires unsubscribe mechanism (CAN-SPAM, GDPR)
Suppressed by unsubscribe or complaint
Sent to opted-in subscribers
Performance tracked by open rate, click rate, conversion

Transactional email

Password reset and account confirmation
Purchase receipts and invoices
Account alerts and system notifications
Payment failure notifications
Security alerts (login from new device, etc.)
Triggered by a specific user action
Generally not suppressible by marketing unsubscribe
Must reach the recipient — deliverability is critical
Performance tracked by delivery rate and latency

Should marketing and transactional email share the same infrastructure?

Not always — and not without thought. A marketing campaign that generates spam complaints can damage the sender reputation of the domain and IP you use for transactional email. If a customer marks your newsletter as spam and your password reset goes to their spam folder as a result, that is a real problem.

The right approach depends on your sending volume, domain strategy, and provider. At minimum, most teams should use separate sending domains for marketing and transactional email. At higher volume, separate IP pools are worth considering. AledaMail makes it straightforward to configure this separation without requiring two completely separate platforms.

How AledaMail manages both

One platform. Appropriate separation where it matters.

AledaMail includes a dedicated transactional email API alongside the full marketing platform. Both can route through your own sending infrastructure, with separate configurations per email type.

Separate sending streams

Configure different sending domains or accounts for marketing and transactional email. Marketing campaign reputation is isolated from your transactional deliverability. Both managed from one platform interface.

Separate suppression lists

A marketing unsubscribe does not automatically suppress transactional email. Transactional messages like password resets can still reach users who have opted out of marketing. Suppression rules are configured per email type.

Transactional REST API

A dedicated REST API for transactional sends. Template-driven with variable substitution. Separate event webhooks for delivery, bounce, and complaint events on transactional messages.

Marketing campaign platform

Full campaign builder, automation workflows, subscriber management, segmentation, and analytics for marketing email — on the same account, without interfering with transactional sending.

BYOS per stream

Connect different sending providers or accounts per stream if needed. Marketing campaigns through one Amazon SES sending identity. Transactional through another. Or both through the same account on different domains.

Unified template management

Manage email templates for both marketing and transactional messages in one place. Consistent branding without duplicating template infrastructure across two separate tools.

Transactional email API

Send transactional messages via REST API.

The AledaMail transactional API accepts send requests, renders templates with variable substitution, routes through your sending infrastructure, and fires webhook events on delivery, bounce, and complaint.

// Send a transactional message via AledaMail API
POST https://mxa.aledamail.com/api/tx/v1/messages/send

{
  "to": [{ "email": "user@example.com", "name": "Jane Smith" }],
  "template_id": "password-reset",
  "variables": {
    "reset_url": "https://app.example.com/reset/abc123",
    "expiry_minutes": "30",
    "first_name": "Jane"
  }
}

// Response
{
  "message_id": "tx_01J9XYZ...",
  "status": "queued"
}
    

Common questions

Questions about managing both email types.

Should transactional and marketing email share the same sending domain?

Generally no, especially at meaningful volume. Marketing campaigns can generate spam complaints that affect the reputation of the sending domain. If that domain is also used for password resets and receipts, transactional deliverability suffers. Using separate sending domains — one for marketing, one for transactional — is the standard recommendation. Your sending provider allows you to configure multiple sending identities, and AledaMail can be configured to use different ones per email type.

If a user unsubscribes from marketing email, do they still receive transactional email?

With proper configuration, yes. Marketing unsubscribes are stored in AledaMail's suppression list for marketing campaigns. Transactional messages — password resets, receipts, account alerts — use a separate suppression scope and are not blocked by a marketing unsubscribe. This is the legally correct and operationally expected behaviour: a user who unsubscribes from your newsletter should still receive their password reset.

Can I use the same sending provider for both email types?

Yes. You can use the same Amazon SES or SendGrid account for both, while routing each type through a different sending domain or identity on that account. The provider handles delivery for both. AledaMail manages the routing, suppression, and templates for each type separately.

Do I need two separate platforms for marketing and transactional email?

No. AledaMail includes both a full marketing platform and a transactional REST API in one product. The separation that matters — sending domains, suppression lists, and stream configuration — is handled within AledaMail, not by using separate tools.