Picture a founder a few months after launch. Password resets and receipts go out through one email service, wired up in a weekend. Newsletters and the welcome sequence live in a second tool. A customer upgrades, gets the receipt within seconds, and never gets the "here's what Pro unlocks" email, because in this setup the upgrade event only reached the first system.
That is the real question behind putting transactional and marketing email on the same platform. In a setup like that founder's, keeping the two tools in step is extra work someone has to do. This article is for founders and small product teams deciding whether one platform can do both jobs, and when two still makes sense.
What transactional and marketing email each do
Transactional email answers something a person just did: a password reset, a receipt, a shipping update. It's automated, one-to-one, and triggered by the action.[1] People implicitly opt into it by taking the action.[2]
Marketing email is something your team starts: newsletters, promotions and lifecycle sequences.[1] In Pombo it goes only to people who gave permission, and an unsubscribe stops it.
The two follow different rules. Transactional vs marketing email covers the test for which bucket a message belongs in. The question here is narrower: does keeping them in different tools help you follow those rules, or just make it harder?
Transactional and marketing email on the same platform: what gets simpler
Two things get easier when both kinds of email share one system.
One event can do both jobs. In Pombo, your backend posts an event once, and that one event can send a transactional email and start a marketing sequence at the same time. Both are bound to the event's name and run independently. A plan.upgraded event can send the receipt immediately and also start a short "getting the most from Pro" sequence:
POST https://flypombo.com/api/v1/events
Authorization: Bearer pombo_...
{
"event": "plan.upgraded",
"email": "[email protected]",
"properties": { "plan": "pro" }
}
In the founder's setup above, that one upgrade would have had to reach both tools. The events docs show what a single event can drive in Pombo.
One contact, with suppression applied by kind of email. Pombo keeps one status per contact and applies it the way the rules intend. Someone who unsubscribes stops getting marketing but still gets their receipts, because a receipt is not a promotion. A hard bounce or a spam complaint stops everything, transactional included. If you run two tools, check how an unsubscribe or a complaint recorded in one reaches the other. Suppression lists each status.
What one platform doesn't change
One tool doesn't merge the rules. Pombo asks every organization to attest that it only emails people who gave permission, so a contact being in your product database isn't enough on its own. Unsubscribes and suppression are always honoured. Every send also passes the same gates: an approved account, that attestation, a verified sending domain and the weekly cap. Sending gates has the detail.
Does deliverability require separate tools?
Not necessarily. Customer.io's documentation describes separating transactional and marketing domains as a way to keep marketing mail from affecting critical transactional messages.[2] Some write-ups point out that many mature setups separate the two streams even on a platform that supports both.[1] Both points are about separate domains or streams, which you can have without a second tool.
In Pombo, every transactional send names its own from address, which must be on a verified sending domain, and each sequence sets its own from address too. So receipts can come from receipts@ on one verified domain while marketing comes from another. Sending a transactional email by API looks like this:
POST https://flypombo.com/api/v1/transactional_emails
Authorization: Bearer pombo_...
{
"template": "receipt",
"to": "[email protected]",
"from": "[email protected]",
"variables": { "plan": "Pro" }
}
Sending by key covers the options, including binding a template to an event so the event triggers the send instead of a separate transactional request. Verify your sending domain covers adding a domain.
When two tools still make sense
Keep two tools when there's a specific requirement the single platform can't meet. Examples are a contract or compliance rule that demands separate vendors, or a sending volume or feature your current transactional provider handles and the new platform doesn't. Write the requirement down. If you can't name one, it's worth asking whether the second tool is still needed or was simply the fastest way to send the first password reset.
Moving from two tools to one
If you decide to consolidate, move in an order that never leaves a message without a sender.
- Bring contacts and their status across first. Import unsubscribed, bounced and complained contacts with those statuses, so nobody who opted out is mailed again. Migrating covers what comes over.
- Recreate the transactional templates and test each one with a test send before switching anything.
- Point one event at a time at the new platform. Start with the event that drives both a receipt and a follow-up, so you can see both fire from a single post.
- Retire the old sender only when its traffic has dropped to zero.
Moving one event at a time keeps each change small and easy to check.
A simple way to decide
List the messages that are critical to using your product, the marketing sends you plan to run, and the events that should start each one. Then check one platform against that list: can one event drive both the receipt and the follow-up, does an unsubscribe stop marketing but not receipts, and can each kind of email come from its own address? If the answer is yes to all three, one platform covers both jobs with fewer connections to maintain.
Start free to build both in one place. You can set up templates and sequences and import contacts while your account is reviewed for sending.
Frequently asked questions
Can transactional and marketing email run on the same platform?
Yes. In Pombo one event can send a transactional receipt and start a marketing sequence at the same time, and each kind of email can come from its own address on a verified sending domain.
Does putting both on one platform hurt deliverability?
Deliverability advice is about separating domains or sending streams, not tools. In Pombo every transactional send and every sequence sets its own from address, so receipts and marketing can come from different verified domains.
Do unsubscribed contacts still get receipts?
Yes. In Pombo an unsubscribe stops marketing email but not transactional email, because a receipt is not a promotion. A hard bounce or a spam complaint stops everything.
When should I keep two separate email tools?
When there's a specific requirement one platform can't meet, such as a contract or compliance rule that demands separate vendors, or a feature your current provider has that the new platform doesn't.
