Email Marketing Fundamentals

Permission is the foundation

Every email program starts with one question: did this person actually agree to hear from you? "Permission" means someone knowingly opted in — they filled out a form, checked a box, or handed over their email address specifically to receive what you're about to send. It does not mean you found their email address on a business card, scraped it from a directory, or added them because they bought something once and you assumed that counted as consent for ongoing marketing.

A stronger version of this is double opt-in: after someone submits their email, they receive a confirmation message and have to click to confirm before they're added to your list. It adds one small piece of friction, but it guarantees the address is real, the person genuinely wants to be there, and you have a clear record of consent if it's ever questioned. For a small business just getting started with automation, double opt-in is worth the minor drop in sign-up numbers — the people who do confirm are the ones who will actually engage.

Respecting an unsubscribe request immediately, without follow-up emails asking "are you sure," is part of the same principle. Permission can be withdrawn, and a business that makes it hard to leave a list damages its reputation with both the subscriber and, as the next section covers, with the mailbox providers watching how it behaves.

List hygiene: why a smaller list often outperforms a bigger one

List hygiene means regularly removing the addresses that are no longer worth keeping: hard bounces (the address doesn't exist), repeated soft bounces (a mailbox that's been full or broken for months), and contacts who haven't opened or clicked anything in a long stretch of time. It feels counterintuitive to delete people from a list you worked to build, but a list padded with dead and disengaged addresses actively hurts you.

Mailbox providers such as Gmail and Outlook watch how recipients behave with a sender's email — do they open it, do they mark it as spam, do they delete it unread every time. A list full of people who never engage drags that behaviour average down, and providers respond by routing more of that sender's mail to spam, including the mail going to people who genuinely do want it. In other words, dead weight on your list doesn't just fail to help — it actively damages deliverability for your engaged subscribers too.

A simple standing practice: remove hard bounces immediately, and run a periodic re-engagement pass (see Chapter 3) for anyone who hasn't opened in several months — either win their attention back or remove them.

Deliverability basics: SPF, DKIM and DMARC in plain language

Before automating any volume of email, it's worth understanding — at a plain-language level — the three technical records that tell mailbox providers your email is legitimate. You don't need to configure these yourself; your web developer, IT person, or your email tool's support team can set them up. But knowing what they do helps you ask the right questions.

• SPF (Sender Policy Framework) is a small DNS record for your domain that lists which mail servers are allowed to send email on your behalf. When a receiving server gets a message claiming to be from your domain, it checks this list — if the sending server isn't on it, that's a red flag.
• DKIM (DomainKeys Identified Mail) attaches a digital signature to each email your domain sends. The receiving server can verify that signature to confirm the message genuinely came from you and wasn't altered or spoofed along the way.
• DMARC (Domain-based Message Authentication, Reporting and Conformance) sits on top of both — it tells receiving servers what to do if a message fails SPF or DKIM checks (quarantine it, reject it, or let it through), and it gives you visibility into who is sending email using your domain, which is also useful for catching impersonation attempts.

Together, these three records are what separate "trusted sender" from "unverified sender" in the eyes of Gmail, Outlook and every other major mailbox provider. If you're about to start sending automated sequences at any real volume, confirming these are correctly configured for your sending domain is one of the highest-leverage half-hours you can spend.

Common spam triggers to avoid

Beyond the technical setup, the content and behaviour of your emails themselves affects deliverability. A few patterns worth avoiding as a matter of habit:

• Subject lines in ALL CAPS, with excessive exclamation marks, or that misrepresent what's inside the email.
• Emails that are a single large image with almost no real text — spam filters can't "read" an image, and this pattern is common in low-quality email.
• A very high ratio of links to text, especially links to unfamiliar or shortened domains.
• Sending a large volume suddenly from a brand-new domain with no sending history — mailbox providers trust reputation built gradually, not a burst of volume on day one. Warming up a new domain with smaller, steady sends is safer than starting with a full-list blast.
• Buying, scraping or renting a list — beyond the permission problem covered above, these addresses are disproportionately likely to be spam traps or dead mailboxes that tank your sender reputation immediately.

Why list quality beats list size

It's tempting to treat list size as the headline metric — more subscribers feels like more opportunity. In practice, a smaller list of people who genuinely opted in and regularly open your email will outperform a much larger list of cold or purchased contacts on every measure that matters: open rates, click rates, replies, and ultimately sales. It also protects the one asset that's expensive to rebuild once damaged — your sending domain's reputation with mailbox providers, which affects every email you send from that domain, automated or not.

With permission, hygiene and deliverability handled, you have a foundation worth automating on top of. The next chapter covers how to structure the sequences — welcome, nurture, cart-recovery and re-engagement — that actually run on that foundation.