Transactional vs Marketing Email

Transactional vs marketing email

Disclosure: SendNeo is built by Yorker Media, the team behind this blog.

A password reset and a product newsletter can come from the same company, but they are different messages with different expectations. Transactional email completes an action a person requested: a receipt, invitation, login code, alert, or confirmation. Marketing email promotes a product, publication, or offer to an audience. Separating those jobs helps recipients understand the message and helps your team respond when delivery changes.

You can keep both lanes in one SendNeo account. The important part is to separate the workflows, audiences, and decisions that produce them.

What transactional mail does

Transactional mail is tied to an event. A customer places an order and needs a receipt. A new user asks for a password reset. A subscriber confirms an address and receives a welcome message. The message should be timely, expected, and limited to the information that completes the event.

Use the SendNeo API for this lane. POST /emails accepts the sender, recipients, subject, HTML or text body, reply address, headers, tags, schedules, and attachments. Add an idempotency key so a retry after a timeout does not create a duplicate receipt. Use webhooks to record sent, delivered, bounced, complained, and failed outcomes.

A transactional stream still needs accurate authentication and a clean sender. It should not be a loophole for an unrelated promotion. If a receipt contains a small product note, keep the purpose clear and follow the rules that apply to the message in your jurisdiction.

What marketing mail does

Marketing mail is sent to an audience because the recipient chose to receive a publication, update, or offer. It can be a newsletter issue, a launch announcement, or a re-engagement message. The recipient needs a visible unsubscribe, a sender they recognize, and a clear explanation of why the message arrived.

Use SendNeo audiences and broadcasts for this lane. Audiences hold contacts, tags, sign-up settings, and a welcome email. Broadcasts can be written in Markdown or HTML, previewed, tested, scheduled, and published in a public archive. Broadcasts include RFC 8058 one-click unsubscribe headers. A postal address belongs in the message footer for CAN-SPAM compliance.

Tracking is off by default. If you enable it for a broadcast, interpret open data carefully because Apple Mail Privacy Protection makes opens unreliable. Delivered, bounced, complained, unsubscribed, and reply signals tell you more about whether the audience wants the message.

Why keep one account?

A product and a publication often share a verified domain, an owner, and a billing team. One SendNeo account avoids duplicating domain verification and contact administration. The API can send a receipt while the newsletter team prepares an issue, and GET /usage gives one view of the account allowance.

Pricing is also based on emails sent, never contacts. Contacts are unlimited on every plan. Free is $0 for 3,000 emails per month with a 100-per-day maximum; Starter is $9 for 30,000; Growth is $19 for 75,000; Pro is $49 for 200,000; Scale is $99 for 500,000; and Business is $199 for 1 million. Yearly billing gives two months free, and every paid plan includes every feature.

The account is shared; the lanes are not merged. Keep a transactional key in the application secret store, keep an audience owner in the publishing workflow, and give an AI agent only the MCP tools it needs.

What happens at the monthly limit

A shared account should have a safe failure mode. When a plan’s monthly email allowance runs out, SendNeo lets transactional messages and welcome or confirmation emails continue for up to 20% more while you upgrade. Broadcasts wait. That means an issue may be delayed while a password reset or a new-subscriber confirmation keeps working.

Forecast both lanes. A newsletter may use most of the normal allowance during a launch, while an application creates a steady stream of receipts. Use GET /usage and set an internal alert before the limit. A plan change is easier when you make it before the critical-mail window begins.

Deliverability is shared, responsibility is specific

SendNeo automatically suppresses hard-bounce and complaint addresses for the account. A broadcast pauses above 2% bounces or 0.08% complaints, and an account pauses for review at 5% bounces or 0.3% complaints. These protections contain a campaign problem, but they cannot turn an unwanted list into wanted mail.

For marketing, use double opt-in, import only permission-based addresses, and keep one-click unsubscribe. For transactional mail, send only in response to the event and keep the recipient address tied to the account action. Authenticate both paths with SPF, DKIM, and DMARC and monitor webhook events.

New accounts begin in review. Until a quick human review usually completed within one business day, live keys can send only to your own verified team emails. Test keys work fully. Use that time to test both lanes and make sure a campaign cannot accidentally reach the transactional audience.

A practical separation

Name the streams in code and in the dashboard:

transactional: receipts, resets, invitations, confirmations
marketing:      newsletters, launch notes, offers, editorial issues

Give marketing broadcasts their own audience and tags. Keep the application’s event handler responsible for transactional calls. Route complaints and unsubscribes to a shared suppression record, but keep the reason and source visible. A person who leaves a newsletter should not automatically lose a necessary account receipt, while a hard bounce should be handled consistently.

Choose the right lane before you write

Ask why the recipient is receiving the message, what action they expected, and whether the message would still be sent if they had not subscribed to a publication. If the answer is an account event, use the API. If the answer is an audience relationship, use a broadcast and its unsubscribe controls. If it is both, rewrite the message or split it into two sends so the expectation is honest.

Read Sending, Newsletters, and Deliverability for implementation details. One account can simplify operations, but clear lanes are what keep the recipient experience predictable.

Templates and ownership

Give each lane its own templates and owners. The application team can own receipt and reset templates, while the editorial team owns a newsletter layout and archive settings. Review sender names, reply addresses, and links separately. A shared domain does not require a shared template folder.

When an address changes, preserve the reason and source in your contact record. A person may unsubscribe from an editorial audience while still needing an account alert. A hard bounce may indicate that the account address itself needs attention. Clear event types help your team make that distinction without guessing.

Launch both lanes intentionally

For a new product, send a test receipt and a test issue before inviting outside recipients. Verify DNS, webhook signatures, the visible unsubscribe, and the archive. Use the deterministic addresses in Test mode to exercise delivered, bounced, and complained outcomes. Then start with a small, permission-based audience and watch the signals before increasing volume.

A single account can be convenient without becoming a single undifferentiated stream. Keep the purpose, permission, and failure behavior visible, and the platform can serve both the product and the publication without making recipients wonder why they received a message.

For the budget side of the decision, see Per-email vs per-subscriber pricing.