SMF·CAMPAIGN-MONITOR
Can a prompt replace Campaign Monitor?
Newsletters & publishing — email newsletters and creator publishing
Exhibit tracking slip
Verdict
Sending through a transactional provider is the same weekend it always is. Campaign Monitor's distinctive piece is the template system: an agency builds one email layout, marks which regions the client may edit, and the client can then change copy and images without touching the table structure that keeps it rendering in Outlook. Building that lock-region model, and the bulletproof HTML underneath it, is real and specific work — and a sending reputation still is not something you can build.
Exhibit A — The prompt
Received on31.07.2026Build a campaign sender whose distinguishing feature is templates with locked and editable regions.
Template model, which is the point. A template is HTML authored by a developer, using table-based layout and inline styles because that is what email clients require. Regions the client may change are marked with a data attribute declaring an id, a type (short text, rich text, image, link, or a repeatable block) and constraints (maximum length, allowed image dimensions). Everything not marked is immutable and is not exposed in the editor at all.
Campaign editor: renders the template with only its editable regions as form fields, in reading order, with a live preview beside them. A repeatable block can be duplicated or removed but not restructured. Validate against each region's constraints before a campaign can be sent — an image that will render at 900 pixels wide inside a 600-pixel table is a rejected input, not a warning.
Rendering: produce both the HTML and a plain-text alternative generated from the same content, since a missing text part hurts deliverability. Inline all CSS at send time. Provide a preview of the plain-text version, because nobody checks it and it is what a fair proportion of spam filters read.
Subscribers: import CSV with explicit consent-source and timestamp columns, double opt-in with a confirmation email, one-click unsubscribe including the List-Unsubscribe-Post header, and a suppression list that is checked at send time and can never be bypassed.
Sending: queue through Amazon SES with a per-second rate limit, retries with backoff, idempotency per recipient per campaign, and resumable batches so an interrupted send does not double-deliver. Process delivery, bounce and complaint notifications, remove hard bounces immediately, and suspend a campaign automatically if the complaint rate crosses a threshold mid-send.
Reporting: per campaign, sends, deliveries, bounces by type, complaints, opens and clicks by link. Never store message bodies against a recipient, and make open tracking a per-campaign choice that is off by default.
Setup: the README must walk through the DNS records — SPF, DKIM, DMARC — and state plainly that a new domain needs weeks of gradual volume increase before large sends land reliably, and that this warming period is the real cost of leaving a platform.
Out of scope: multi-step automation journeys, ecommerce integrations, a drag-and-drop template designer, and client accounts with their own logins.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the sending reputation, which is earned over months and not transferable
- B.2 inbox-placement testing across the major mail clients
- B.3 the journey builder for multi-step automated sequences
- B.4 the agency layer: client accounts, permissions, white-labelled reports
Prior art
Exhibit C — Why people still pay: deliverability, growth network, and integrations
Because deliverability is a reputation, not a feature. A new sending domain starts at zero trust, and the months of warming and monitoring that fix that are exactly what a platform has already done.
Questions
Can I move my Campaign Monitor lists and templates?
Subscribers export as CSV with consent data, which is the important part and imports cleanly. Templates export as HTML, but the editable-region markers are Campaign Monitor's own syntax, so each template needs its regions re-annotated in this build's format — an hour per template.
Why mark regions instead of using a drag-and-drop builder?
Because email HTML breaks in ways web HTML does not, and every drag-and-drop builder either produces fragile output or constrains itself so heavily that it becomes a region editor with extra steps. Locking the structure is what lets a non-technical person edit an email that still renders in Outlook.
What does it cost to run?
SES is roughly ten cents per thousand emails, plus a small VPS with PostgreSQL. A list of 10,000 sent weekly costs a few dollars a month against a plan priced per subscriber, which is the strongest financial argument in the whole newsletter category.
What is the one thing that does not survive the rebuild?
Landing in the inbox. Your first send from a fresh domain will go to spam for a meaningful share of recipients, and no amount of correct SPF and DKIM changes that on day one. Reputation is built by sending well over months, and it is the one thing on this list that money genuinely buys.
Related tools
Receipt