What has to be true before the first campaign
Most email problems are foundation problems that surface later as campaign problems. A newsletter that nobody opens is usually not a subject-line failure; it is a list that was built from the wrong sources, a domain that mailbox providers have no reason to trust, or a send that went to everyone because the sender could not tell who would care. Fixing the symptom at the campaign level is slow and often impossible, because the cause is upstream.
The foundations are three. Permission: every address on the list was given knowingly, for the kind of mail now being sent, with a record of when and how. Trust: the sending domain is authenticatedRecords and signatures, SPF, DKIM and DMARC, that let mailbox providers check that a message comes from the domain it claims., the sending pattern is steady, complaints are rare and unsubscribesShare of delivered emails that led the recipient to opt out. are honoured at once. Relevance: enough is known about each subscriber to send fewer, better-targeted messages rather than more of the same. Each has a guide below. Together they decide the ceiling on everything in the campaigns section and the automation section; no flow or newsletter can perform above the quality of the list it is sent to and the inbox placement it achieves. The email marketing hub sets these foundations within the wider system.
List, deliverability, segmentation: the core guides
- List building and consent — where sign-up forms belong and what to offer, how consent and lawful basis work in principle, single against double opt-inA sign-up process in which the subscriber confirms through a link sent to the address given., preference centres, the risk in imported and purchased lists, and unsubscribe done properly. The guide is general and not legal advice; rules differ by jurisdiction, and it points to regulators' own guidance.
- Deliverability — the difference between delivered and in the inbox, how SPF, DKIM and DMARC authenticate a domain, the sender requirements mailbox providers document, reputation and engagement, warming a new domain, monitoring through postmaster tools, and a diagnosis table for placement problems.
- Segmentation — the data worth collecting, lifecycle and behaviour segments, engagement tiers and suppression, preference segments, and how to keep the number of segments manageable.
Read the core guides in that order the first time. Consent decides who can be mailed, deliverabilityWhether sent email reaches the inbox rather than spam or rejection, decided by sender reputation. decides whether the mail arrives, and segmentationDividing a market or customer list into groups that need different offers or messages. decides what each person receives. A team that already has a list should still start with the first guide, because the most common inherited problem is a list whose consent history nobody can reconstruct.
Further guides
Further guides cover the decisions and situations around those foundations: the platform the mail is sent from, a list that has gone quiet, what a subscriber is worth, a programme that spans several markets, addresses collected in person, and the outside help that runs it:
- Choosing an email platform — choosing from what the programme needs: sending on your own domain, consent and suppression, flows, testing, data and leaving later.
- Migrating to a new email platform — a tutorial for moving without losing subscribers or reputation: inventory, consent and suppression, authentication, flows, forms and staged sends.
- Restarting email to a dormant list — a tutorial for a list nobody has mailed in a long time: rebuilding the consent record, cleaning the list, checking authentication, re-permission and sending in stages.
- What an email subscriber is worth — putting a value on a subscriber: margin rather than revenue, cohorts by sign-up source, the incremental part from a holdout, and what the figure is for.
- Running email across countries and languages — one programme across markets: consent by market, language as subscriber data, local timing, sender identity and reporting.
- Collecting email sign-ups in person — a tutorial for addresses given at a till, a counter, a reception desk or by phone: what staff say, a choice kept apart from the receipt, confirmation and records.
- Hiring and evaluating an email marketing agency — a guide to choosing an agency or freelancer to run email: what stays in the business's name, the questions to ask about consent and sending, warning signs in a proposal, reports that tie back to orders and a handover list.
Sender requirements in brief
Mailbox providers publish what they expect from senders, and the expectations have tightened. Google's email sender guidelines document a set of requirements for all senders and an additional, stricter set for bulk senders, defined by a documented daily volume of messages to its users. For all senders, the guidelines document authentication with SPF or DKIM, valid forward and reverse DNS records for sending servers, use of TLS, a spam rate kept below the documented threshold as reported in Postmaster Tools, messages formatted to the internet message format standard, no impersonation of Gmail in the From header, and ARC headers where mail is forwarded. For bulk senders the guidelines add authentication with both SPF and DKIM, a DMARC policy for the sending domain, alignment of the From header domain with SPF or DKIM, one-click unsubscribe for marketing and subscribed messages with a clearly visible unsubscribe link in the body, and processing of unsubscribe requests within the documented window.
Two points matter for anyone reading that list. First, the requirements are a floor, not a target: meeting them stops mail being rejected or filtered for a documented reason, and says nothing about whether the content earns the inbox. Second, other large providers publish their own expectations, which overlap but are not identical; check each provider's documentation rather than assuming one set covers all. The deliverability guide covers each requirement in the depth needed to implement it, and the list building guide covers the unsubscribe mechanism from the subscriber's side.
The hygiene routine
Foundations decay unless someone tends them. The routine below is the minimum most teams settle on; the cadence can tighten during heavy sending periods.
| Cadence | Task | What to look for | Guide |
|---|---|---|---|
| After every send | Review bounces, complaints and unsubscribes | A jump in hard bounces or complaints on one send points to a list source or content problem | Deliverability |
| Weekly | Check authentication and postmaster dashboards | DMARC reports showing unexpected sources; spam rate drifting towards the documented threshold | Deliverability |
| Weekly | Confirm new sign-ups carry a consent record | Imports or integrations adding addresses without a source, timestamp or form reference | List building |
| Monthly | Refresh engagement tiers and suppression | Subscribers who have not opened or clicked within the chosen window moved to a re-permission or suppressed segment | Segmentation |
| Monthly | Remove hard bounces and role addresses | Addresses that bounced permanently still sitting on the active list | Deliverability |
| Quarterly | Audit sign-up points and the preference centre | Forms with vague promises, broken double opt-in, preferences nobody acts on | List building |
| Quarterly | Review segment count against use | Segments nobody has mailed in the quarter; overlapping definitions | Segmentation |
The routine is short on purpose. A list owner who does these things consistently will catch most problems while they are still cheap. The measures that make up a list-health KPIA metric tied directly to an objective., such as complaint rate, bounce rate and the share of the list that is active, belong in the monthly email report alongside click-through (CTRShare of impressions that result in a click.) and conversion rate (CVRShare of visits or clicks that convert.), so that foundation drift is visible next to campaign results rather than discovered when placement collapses. A hard bounceAn email rejected permanently by the receiving server, usually because the address does not exist or the domain cannot receive mail., a permanent delivery failure, is the one figure in that report that always means an address should leave the list.
An inherited list, audited before the first send
A new marketing lead at a meal-kit company inherits a list of 48,000 addresses and a brief to send a relaunch
email the following week. Instead she spends four days on the foundations. The export shows that 11,000
addresses came from a trade-show badge scanner in 2022 with no opt-in field, 6,500 have hard-bounced at least
once, and 9,000 have not opened anything in 18 months. The sending domain has SPF but no DKIM and no DMARC.
She removes the bounces, holds the trade-show addresses in a quarantine segment pending a re-permission
campaign, suppresses the long-inactive group, and asks IT to publish DKIM and a p=none DMARC record. The
relaunch goes to 21,500 people a week later than planned. Complaints total 3, and the welcome flow built the
same week greets the 180 new sign-ups the campaign produces.
Common fundamentals problems
| Symptom | Usual cause | Guide |
|---|---|---|
| New campaigns land in spam from the start | Domain not authenticated; sending from a shared or new domain without warming | Deliverability; diagnosis: emails going to spam |
| Complaint rate rises after a list import | Addresses added without consent for this sender or this type of mail | List building |
| Hard bounces jump after an import or a platform move | Stale, bought or mistyped addresses, or bounces never suppressed | List building; diagnosis: email bounce rate too high |
| Opens and clicks fall steadily over months | Whole-list sends with no suppression; subscribers who never engage dragging reputation down | Segmentation; for a sudden fall: email open rate dropped |
| Unsubscribes spike on a particular send | Expectations set at sign-up not matching what was sent; cadence higher than promised | List building |
| DMARC reports show unknown senders | Third-party systems sending as the domain without being included in SPF or signing with DKIM | Deliverability; diagnosis: DMARC failing |
| Every segment gets the same message | Data collected but not used; segments defined without a message plan | Segmentation |
| Nobody can say where an address came from | No source, form or timestamp recorded at sign-up | List building |
| People write to say they never signed up for the email | An address that reached the list by a route with no clear choice or no record of one | List building; diagnosis: subscribers saying they never signed up |
| The list total stays flat although people keep signing up | A form lost in a redesign, confirmations not arriving, or losses matching new arrivals | List building; diagnosis: email list not growing |
| A list nobody has mailed in a long time is about to be used again | Consent records lost, addresses decayed and authentication unchecked since the last send | Restarting email to a dormant list |
| Old opt-outs are mailed again after a platform move | Suppression files not loaded before contacts, or not carried across at all | Migrating to a new email platform |
| Nobody can say what a new subscriber is worth, so sign-up spend has no ceiling | Value read from revenue attributed to email rather than margin and a holdout | What an email subscriber is worth |
| Subscribers in one market receive mail in the wrong language or at the wrong time of day | Language and market not captured at sign-up; one send time for every market | Running email across countries and languages |
| Addresses taken at the till or on the phone bounce, or customers say they never asked for offers | Addresses written down by staff, no separate marketing choice and no confirmation | Collecting email sign-ups in person |
| An agency or freelancer is about to take over email, and nobody has said who keeps the platform, the domain and the list | The account, the sending domain's records, the consent records and the suppression list left in the provider's hands | Hiring and evaluating an email marketing agency |
When a problem appears in the campaigns or automation sections that none of their guides explain, the cause is usually here. Check the foundations before changing the creative. For a symptom-first diagnosis, the email troubleshooting section works through each cause with a check and a fix.
