Nine things to check before you send a campaign

Most campaign mistakes are not dramatic. Nobody sends the wrong file to the whole list. What happens is smaller and more embarrassing: a subject line that still starts with [TEST], a button that points at last month's landing page, a greeting that reads "Hi ," because a contact has no first name on file.

Sent email stays sent. So the cheapest moment to catch a problem is just before the send, and it only works if you check the same things in the same order every time. Below are the nine we use. Each has a reason, a common way it goes wrong, and the place in the campaign builder where you can do it.

A quick map of the builder: you build the email and pick recipients in the first step, optionally set up a subject line test in A/B Test, and finish in Review + Send. Checks 1 to 6 live mostly in the first step, 7 and 8 are about recipients and timing, and 9 happens at the end.

The sender name is the first thing a person reads, and they decide in a moment whether it is someone they know. Use the name they recognise from your last email: your brand, or a person they have dealt with. Changing it from one campaign to the next is a reliable way to look unfamiliar.

The usual failure is the address, not the name. A from address on a domain that is not set up for sending will fail authentication or be refused outright, and a mailbox nobody reads means real replies disappear.

The inbox shows them side by side, so write them as one sentence split in two. The subject says what the email is. The preheader adds the detail the subject had no room for.

If you leave the preheader empty, the inbox fills the space with the first text it finds in the body, which is often "View this email in your browser" or a row of navigation links. That is a wasted line in the one place everyone looks.

Mailnaptic's own guidance in the builder is to keep subjects under 50 characters and preheaders under 100, and to avoid ALL CAPS and spam-trigger words. Treat the numbers as a guide, not a rule: a phone cuts text off earlier than a desktop client, so put the important words first.

A good share of your list will read the email on a phone, and many mail clients hold images back until the reader allows them. If your whole message is a picture of text, some people will see a grey box.

Look at the mobile layout, then ask what the email says if no image loads. The headline, the offer and the button should all exist as real text, and images should carry alt text that still makes sense.

Click every link in the test email you just sent, not in the editor. Broken or stale links are the most common error we see, and they are easy to miss because the button looks fine. Check that the destination is the live page, that it works on a phone, and that nothing lands on a login screen.

UTM tags are the other half. They are what lets your analytics tell a campaign visit from any other visit, and they only work if you apply them consistently. Mailnaptic can append utm_source, utm_medium, utm_campaign and utm_content to every link automatically.

Every merge tag is a promise that the data exists. When it does not, the reader sees an empty gap: "Hi ," or "Your order of is ready". It looks careless, and it is the failure that testing on your own contact record never reveals, because your record is complete.

The fix is a fallback. Mailnaptic supports conditional blocks with an else branch, for example {{#if tag:vip}} offer text {{else}} default text {{/if}}, and the else branch works in subject lines too. Write the default version so it reads naturally on its own.

Both are legal requirements for marketing email in many places (CAN-SPAM in the US, for one), and both are what a mailbox provider expects to see. A missing unsubscribe link also pushes people toward the spam button, which hurts you more than an unsubscribe does.

Mailnaptic adds the unsubscribe link for you, and it will not let you send until the sending domain has a physical mailing address. The footer in the builder shows the address and the link, so look at them once rather than assume.

Most people check who the email is for. Fewer check who it is not for. The embarrassing sends are almost always an exclusion that nobody thought about: the offer that lands in the inbox of someone who bought yesterday at full price, the upsell that arrives while a customer has an open complaint.

Segments in Mailnaptic are dynamic, so only contacts who match at send time receive the email. That is useful, but it means the audience can be different from the one you looked at last week. Open the segment and read its rules again.

One more thing that can shrink the audience: if frequency capping is on for your organization, Mailnaptic may skip contacts who have already received the maximum number of emails for the day or week. The builder tells you when it applies.

Send time is the check people skip, and it has fewer rules than it seems. There is no universal best hour. What matters is that you chose one on purpose, and that it makes sense for where your readers are. A Monday morning in Copenhagen is Sunday night in Los Angeles.

Mailnaptic offers three ways to deal with that. A fixed time in your organization's timezone, which is set at the organization level. Send in contact's local timezone, so everyone gets it at, say, 9:00 where they live. Or, on Pro and above, Send Time Optimization, which sends each contact's email at the hour they have historically opened most. The last two need at least 26 hours of lead time and cannot be combined, because turning on local timezone sends disables Send Time Optimization.

The last check is a pass over the whole thing, in the state it will actually go out. Review + Send is built for it. It has a Pre-send checklist that blocks the send until the required items pass, a spam score you can run on demand, an AI compliance review that looks at CAN-SPAM and GDPR signals, and the rendered preview.

On Pro and above there is also a rehearsal with subscriber digital twins. It simulates a sample of representative subscribers reading your draft and gives back predicted open, click and unsubscribe rates, plus the lines where readers hit friction. Read it as a second opinion from an audience that never gets tired, not as a forecast. Mailnaptic labels it beta, it anchors the numbers to your own sending history where it has some, and the result is cached until you change the subject or body.

Then do the human version. Open the test email, read it once from the top as if you had never seen it, and click the button. If something feels off, it is.

Keeping it short

Nine checks sounds like a lot, but most take under a minute once the habit is there. The ones that take longer, like re-reading an exclusion rule, are the ones that prevent the worst sends. If you only have time for three, make them 4, 5 and 7.

If you want a place to run all of this in order, the Mailnaptic campaign builder keeps them in one flow, and the email campaigns page shows how the pieces fit together.