Key takeaway
The twenty-odd named types of email marketing sort onto a single axis, what starts the send, and collapse into three families: broadcast, triggered, and transactional. The family is the useful part. It decides the consent basis the message needs, the rules it's judged by at the mailbox provider, and which of three things you build: a campaign aimed at a segment, a flow with an entry condition, or a template plus an API call. I stop counting names at three.
Each of these types has its own shelf in the email example library, with real sends rather than mockups.
What counts as a type of email marketing.
A type of email marketing is a category of message defined by three things: what it's for, who receives it, and what caused it to be sent. That definition is flat, correct, and liftable from any page on the subject. The trouble starts one line later, when the page hands you a numbered list.
The lists sorting this question aren't sorted. One popular set of twenty-one puts promotional, transactional, and marketing beside each other as three siblings, when the last is the parent of the first and the middle one is the class the other two aren't. Another puts drip next to promotional, but drip is a schedule that almost any type can be sent on. A third offers dedicated, which isn't a message type at all: it's a commercial arrangement where you pay to appear in somebody else's send. Counting names isn't the same as understanding them.
That matters for a reason which isn't tidiness. The three families hiding under those names sit on different footings, need different permission, and take different things to build. A list that mixes them tells you nothing about the work in front of you, which is the thing you came to find out.
Naming a type also stops short of the thing you need. It says nothing about whether you're allowed to send it to the person you have in mind, and the answer to that changes from one family to the next.
The three families every type belongs to.
Sort the names on one axis, what starts the send, and every list collapses into three families. Not seven, not twelve, not twenty-one. Three. Everything you'll meet is either a broadcast you decided to send, a triggered message the contact set off, or a transactional message somebody is owed because of something they just did. The counts differ between pages because purpose is infinitely divisible, and a platform with nine screens tends to publish nine types. The axis doesn't move.
- Broadcast: you start it, at a moment you choose, aimed at a segment you choose. Newsletters, promotions, announcements, and seasonal sends are one family wearing different clothes.
- Triggered: the contact starts it, by doing something or by a date arriving. Welcome, abandoned cart, win-back, and renewal reminders are all this, and each is a flow rather than a send.
- Transactional: a single recipient's own action starts it, it goes to that person alone, and it's expected within seconds. Receipts, password resets, and confirmations.
The third family behaves differently from the other two, and the difference isn't tone. A transactional message is one the recipient's own action asked for, so it doesn't carry what marketing mail carries and isn't scored the way marketing mail is scored. The families have a limit, and it's the next question. They tell you what starts a send, never whether the send is wanted, and I've watched teams build all twenty-one before answering the second question once.
Broadcast types, the ones you decide to send.
A broadcast is one message sent to a chosen audience at a moment you picked. Nobody did anything to earn it and nothing fired to release it, so editorial judgment does most of the work. That's also why one platform ships nine types here and another twelve: the differences are about purpose and tone rather than mechanism, so the same handful of things can be cut a dozen ways without anybody being wrong.
- Newsletter: a recurring send on a published cadence, mixing news, useful writing, and light promotion, read as a relationship rather than an offer.
- Promotional: a single offer with a deadline and one call to action, sent to the segment most likely to act on it.
- Announcement: a launch, a feature, a price change, or a policy update, written to inform rather than to convert.
- Seasonal or event: a send tied to a date everybody shares, which is also why the inbox is crowded on that date.
- Survey or feedback request: a send whose conversion is a completed response, and the one broadcast where a short list beats a large one.
- Sponsorship or dedicated: a message you pay to put in front of somebody else's list, which is media buying rather than a type of your own.
Consent lands on all six the same way, and none of the six is a substitute for it. What you're allowed to send to somebody turns on what they agreed to when you got the address, not on which family the message belongs to. A broadcast is narrower than it sounds. It's aimed at a segment, so it's only ever as good as that segment, and email segmentation is a job of its own.
Triggered types, the ones the contact starts.
A triggered type is a flow: an entry condition, a wait, usually a branch, and an exit. This is the half of the list that gets called automation, and then gets described as though automation were the type. It isn't. The type is what the trigger is, and the automation is only how it runs. Read that way, the seven-item lifecycle guides and the twenty-one-item mega-lists are naming the same events in different vocabulary.
- Welcome: entered on subscription, and the one send where attention is highest and the sender hasn't said anything yet.
- Onboarding: a short sequence entered on signup, teaching one action at a time rather than the whole product at once.
- Abandoned cart or browse: entered on an intent signal that stopped short, and the type most often credited with revenue it would partly have earned anyway.
- Post-purchase: entered on an order, covering delivery expectations, getting started, and the first sensible cross-sell.
- Re-engagement or win-back: entered on a stretch of silence, and the only type whose success sometimes means letting a contact go.
- Milestone or renewal: entered on a date attached to the contact rather than to the calendar, like a signup anniversary or a subscription about to lapse.
Consent works differently here, and only just. Where a company took an address in the course of selling somebody a product, it may market its own similar products to that person, provided an easy and free way to object is offered when the address is collected and on every message after. That's why a post-purchase cross-sell sits on a different footing from a cold newsletter blast. The exception is narrow, so it doesn't stretch to a product line the customer has no relationship with. What stops a triggered type is missing events. The trigger is a data problem before it's a copy problem.
Transactional email, and the line that decides what it may carry.
The split runs on what the message is primarily for. A marketing message exists to promote something. A transactional or relationship message is one that confirms a transaction the recipient already agreed to enter into, carries warranty, recall, safety, or security information, gives notice of a change in subscription, membership, account status, or an account statement, relates to an employment relationship or a benefit plan, or delivers goods, services, or updates the recipient is already entitled to. Five categories, and nothing else qualifies.
The mailbox providers draw the same line. Google scopes one-click unsubscribe and a visible unsubscribe link in the message body to marketing and subscribed messages, alongside SPF, DKIM, and DMARC on the sending domain and a Postmaster Tools spam rate under 0.30%, in force since 1 February 2024 for anyone sending more than 5,000 messages a day to Gmail accounts. So the classification isn't a filing convention. It sets what the message has to carry and which rules judge it.
The limit of that split is the useful half, because the line moves when the message does. A receipt with a promotional block bolted under it has stopped being a receipt, and once a message reads as marketing it needs everything marketing mail needs: a one-click unsubscribe header, a visible link in the body, and suppression that holds. Yahoo asks bulk senders to action that unsubscribe within two days. We send both classes and hold suppression on the platform side, so what's left to you is which class you just wrote.
Twenty-one types, three things to build.
Whatever a list calls a type, building it is one of three jobs. A broadcast is a campaign object pointed at a segment. A triggered type is a flow with an entry condition, steps, and branches. A transactional type is a template plus a call from whatever system knows the event happened. Twenty-one names, three objects.
Three objects is small enough to operate by instruction instead of by navigation, and that's where the taxonomy stops being trivia. Nitrosend is MCP-first: every capability is an API endpoint and an MCP tool before it's a screen, so campaigns, flows, templates, contacts, lists, segments, and suppression are all addressable the same way. "Build the win-back flow, entry condition ninety days without an open, three steps" is a sentence rather than an afternoon.
I think dashboard-first products publish twenty-one-item lists because in a builder each of those items really is a different screen, with its own wizard and its own place in the menu. The list isn't a taxonomy then, it's a site map. Bolting an agent onto that is bolting a motor onto a bicycle.
Honestly, sorting the list doesn't tell you which types are worth running for your business, and an agent doesn't make an unwanted list wanted. It takes out the clicking, which was never the work.
Building the infrastructure for automated campaigns takes time. Phil and I assumed we could build a data tool for e-commerce stores in a single quarter. We thought the project would take three or four months. The reality I outlined on QA Selling Online was much slower. It was "like 17 months later, we have an MVP" ready for launch in 2016.
Which types to run first.
Four moves, in this order. The sequence runs from the mail people expect toward the mail you'd like them to want, because the early sends build the reputation the later ones spend.
- Get the transactional set right first. It's expected, it's opened, and it's the mail that establishes what your domain sends.
- Add the welcome sequence next. It's the one triggered type every list agrees on, and it arrives with the reader's attention already won.
- Set a broadcast cadence you can sustain. Whatever frequency you first thought of, the one you can hold is usually lower.
- Add behaviour-triggered types last, one at a time. Build only the ones whose firing event is data you genuinely have.
That cadence rule is buildable rather than just an intention: cap how soon the same subscriber gets mailed again, a day as a baseline and up to a week for anyone stricter, with transactional and welcome mail excepted so nothing urgent gets throttled by mistake.
A list of types is only useful once it turns into three things you can build, and building them shouldn't mean a different screen for each. We put campaigns, flows, and transactional sending behind one API and one set of MCP tools, so you can describe the send and have it built. The free tier is 8,000 emails to start, then 500 a month, with unlimited contacts and full MCP, API, and CLI access. No credit card.
Sources
- Google, Email sender guidelines: the bulk-sender threshold, authentication requirements, the 0.30% spam rate, and one-click unsubscribe scoped to marketing and subscribed messages.
- Yahoo, Sender best practices: the two-day window bulk senders are asked to honour an unsubscribe in, and the one-click requirement on marketing mail.
Common questions
Three, once you sort them on what starts the send. Broadcast is mail you decide to send to a segment you choose, and it covers newsletters, promotions, announcements, and seasonal sends. Triggered is mail the contact sets off by doing something or by a date arriving, which covers welcome, abandoned cart, post-purchase, and win-back. Transactional is mail a single recipient is owed after their own action, like a receipt or a password reset. The longer lists of nine, twelve, or twenty-one are those same three families cut by purpose.
Primary purpose. A marketing email exists to advertise or promote a product or service. A transactional or relationship email confirms a transaction the recipient agreed to, carries warranty or safety information, notifies an account or subscription change, relates to employment, or delivers something the recipient is already entitled to. The split isn't cosmetic: it decides whether the opt-out rules apply, and mailbox providers scope their unsubscribe requirements to marketing and subscribed mail on the same line.
Both, and the useful answer is that it's a broadcast with a cadence. What makes a newsletter a newsletter is that it recurs on a published rhythm and gets read as a relationship rather than as an offer, but mechanically it's the same object as a promotion: one message, one segment, one moment you picked. If you're deciding whether to start one, the commitment is the cadence rather than the format.
No. Drip is a schedule, not a type. Any triggered sequence can be run as a drip, which is why a welcome series, an onboarding sequence, and a win-back all show up on somebody's list as drip campaigns. When a list puts drip beside promotional as two siblings, it's mixing how a message is delivered with what the message is for. Ask what the entry condition is and the type appears.
Fewer than the lists imply. Get transactional mail right first, because it's expected and it's what teaches the mailbox providers what your domain sends. Add one welcome sequence. Set a broadcast cadence you can actually hold. Then add behaviour-triggered types one at a time, and only where the event that fires them is data you already collect. Three or four running well beat twelve half-built.
Not for every type, and the split follows the families. In the EU, direct marketing by email is on a prior-consent footing by default, with a narrow exception letting a company market its own similar products to somebody it already sold to, provided an easy and free way to object is offered every time. Transactional mail sits on a different footing because it isn't marketing at all. Once a promotional block goes into a receipt, that message has changed class and the marketing rules follow it.
The trigger-heavy ones, because a store generates the events that fire them. Abandoned cart and abandoned browse run off an intent signal that stopped short. Post-purchase covers delivery expectations, getting started with the item, and a first sensible cross-sell. Win-back runs off a stretch of silence. All four are flows with an entry condition rather than sends, so what limits them is the quality of the event data reaching your email platform, not the copy.
Ask what started it. If you started it, at a moment you chose, it's a broadcast and it needs a segment and a reason to arrive today. If the contact started it, by acting or by a date passing, it's a triggered type and it needs an entry condition, a wait, and an exit. If it's owed to one person because of something they just did, it's transactional and it needs to arrive in seconds. The answer names the object you have to build.