A Newsletter Is Not a Campaign

· 5 min read

Because both arrive as email from the same software, newsletters and campaigns get treated as one activity with two names. The consequences are subtle and compounding: newsletters get judged by campaign metrics, campaigns get sent at newsletter frequency, and the list gets worn out by both.

The distinction is not academic. They are doing different jobs.

The difference in one sentence

A campaign asks for something. A newsletter earns the right to ask later.

A campaign has a call to action, a window, and an outcome you can count — bookings, purchases, registrations. Its success is measured against that outcome, and if it does not produce one, it failed regardless of how well written it was.

A newsletter has no such outcome, and building one into it changes its nature. Its job is to remain worth opening. Its success is measured over months, in whether people still open it, and in whether your name is familiar when a need eventually arises.

What goes wrong when they are conflated

Newsletters measured as campaigns get killed. Someone looks at a newsletter's direct attributable revenue, finds it near zero, and concludes it is not working. But direct revenue was never its function. Measuring it that way guarantees it is discontinued at exactly the point it was starting to compound.

Campaigns sent at newsletter frequency exhaust the list. If every email asks for something, the pattern people learn is that hearing from you costs them. Open rates fall, and the fall gets misread as message-quality problem, which prompts more sending.

Both together produce the worst outcome. A newsletter with a sales pitch stapled to the end is neither. It is not useful enough to be worth opening and not direct enough to convert, and it teaches readers that your useful content is bait.

The list is one shared resource

Here is the part that connects them, and the reason the distinction has practical teeth: they draw on the same finite thing, which is people's willingness to hear from you.

Every send spends a little of that willingness. A good newsletter replenishes it. A campaign spends it. Running campaigns without newsletters is drawing down an account with no deposits, and it works until abruptly it does not.

This is also why the technical hygiene matters more than it seems. Making it easy to leave protects the list you keep: there is a whole specification for signalling "a one-click function for the List-Unsubscribe email header field" [1], and it exists because the alternative — a hunt for a link, a landing page, a confirmation step — pushes people to the spam button instead. An unsubscribe costs you one address. A spam complaint costs you deliverability to everyone.

And since both newsletter and campaign ride the same domain reputation, the damage is not contained. DMARC's reporting half exists precisely so a sending organisation can see what receivers are doing with its mail and "improve mail handling" [2] — which is only useful if someone reads the reports. Most businesses publish the record and never look at the output.

Different rhythms

A newsletter needs a rhythm people can predict, and the specific interval matters less than its reliability. Monthly, sent on time, beats weekly-when-we-remember. Predictability is what makes it feel like a publication rather than an interruption.

A campaign needs a reason. Sending one because it has been a while is how campaigns become noise. If you cannot name what is happening and why now, there is no campaign — there is a desire to be seen, which is not the same thing.

The two also differ in what people agreed to, and this is where a lot of otherwise careful businesses drift.

Someone who subscribed to a newsletter agreed to a newsletter. Someone who bought something agreed to a transaction. Neither automatically agreed to promotional campaigns, and treating a purchase as consent to marketing is the most common quiet overreach in small-business email.

The cleanest approach is to keep the two permissions separate, ask for each plainly, and let people hold one without the other. It shrinks the campaign list, which feels like a loss and is not: a smaller list of people who agreed outperforms a larger one that did not, on every measure including the ones you care about.

This is the collection discipline again, applied to permissions rather than fields — not gathering things speculatively "in case it is useful later" [3]. An address collected without a stated purpose is an address you cannot confidently use for any purpose.

What a newsletter is allowed to be about

The most common reason newsletters stop is not that they failed. It is that nobody could think what to put in the next one.

This is usually a scoping problem. A business decides its newsletter is about its own news, discovers that it does not generate news at a monthly rhythm, and starts padding — a staff birthday, a minor feature, an office photograph. Readers notice the padding faster than anyone writing it does, and the open rate falls for reasons that look mysterious from the inside.

The way out is to define the newsletter by what it is useful for rather than by whose news it carries. What are your customers repeatedly confused about? What did you learn this month that a customer would find worth knowing? What question came up three times?

A business generates that material continuously, without effort, as a by-product of doing the work. It requires only that someone writes down the questions when they arrive, which is a five-second habit rather than an editorial process.

It also solves the credibility problem. A newsletter that answers the questions customers actually ask reads as competence. One that reports internal milestones reads as an announcement nobody requested.

How to run both

Keep one list of people and two permissions on it. Send the newsletter on a fixed rhythm with no ask, and judge it on whether people keep opening it. Send campaigns when there is a real reason, to the people who agreed to receive them, and judge each on its own outcome.

Then, once a quarter, look at the two together. If newsletter opens are falling while campaign volume is rising, you have your explanation, and it will not be the copy.

Sources

  1. [1] RFC 8058 — Signaling One-Click Functionality for List Email Headers — IETF
  2. [2] RFC 7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC) — IETF
  3. [3] 360REV Use of Data Policy — what we collect — 360REV, Inc.