Campaigns and receipts, one account, metered apart
Most teams run a marketing tool and a separate transactional provider: two bills, two sending reputations, two dashboards to check when something breaks. Bluey sends both, and meters them separately so neither can starve the other.
Bluey sends marketing campaigns and transactional email from the same account, with separate volume metering so a large campaign can never consume the headroom your password resets need. Transactional starts at ₹250 / $4 a month for 15,000 emails, with SMTP and REST, domain authentication, suppression handling and event webhooks. The usual alternative is a marketing platform plus a dedicated transactional provider — which means two invoices, two reputations to manage, and contact data split across two systems. On SendGrid's Email API plans the two share one monthly quota, so the problem is the reverse: they compete.
The receipt that went to spam
Every business sends two kinds of email. One you decide to send — campaigns, newsletters, launches. One the customer triggers — receipts, password resets, shipping notices, invoices. They have different urgency, different volumes and different consequences when they fail, and almost every stack handles them with two separate vendors.
The failure mode is quiet and expensive. A password reset does not arrive; the customer assumes the account is broken and leaves. An order confirmation lands in spam; a support ticket arrives instead. Nobody investigates, because the transactional provider was set up once by an engineer who has since moved on and nobody checks its dashboard.
The underlying cause is usually authentication drift. The marketing domain was warmed and monitored because a marketer looks at it weekly. The transactional domain was configured in an afternoon two years ago and has not been checked since.
Why one platform and two meters is the right shape
The naive fix is to send everything through one pipe. That is worse, not better: a marketing campaign that generates complaints would then damage delivery of your receipts, which is the one category of email that must always arrive.
The right arrangement is one platform, separate metering and separate reputation tracking. You get a single bill, one set of authentication records to maintain, and one contact record — while the two streams stay isolated where isolation matters.
- Separate volume metering — a heavy campaign month cannot consume your transactional allowance, and a spike in receipts cannot eat your campaign quota.
- Separate reputation tracking per stream — a marketing complaint problem does not follow your operational mail.
- One set of DNS records — SPF, DKIM and DMARC published once and monitored continuously, rather than twice with one half forgotten.
- One contact record — a purchase that triggers a receipt is the same event that should exit someone from a cart-recovery flow. Across two vendors, that requires an integration; here it does not.
- Transactional from ₹250 / $4 for 15,000 emails, ₹749 / $14.95 for 100,000 — with SMTP, REST, suppression handling and event webhooks on the entry tier.
Two vendors, or one
Bluey figures are exact: Grow marketing plus transactional Essentials. The two-vendor column is a typical marketing plan plus a typical transactional plan at the same volumes, drawn from the published figures on our comparison pages — an illustration of the arrangement, not a quote for a named pair of products.
| Scenario | Per-contact model | Bluey |
|---|---|---|
50,000 marketing + 15,000 transactional Small store or early SaaS | ~$60/mo across two bills | $34/mo, one bill |
100,000 marketing + 100,000 transactional Established store | ~$225/mo across two bills | $50.95/mo, one bill |
250,000 marketing + 300,000 transactional Scaling business | ~$400/mo across two bills | $113.95/mo, one bill |
When two vendors is the right answer
Consolidation is not automatically correct, and there are cases where the split is deliberate and sensible.
- You need inbound email routing as part of your product. Mailgun does that well and Bluey does not do it at all.
- You need long message retention for debugging or compliance — Postmark keeps 45 days, extendable to 365, against 3 to 7 here.
- You are already at a scale where a dedicated provider's infrastructure guarantees and SLA matter more than the invoice.
- Your engineering team has standardised on a provider across several products, and one product's email is not worth breaking that.
- You want vendor redundancy on operational mail deliberately, so a single provider outage cannot stop your password resets.
What you give up
- Redundancy. One provider is one point of failure for both streams. If your operational email is business-critical enough to warrant a second vendor as a fallback, that is a legitimate reason to keep two.
- Message retention. 3 days on transactional Essentials and 7 on Pro is genuinely less than a dedicated provider offers, and if you rely on long history to debug, that is a real loss.
- Best-of-breed depth. Postmark's deliverability record and Resend's developer experience are each better than ours in their own dimension.
Questions
Can transactional and marketing really share one account?
Yes, and they are metered separately so neither can starve the other. This is worth checking against alternatives — on SendGrid's Email API plans marketing and transactional draw on the same monthly volume, which means a campaign near the end of a cycle can consume the headroom your password resets need.
Do they share a sending reputation?
Reputation is tracked per stream and you can use separate sending domains, so a marketing complaint problem does not follow your operational mail. That separation is the reason to run two meters rather than one pipe.
What does the transactional side actually include?
SMTP relay and REST API, SPF/DKIM domain authentication, suppression management, full analytics, 2 event webhooks and 5 API keys on Essentials from ₹250 / $4 for 15,000 emails. Pro adds 5 webhooks, unlimited API keys, subuser management and a 7-day searchable activity feed.
How hard is it to move my transactional email across?
Usually an afternoon. Both SMTP and REST are supported, so for most providers it is a host, a username and a password — or repointing one API call. Authenticate the domain and import your suppression list before the first send, then ramp volume over a few days.
Will consolidating actually save money?
Usually, but check it rather than assume. Add your current marketing and transactional invoices together and compare against the equivalent Bluey tiers. If you are on a cheap grandfathered plan for one of them, the arithmetic may not favour moving.
Keep exploring
Check it against your own bill.
Seven days of full access, no credit card. Or put your list size and send volume into the calculator first — it will tell you if switching would not save you anything.