Why email still carries the owned channel
Every other digital channel is rented. Organic reach on social platforms depends on an algorithm the brand does not control; paid reach stops the moment the budget does; search visibility can move with a core update. Email is different in kind. The addresses on a list were given to the business directly, the sending infrastructure is chosen by the business, and the cost of one more message is close to nothing once the system exists. That is why email tends to carry retention, repeat purchase and the quieter stages of a relationship that paid channels cannot afford to serve. The owned, earned and paid media guide sets out the wider distinction.
Ownership is not the same as freedom. The mailbox provider, not the sender, decides whether a message lands in the inbox, the promotions tab or the spam folder, and it decides on evidence: whether the sending domain is authenticated, how many recipients complain, how many engage, and whether the sender honours unsubscribe requests. A list that was built carelessly or mailed indiscriminately loses that trust, and losing it is far quicker than earning it back. The practical consequence is that email rewards patience. The teams that get the most from it treat the list as a relationship with a customer lifetime value (LTVTotal value a customer brings over time.) attached, not as a database to be extracted from.
The email system
Email marketing is five connected parts. A weakness in any one of them shows up as a symptom somewhere else, which is why the sections of this hub are organised the way they are.
| Part | The question it answers | What good looks like | Where to read |
|---|---|---|---|
| List | Who has agreed to hear from us, and about what? | Consent recorded at sign-up, expectations set, preferences captured, unsubscribes honoured promptly | List building and consent |
| Deliverability | Will the message reach the inbox at all? | Authenticated domain, documented sender requirements met, low complaints, stable volume | Deliverability |
| Content | Is this message worth opening, and does it ask for one clear thing? | A repeatable newsletter structure, promotional and transactional mail kept distinct, accessible design | Campaigns |
| Automation | Which messages should send themselves, triggered by what a person does? | Welcome and abandoned-cart flows that run without a calendar and are reviewed on a schedule | Automation |
| Measurement | What happened, and what should change? | Metrics tied to outcomes, tests that answer one question each, reports that end in a decision | Email metrics and testing |
The order matters. Content sent to a list that was never asked for permission, through a domain that is not authenticated, will underperform however well it is written, and no amount of testing will show why. When a symptom appears first, the email troubleshooting section traces it back to the part that caused it.
Fundamentals
The fundamentals section covers what has to be true before the first campaign goes out. Its core guides are introduced below, followed by further guides on platforms, quiet lists, subscriber value, email across markets, sign-ups collected in person and hiring an agency or freelancer.
List building and consent. Where sign-up forms go, what to offer in exchange for an address, how consent is recorded, when double opt-inA sign-up process in which the subscriber confirms through a link sent to the address given. is worth the friction, and why imported or purchased lists carry risk. Rules on consent vary by jurisdiction, so the list building guide explains the principles and points to regulators' own guidance rather than giving legal advice.
Deliverability. How mailbox providers decide what to do with a message: the authentication standardsRecords and signatures, SPF, DKIM and DMARC, that let mailbox providers check that a message comes from the domain it claims. SPF, DKIM and DMARC, the sender requirements Google documents for all senders and the stricter set for bulk senders, reputation and engagement, and how to warm a new domain. Sender requirements are a theme that runs through the whole hub, because they changed what "allowed" means. Google's guidelines document that bulk senders must authenticate with both SPF and DKIM, publish a DMARC policy, align the visible From domain with that authentication, and support one-click unsubscribe for marketing mail. The deliverability guide explains each requirement as the source documents it, without inventing figures the source does not give.
Segmentation. The data worth collecting, lifecycle and behaviour segments, engagement tiers, and the suppression lists that protect reputation by not mailing people who have stopped responding. The segmentation guide is where a list stops being one audience.
Further guides. Choosing an email platform starts from what the programme needs rather than from feature lists, and the tutorial on migrating to a new email platform moves a programme without losing subscribers or reputation. Restarting email to a dormant list covers a list nobody has mailed in a long time, what an email subscriber is worth puts a value on a subscriber from margin rather than revenue, and running email across countries and languages covers consent, language and timing by market, and collecting email sign-ups in person covers addresses given at a till, a counter or by phone. The guide to hiring and evaluating an email marketing agency sets out what stays in the business's name when an outside provider runs email, and what to ask before choosing one.
Campaigns
A campaign is a message a person decides to send, to a chosen audience, at a chosen time. The campaigns section covers the campaigns most teams run and the distinction that governs them. The newsletter design and copy guide sets out a structure that can be repeated every issue, subject lines and preheaders, scannable copy and the discipline of one call to action. The promotional vs transactional comparison explains why order confirmations and password resets are treated differently from offers, both by the law in many places and by mailbox providers, and why mixing the two in one message is a mistake. Further guides cover running a sale or launch by email, personalising email content, choosing a newsletter format, plain-text and HTML email, fixing a mistake in a sent email and newsletter sponsorships.
Campaign performance is read through click-through (CTRShare of impressions that result in a click.) and the conversion rate (CVRShare of visits or clicks that convert.) of the traffic a message sends, not through opens alone; the conversion rate calculator turns clicks and outcomes into the rate a campaign report should show. Opens have become a weak signal in many mail clients, which is one reason the measurement guide in the automation section puts clicks and conversions first.
Automation
Automated email is triggered by what a person does rather than by a calendar. The automation section holds the core tutorials and a measurement guide, with further tutorials beside them. The welcome series tutorial builds the sequence that greets a new subscriber, sets expectations and makes the first ask; it is usually the highest-value flow a business runs, because every subscriber passes through it at the moment of most attention. The abandoned cart tutorial covers the retail flow that follows a product left behind, including timing, content and when to stop. The email metrics and testing guide explains which metrics mean what, how to run an A/B TestControlled comparison of two variants. that can be trusted, and how to report on email in a way that leads to a decision rather than a chart. Further tutorials build a post-purchase flow, onboarding emails for a software product and back-in-stock and price-drop alerts.
Automation is also where the foundations get tested. A welcome flow sends to every new address, so a sign-up form that admits bots or typos shows up as bounces within the first message; an abandoned cart flow depends on a reliable link between an email address and a session, which is a data question before it is a creative one.
Email and the rest of the stack
Email rarely stands alone. Its data lives in a customer relationship system or an automation platform, and its results are read in analytics alongside every other channel. The marketing automation hub covers the systems side: lead stages, scoring, nurture workflows and the governance that stops automations from multiplying unchecked. The lifecycle marketing guide places email within the full customer journey, from first contact through purchase to advocacy, and explains which stages email serves best.
Measurement connects through tagged links and conversion events. Every link in a campaign should carry campaign parameters so that analytics can attribute sessions and outcomes to the send; the key performance indicators (KPIA metric tied directly to an objective.) for email should be the same outcome measures the business uses elsewhere, with email-specific metrics used as diagnostics beneath them. The other channels expertise page describes how the author approaches email in practice; this hub teaches the method.
A first ninety days
A team starting from nothing can have a working email programme within a quarter if it does the foundations before the campaigns.
The first month: foundations. Choose the sending domain or subdomain, set up SPF, DKIM and DMARC, and verify them before any marketing mail is sent. Put sign-up forms where visitors already show interest, with a clear statement of what they will receive and how often. Record consent. Write the welcome series and switch it on, so that every new subscriber is greeted even before the first campaign exists.
The second month: the first campaigns. Send a newsletter on a cadence the team can keep, to the whole list, with one call to action per issue. Watch complaints, bounces and unsubscribes after every send. Build the abandoned cart or lead follow-up flow if the business model calls for one.
The third month: relevance and testing. Split the list into a few segments that matter, suppress people who have never engaged, and run the first subject line test. Agree the monthly report and the decisions it should drive.
A specialist coffee roaster's first quarter
A roaster with an online shop and no list begins in January. Week 1 goes on authentication: a subdomain for
marketing mail, SPF and DKIM configured, a DMARC record at p=none with aggregate reports flowing to the
team's inbox. Weeks 2 to 4 add a sign-up offer (a brewing guide) on the product pages and at checkout, plus a
three-email welcome series. By the end of month 1 the list holds 640 addresses, all with a recorded consent
timestamp. In month 2 the roaster sends a fortnightly newsletter; the second issue goes to 1,150 subscribers,
earns 312 clicks and 41 orders, a conversion rate on clicks of just over 13%. Complaints stay at 2 per send.
In month 3 the team builds two segments, repeat buyers and never-purchased, and suppresses the 90 addresses
that have not opened or clicked in 60 days. The first subject line test runs on the never-purchased segment,
with 500 people per variant.
The quarter ends with a list that mailbox providers trust, a flow that works without attention, and a reporting habit. Growth comes after that, and it comes faster on a foundation that does not need to be rebuilt.
