Email Marketing in 2026: How to Build a List and Actually Get Opens

Email delivers an average $36 return for every $1 spent — the highest ROI of any digital marketing channel by a substantial margin. The reason it underperforms for most businesses has nothing to do with the channel itself. It has to do with the technical infrastructure underneath it: DNS authentication records that were never configured, sender domains that were warmed up too fast, databases full of unengaged contacts that degrade deliverability for every subsequent send, and list segmentation approaches that treat a customer who bought six months ago identically to one who bought last week.

The case that illustrates the problem precisely: a mid-sized US e-commerce client came to Nexentity with a 4 percent email open rate and $12,000/month in abandoned cart revenue that was disappearing because recovery emails were landing in spam. Their previous agency had sent to their full 45,000-subscriber list from day one of migration to a new ESP — without completing an IP warmup sequence — and their domain reputation had been flagged by Gmail and Outlook's spam filters as a result. The database also contained 18,000 contacts who had not opened an email in 12 months, which were dragging down the engagement rate and compounding the deliverability problem. The solution was not a better subject line or a more compelling offer. It was a technical infrastructure rebuild: DNS records, IP warmup, database hygiene, and behavioural segmentation based on actual engagement data.

This guide covers the email infrastructure setup that prevents deliverability problems, the platform comparison for choosing the right ESP, the five-step implementation sequence, two case studies with documented results, and the six technical mistakes most responsible for poor email marketing performance in 2026.

The ESP (Email Service Provider) selection decision is the foundation of the email marketing infrastructure. The right choice depends on three variables: the business model (e-commerce, B2B SaaS, or general newsletter), the technical complexity required (simple broadcasts vs. behavioural automation), and the contact volume relative to the platform's pricing model. The comparison below covers the four most commonly used platforms for USA and UK markets in 2026.

Platform

Five-Step Email Infrastructure Setup

DNS authentication is the technical prerequisite that determines whether email from a domain is trusted by inbox providers. Three records are required: SPF (Sender Policy Framework), which specifies which mail servers are authorised to send email from the domain; DKIM (DomainKeys Identified Mail), which adds a cryptographic signature to outgoing emails that inbox providers verify against a public key published in DNS; and DMARC (Domain-based Message Authentication, Reporting, and Conformance), which tells inbox providers what to do with emails that fail SPF or DKIM checks and provides a reporting mechanism to the sender.

The DMARC configuration detail that most new senders miss: DMARC policy should be set progressively, not immediately to the strictest setting. The correct progression: start with p=none (monitor mode — failed emails are delivered but reported) for two weeks to identify any legitimate mail sources that are failing authentication; then move to p=quarantine (failed emails go to spam) once all legitimate sources are authenticated; then after 30 days of clean p=quarantine reports, move to p=reject (failed emails are blocked at the inbox provider level). Setting p=reject immediately without the monitoring phase can block legitimate emails from secondary sending services (transactional email, CRM, support tools) that are not yet authenticated under the domain.

Google and Yahoo's 2024 bulk sender requirements made DKIM and DMARC mandatory for domains sending more than 5,000 emails/day to Gmail addresses — and this requirement has effectively become the deliverability baseline across all major inbox providers regardless of volume. A domain without all three records configured will see increasing spam folder placement in 2026.

Watch for: DNS propagation delays — new DNS records take up to 48 hours to propagate globally. Use MXToolbox or the DMARC Analyser to confirm all three records are resolving correctly before beginning sends. Also check for existing SPF records that may conflict with a new ESP's SPF include statement — multiple SPF records on a single domain cause authentication failures.

Before migrating an existing email list to a new ESP or launching campaigns on a new IP, the database must be audited. The two categories of contacts that damage deliverability: hard bounces (invalid email addresses — these should never be sent to again and must be suppressed permanently), and chronically unengaged contacts (valid email addresses whose owners have not opened or clicked any email in the previous 90 days). Sending to chronically unengaged contacts drives down the engagement rate that inbox providers use to assess sender reputation, and some of these contacts may have been converted to spam traps (addresses that inbox providers monitor specifically to identify senders with poor list hygiene).

The segmentation structure that produces the highest ROI: divide the list into three engagement tiers — Active (opened or clicked in the last 30 days), Warm (opened or clicked in the last 31–90 days), and Dormant (no engagement in 90+ days). Send to Active and Warm segments for regular campaigns; build a separate re-engagement sequence for Dormant (3 emails over 2 weeks with a specific re-engagement offer or "we miss you" message); suppress any Dormant contacts who do not re-engage after the sequence from future sends. This approach consistently improves deliverability metrics (because the sending audience is more engaged) and produces higher ROI per send (because unresponsive contacts stop diluting the average).

For new lists being built from scratch: use double opt-in confirmation for all subscribers. A confirmed subscriber who has actively clicked a confirmation email is significantly less likely to mark future emails as spam than a single-opt-in subscriber, and inbox providers weight the list quality signal accordingly.

Watch for: Role-based email addresses (info@, support@, sales@) — these are often shared mailboxes or ticketing system inboxes where individual open and click behaviour is not meaningful. They should be excluded from engagement-based segmentation to avoid distorting the metric. Klaviyo suppresses role-based addresses automatically; other platforms require a manual filter.

A new sending IP address (or a new domain) has no sending reputation — inbox providers have no history of whether the mail from this source is wanted or unwanted. Sending a full campaign volume immediately from a new IP causes inbox providers to flag the activity as anomalous and route emails to spam. IP warmup is the process of gradually increasing sending volume over 4–6 weeks, starting with small volumes to the most highly engaged subset of the list, to establish a positive reputation before sending to the full database.

A standard IP warmup schedule for a 50,000-contact list: Week 1: 200 emails/day to the most engaged subscribers (most recent purchasers or highest open-rate segment); Week 2: 500/day; Week 3: 2,000/day; Week 4: 5,000/day; Week 5: 15,000/day; Week 6: full volume. The volume targets should be adjusted based on the engagement metrics at each stage — if spam complaint rate exceeds 0.08 percent (Google's threshold for negative reputation impact) at any volume level, pause and investigate before increasing further.

For brands migrating from one ESP to another, the new IP warmup applies even if the domain has an established sending reputation. The domain reputation and the IP reputation are separate signals — a well-established domain on a cold IP still requires warmup, because inbox providers weight IP reputation heavily in spam filter decisions.

Watch for: Sending too aggressively in the early warmup phase to hit "real" volume quickly. The 4–6 week warmup timeline exists because inbox providers need to see a pattern of consistent, well-received mail before extending full reputation credit. Shortcuts in the warmup phase produce the exact deliverability problems they are designed to prevent.

The three highest-ROI automated flows, in order of revenue impact, apply across both e-commerce and B2B SaaS contexts with different triggering conditions. For e-commerce: abandoned cart sequence (3 emails over 48 hours — first email at 1 hour, second at 24 hours, third at 48 hours with optional discount; targets contacts who added to cart but didn't purchase); welcome series (3 emails over 7 days introducing the brand, primary product benefits, and customer social proof to new subscribers); post-purchase sequence (3 emails over 14 days: delivery confirmation with accurate timeline, product use guide at expected delivery, review request at 7–10 days post-delivery). For B2B SaaS: onboarding sequence (triggered on account creation, timed around specific in-app actions or inactions — the goal is to reduce time-to-value and prevent early churn from users who don't activate the core feature); trial conversion sequence (triggered at trial day 7 and day 12, addressing the specific adoption blockers most common in the user base); and re-engagement for inactive users (triggered on 14-day login inactivity, with in-app guidance redelivered via email for users who have stalled in the onboarding journey).

The technical implementation detail that separates effective B2B SaaS email automation from generic drip campaigns: the emails must be triggered by actual user behaviour (logged in or not, completed a specific feature or not, reached a milestone or not), not just by elapsed time since signup. A time-based drip campaign sends the same email to every trial user on day 7 regardless of their adoption level — a user who has already activated the core feature and is a power user receives the same activation email as a user who has never logged in after signup. Behavioural triggering requires a backend API connection between the application database and the ESP; this is the implementation that AWS Lambda + Brevo or a custom Node.js middleware + Klaviyo handles.

Watch for: Flows that never exit — a user who abandons a cart, converts, and then triggers the same cart abandonment flow for a second cart should receive the post-purchase flow from their first purchase, not the cart abandonment flow again. Flow entry conditions must include suppression of recent purchasers to prevent sequences from applying to the wrong context.

Email deliverability is not a one-time setup — it requires ongoing monitoring and maintenance as the list grows, the sending volume changes, and inbox provider algorithms update. Three metrics to track weekly: delivery rate (emails delivered / emails sent — target above 99 percent; a drop below 97 percent indicates a deliverability problem that requires investigation before the next send); hard bounce rate (target below 2 percent — above this threshold indicates the list contains a significant proportion of invalid addresses that need to be suppressed); and spam complaint rate (target below 0.08 percent for Gmail; this is now a published threshold with direct reputation consequences).

Google Postmaster Tools and Microsoft SNDS (Smart Network Data Services) provide direct inbox-provider-side deliverability data — domain reputation, IP reputation, and spam rate as measured by Gmail and Outlook respectively. These tools are free and provide the most accurate deliverability signal available; every sender above 5,000 emails/month should have both configured and review them weekly.

Apple Mail Privacy Protection (MPP), introduced in iOS 15 and now present in the majority of Apple Mail clients, pre-loads email tracking pixels automatically — which causes Apple Mail to report an "open" event for every email delivered to an Apple Mail user, regardless of whether the email was actually read. This inflates open rate metrics for lists with a high proportion of Apple Mail users (typically higher-income, USA-skewing demographics). For accurate open rate benchmarking, segment by email client and look at click-through rate (which is not affected by MPP) as the primary engagement metric for Apple Mail users.

Watch for: Spam complaint rate spikes after specific campaigns — a single send to a poorly segmented or re-engaged audience can produce a complaint spike that damages domain reputation for subsequent sends to the entire list. Monitor complaint rate at the campaign level, not just the monthly average, to identify which specific sends are generating complaints and audit those sends for segmentation or content issues.

Two Case Studies: Email Infrastructure Rebuilds

Situation: A premium outdoor gear e-commerce brand had a 4 percent email open rate and $12,000/month in unrecovered abandoned cart revenue. Their database contained 45,000 contacts, of which 18,000 had not opened an email in 12+ months. Their domain was flagged by Gmail's spam filters after their previous agency sent to the full list immediately after migrating to a new ESP without completing IP warmup.

Approach: Nexentity removed the 18,000 chronically unengaged contacts from the active sending list (preserving them for a re-engagement sequence), implemented DKIM/SPF/DMARC records that the previous setup was missing, completed a 4-week IP warmup on the new ESP (Klaviyo), and deployed a 3-step abandoned cart sequence with personalised subject lines based on product category viewed.

Results (6 weeks):

• ▸Open rate increased from 4% to 38% (deliverability rebuild)
• ▸Abandoned cart recovery revenue: $12,000/month restored
• ▸Engagement rate increased 55% on active subscriber segment
• ▸Marketing team manual list management: 15 hours/week eliminated

Lesson: Database hygiene and infrastructure setup precede all content and strategy decisions — the same subject lines that produced 4% open rate in a compromised domain produced 38% in a clean one.

Situation: A UK financial software provider with 10,000 active platform users had a 40 percent early churn rate — users who signed up for a free trial were leaving within 14 days without activating the core feature (document management workflow). The existing onboarding was a time-based drip sequence that sent the same emails to all trial users regardless of activation status.

Approach: Nexentity connected the Node.js application backend to Brevo via API, mapping user activation events (first document uploaded, first workflow created, first team member invited) as triggers for specific email sequences. Users who completed an activation event received a confirmation and next-step sequence. Users who hadn't completed an activation event after 3 days received a help-focused sequence with in-app guidance delivered via email. AWS Lambda functions triggered Brevo API calls on specific in-app error events, so users who encountered a specific error type received a contextual troubleshooting email within 30 minutes.

Results (8 weeks):

• ▸Trial-to-paid conversion improved 28%
• ▸Support tickets reduced 30% (contextual error emails resolved common issues proactively)
• ▸£85,000 in new annual recurring revenue attributed to the onboarding sequence improvement

Lesson: Behavioural triggers (what did the user do or not do?) consistently outperform time-based triggers (how many days since signup?) for SaaS onboarding email sequences, because they send the right guidance at the moment of friction rather than on an arbitrary schedule.

Six Email Marketing Mistakes Costing $50,000+ Annually