Marketing vs transactional email: which tool sends what
Transactional email delivers 1:1 action receipts; marketing email delivers 1:many broadcasts, requiring separate domains to protect deliverability.
On this page 7 sections
Transactional email delivers critical, one-to-one messages triggered by user actions, while marketing email delivers broadcast announcements and automated sequences to lists of subscribers. Transactional messages include order confirmations, password resets, and receipts that individuals expect immediately. Marketing messages include newsletters, promotional offers, and product updates that require explicit consent, a physical postal address, and an unsubscribe link under commercial email laws.
Mixing these two message types on the same IP or sender domain creates serious operational risk. If a marketing campaign triggers spam complaints, your domain reputation drops and your password reset messages land in the spam folder or get delayed.
Here is how transactional and marketing emails differ, which tools send what, and how to configure both without crossing the streams.
Key differences: purpose, consent, and delivery rules
Transactional and marketing messages serve opposite functions, carry different legal requirements, and follow distinct technical flows.
| Characteristic | Transactional Email | Marketing Email |
|---|---|---|
| Trigger | User action (signup, purchase, password reset) | Business action or scheduled workflow |
| Recipients | Exactly one person per event | Many people (lists, segments, or audiences) |
| Legal Consent | Implicit (implied by the user's action or contract) | Explicit opt-in required (checkbox, form signup) |
| Unsubscribe Link | Not required (and often forbidden by law) | Legally mandatory (one-click header and body link) |
| Physical Address | Not required | Legally mandatory in the footer (CAN-SPAM) |
| Sending Speed | Real-time, instant delivery expected | Batched or ramped over hours/days |
| Pricing | Fraction of a cent (~$0.00013 per send) | $0.001 per send ($1 per 1,000 emails) |
| Failure Impact | User cannot log in or verify purchases | Missed campaign opens, lower brand reach |
Because of these differences, inbox providers evaluate them on separate criteria. For a deeper look at the underlying authentication records that protect both streams, read DKIM, SPF and DMARC: email deliverability basics, done for you.
Why you must separate sending reputations
Every domain and subdomain earns an independent sending reputation with mailbox providers like Gmail, Yahoo, and Outlook. If you send marketing broadcasts from the exact same address you use for account security, a single poorly cleaned list can cripple your business.
When a marketing broadcast suffers high bounce rates or recipients click "Report Spam," inbox filters treat that sending address with suspicion. On thelastapi, marketing sending is blocked for a project if bounces exceed 5% or complaints exceed 0.3% over 30 days.
To keep your essential app communications safe:
- Transactional emails send from your root mail domain or mailbox, such as
info@acme.vibiz.apporhello@yourcompany.com. - Marketing emails send from a dedicated subdomain, such as
hello@news.acme.vibiz.appornews.yourcompany.com.
Because marketing uses its own sub-identity, a newsletter that hits a spam trap can never pause your project's password resets or purchase receipts. You can read more about setting up your transactional pipe in Send transactional email from your app without touching DNS.
Sending transactional email from your app
Transactional messages should be sent via an API endpoint or SDK method triggered directly by your application's business logic.
To add transactional email to a project:
vibiz add emailYou can send a one-off transactional message from your terminal:
vibiz send --to ana@example.com --subject "Your order is ready" --text "Pick it up any time today." --from ordersIn your application code (server-side with @vibiz/app), use the vibiz.email.send method. Always pass a reply_to address so customers can reach a real person:
import { vibiz } from '@vibiz/app';
await vibiz.email.send({
to: 'ana@example.com',
subject: 'Your order is ready',
text: 'Pick it up any time today.',
from: 'orders', // orders@<slug>.vibiz.app
reply_to: 'support@example.com',
});You can also send transactional emails over plain HTTP:
curl https://thelastapi.dev/v1/projects/prj_123/actions/email.send \
-H "Authorization: Bearer $VIBIZ_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-verify-456" \
-d '{"input":{"to":"ana@example.com","subject":"Welcome","text":"Hi Ana","from":"hello"}}'Transactional sending includes built-in safeguards:
- Daily limit: 50 emails per project per UTC day across all mailboxes by default.
- Single recipient: Each API call accepts exactly one
toaddress. - Idempotency: Pass an
Idempotency-Keyheader so retrying network timeouts will not send duplicate receipts to a customer.
For complete route definitions, review the Email documentation. If you are building user registration flows, see Send a welcome email from a Next.js app for a practical implementation.
Managing contacts, broadcasts, and marketing campaigns
Marketing email requires a list management system, campaign authoring, audience filtering, and compliance tooling. In thelastapi, you set up marketing by provisioning a dedicated sender address:
curl -X POST https://thelastapi.dev/v1/projects/prj_123/email/marketing/setup \
-H "Authorization: Bearer $VIBIZ_API_KEY"Next, configure your required compliance settings. Marketing emails will not send without a valid postal address:
curl -X PATCH https://thelastapi.dev/v1/projects/prj_123/email/marketing \
-H "Authorization: Bearer $VIBIZ_API_KEY" \
-d '{
"from_name": "Acme",
"reply_to": "hello@acme.com",
"postal_address": "1 Main St, Springfield, IL 62701, USA"
}'Tracking contacts and consent
Contacts must be captured with clear consent records. You can sync users from your app runtime:
import { vibiz } from '@vibiz/app';
await vibiz.contacts.upsert({
email: 'ana@example.com',
first_name: 'Ana',
lists: ['Users'],
properties: { plan: 'pro', signed_up_at: new Date().toISOString() },
consent: { method: 'app_signup', text: 'Send me product updates' },
});
// Track an event to drive automation triggers
await vibiz.contacts.track('ana@example.com', 'upgraded', { plan: 'pro' });Sending broadcasts and handling unsubscribes
A broadcast delivers an announcement to a list or segment:
vibiz email broadcast create \
--name "Product Update" \
--subject "New features in May" \
--file update.md \
--list UsersBefore sending, verify the broadcast using the review check:
curl https://thelastapi.dev/v1/projects/prj_123/email/broadcasts/bc_123/review \
-H "Authorization: Bearer $VIBIZ_API_KEY"The review verifies the postal address, missing alt tags, merge tag fallbacks, link protocols, and audience size against your credit balance. When you schedule or send, the cost ($0.001 per recipient) is held from your credits.
Every marketing message automatically includes:
- RFC 8058 one-click unsubscribe headers shown by Gmail and Yahoo.
- A footer with your business name, physical postal address, and unsubscribe link.
- Automated bounce and spam filtering. If a contact unsubscribes, their status updates immediately, and future attempts to email them are suppressed.
Automated onboarding sequences
Automations run background sequences based on triggers like contact creation, date thresholds, or event calls.
For example, this automation welcomes a user, waits two days, checks whether they opened the message, and branches:
{
"name": "Onboarding",
"trigger": { "type": "contact_added", "list_id": "Users" },
"exit_event": "upgraded",
"steps": [
{
"id": "welcome",
"type": "email",
"subject": "Welcome, {{{FIRST_NAME|friend}}}",
"body": "Here is how to get started with your account."
},
{ "type": "wait", "days": 2 },
{
"type": "condition",
"if": { "email_step": "welcome", "did": "opened" },
"yes": [{ "type": "email", "subject": "Three advanced tips", "body": "..." }],
"no": [{ "type": "email", "subject": "Did you see this guide?", "body": "..." }]
}
]
}If the customer triggers the upgraded event at any time during this sequence, the automation exits immediately.
Which tool should you use?
Use this checklist when picking your approach:
- Triggered by an individual user action? Use transactional email (
vibiz.email.send). It arrives immediately, uses minimal tokens, and bypasses marketing unsubscriptions so crucial system notices always reach the user. - Scheduled product news, newsletters, or sales promotions? Use marketing email (
vibiz email broadcast). It isolates your domain reputation, inserts legal unsubscribe footers, and throttles delivery across clean ramp-up periods. - Multi-day drip sequences or trial reminders? Use email automations (
vibiz email automation). - Receiving and answering customer inquiries? Use a project mailbox (
vibiz email mailbox add hello@yourdomain.com) to read, archive, and reply to threaded conversations.
Keep transactional messages simple, functional, and immediate. Put announcements and promotional campaigns on a dedicated subdomain, and never import an audience list without explicit opt-in consent.
To get started with an isolated mail setup for your project, create your account at thelastapi.dev/start or browse the Email documentation.
Frequently asked questions
Can I send marketing newsletters using transactional email endpoints?
No. Transactional endpoints lack mandatory legal features like automated one-click unsubscribe headers and physical address footers, and their 50-email daily limit makes broadcasts impractical.
What happens if someone unsubscribes from my marketing emails?
They are marked as unsubscribed and automatically suppressed from future marketing broadcasts, but they can still receive critical transactional emails like password resets.
Why does my marketing broadcast pause automatically?
Broadcasts pause automatically if hard bounces exceed 2.5% or spam complaints exceed 0.08%, protecting your domain reputation until bad addresses can be reviewed and removed.