Jeff This article was written by an expert AI about the Notifizz product and martech more broadly. If you notice any issue with the content, please let us know.

Transactional and promotional emails: why separate your sending streams

Notification fundamentals

A user requests a password reset. They wait. They check spam. The email arrived late, or it never arrived at all. Meanwhile, a promotional campaign you sent last week generated complaints, and those complaints weigh on everything sent the same way, including the password reset they asked for.

This risk exists as soon as transactional email and promotional email share the same sending stream. Mailbox providers judge the sender, not each email, and a complaint spike on one campaign can drag down everything sent the same way, including the messages people actually need.

Notifizz separates transactional and promotional sending streams automatically, by campaign category, with nothing to configure. This article explains why that separation matters, how it works in Notifizz, and where the protection stops.

The problem: reputation is shared by everything sent the same way

Mailbox providers do not evaluate each email in isolation. They judge the sender: the IP addresses mail comes from, and the domain it is sent from. When a newsletter generates complaints, that damage lands on everything that left the same way.

If your password resets, receipts, and security alerts travel on the same stream as your promotional campaigns, they pay for every complaint your marketing generates. A user who marked your newsletter as spam has just made it harder for the next person to receive their login link.

The person waiting for a password reset did not opt into anything. They triggered a message they need, and they need it immediately. Mixing that message with promotional mail means the recipient pays for a campaign they never consented to receive.

What separation actually means

Mailbox providers track reputation at two levels: the sending IP addresses and the domain. Full separation works on both, with different IP addresses for each type of message and, ideally, a different From address or domain.

When a complaint happens on the promotional stream, the IP reputation it damages is that of the promotional IP addresses, not the transactional ones. If both streams send from the same domain, the complaint still counts in that domain's spam rate.

This separation reduces the risk that a promotional campaign that generated complaints also degrades the deliverability of your transactional email.

How Notifizz separates sending streams

Notifizz runs exactly two sending streams: transactional, and promotional. The campaign's category decides which stream it uses, and the decision happens automatically, with no stream to configure and no provider setup.

Three campaign categories exist in Notifizz:

  • Transactional: mail the recipient triggered and needs, such as a password reset, a receipt, or a security alert. It cannot be opted out of, and it is served first in the sending order. Transactional campaigns travel on the transactional stream.
  • Product: messages a product event fires for one person, such as a digest, an onboarding nudge, or a win-back. The recipient can opt out on email and in the in-app inbox, globally or for one notification category. Product campaigns travel on the promotional stream.
  • Marketing: a broadcast to a CRM segment, in closed beta. The recipient can opt out of it as a whole, and it is served last so it never delays product mail. Marketing campaigns also travel on the promotional stream.

Product and Marketing campaigns share the promotional stream. Only Transactional campaigns use the transactional stream. This keeps password resets, receipts, and security alerts on their own path, apart from anything the recipient can refuse.

The from address and the sending domain remain the same across both streams: what is separated is the sending IP addresses.

How the category is chosen

A campaign nobody classified is read as Product, which means it travels on the promotional stream. Notifizz recommends a category from the campaign's name, with a strong bias against transactional, because filing a promotional campaign as transactional removes the unsubscribe.

When Notifizz recommends transactional, the campaign stays in the Editing stage until a team member confirms the choice. The recommendation is never applied automatically. Only a team member can make a campaign transactional.

This deliberate friction exists because the category decision has consequences. A promotional campaign filed as transactional rides the transactional stream, loses its unsubscribe, and damages the stream meant to carry password resets.

Suppression scope and the complaint-rate watchdog

Notifizz tracks suppressions separately for transactional and promotional sends. A hard bounce, a permanent rejection, blocks every email, transactional included, so that sends do not keep going to an address that refused them. A complaint on a transactional message also blocks every email. This is a cautious choice, not a reading of the person's intent: a complaint can be a slip, but continuing to write to someone who reported a transactional email is costly for reputation, and the sending provider blocks that address permanently.

A complaint on a promotional message blocks promotional email only: Product and Marketing campaigns alike. Transactional email continues to deliver, because the person still needs their receipts and security alerts even if they refused your newsletter.

An unsubscribe is not a suppression. It is a refusal recorded in the person's preferences, which they can reverse themselves from the hosted preference centre. A complaint, on the other hand, is never lifted.

Notifizz also tracks a complaint rate: the spam reports mailbox providers send back to it, divided by delivered emails over a rolling 7-day window. It compares that rate with the thresholds Gmail publishes for bulk senders: 0.1% raises a warning, 0.3% is critical. This is not Gmail's own rate: Gmail does not send spam reports back one by one, and only Google Postmaster Tools shows its rate, which Notifizz also displays once the domain is linked. At the critical level, Notifizz holds back list and segment sends on its own, a closed-beta surface that applies only to Marketing broadcasts. Event-triggered campaigns, both Product and Transactional, keep sending. The brake releases below 0.2%, a Notifizz rule set lower than the level that engaged it, so it does not switch on and off as complaints trickle in.

Email sending health shows delivered, bounced, and complaint counts broken down by mailbox provider family over 7 and 30 days, so teams can see when a problem is starting instead of discovering it after a password reset fails to deliver.

Where the separation stops

The separation is only as right as the category. A promotional campaign filed as transactional travels on the transactional stream, loses its unsubscribe, and risks damaging the stream meant for password resets. The platform recommends a category and never applies a transactional recommendation by itself, but the final choice belongs to the team. The category does not settle everything: in France, measuring a person's opens to evaluate a campaign requires their consent, even in a transactional email, as the CNIL's 2026 recommendation on tracking pixels spells out.

Both streams send from the same address and domain. The separation protects the stream's reputation, not the domain's. Domain authentication, content quality, and list hygiene still matter. A domain with poor authentication or a history of spam complaints will hurt both streams.

Notifizz does not separate one promotional campaign from another. Product and Marketing campaigns share the promotional stream. A Product campaign that generates complaints affects Marketing sends on the same stream, and the reverse is also true. The separation exists between transactional and promotional, not within promotional.

Why this matters for B2B SaaS

In B2B SaaS, transactional email is part of the product experience. A password reset that arrives late, or not at all, is a product failure, not a deliverability nuance. The person waiting for that email does not care that a newsletter generated complaints last week. They care that the product is not working.

Separating transactional and promotional sending streams means that a marketing campaign gone wrong does not drag the IP reputation of the product's email down with it: password resets, receipts and security alerts keep their own sending IP addresses.

Notifizz makes that separation automatic, by campaign category, with no provider setup and no stream to configure. The category decides the stream, and a transactional recommendation waits for a team member's choice. This keeps transactional email on its own path, where it belongs. The three categories are described in detail in the campaign documentation. Separating sending streams is only one of the components a notification system has to maintain after the first send: our guide to building or buying your notification system goes through them.

Build or buy your SaaS notification system: what you have to build after v1 image.

Build or buy your SaaS notification system: what you have to build after v1

The first notification is easy. Building a reliable system that lasts, and that marketing, dev and product can share, is another matter. The six components to maintain, a three-year cost method, and when to build or buy.

Comparisons and alternatives

Jeff

This article was written by an expert AI about the Notifizz product and martech more broadly. If you notice any issue with the content, please let us know.

Tracking pixels in SaaS emails: the CNIL's 2026 recommendations and alternatives to the open rate image.

Tracking pixels in SaaS emails: the CNIL's 2026 recommendations and alternatives to the open rate

The CNIL's 2026 recommendation spells out how consent applies to email tracking pixels, transactional emails included. What changes for a SaaS's emails, what the exemptions cover, and how to measure a campaign without relying on the open rate.

Notification fundamentals

Jeff

This article was written by an expert AI about the Notifizz product and martech more broadly. If you notice any issue with the content, please let us know.