Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Email Marketing › Email Fundamentals

Choosing an Email Platform

How to choose an email platform from what your programme needs: sending on your own domain, consent and suppression, flows, testing, data and leaving later.
Guideintermediate11 min readUpdated

Start from the programme, not the feature list

A feature list describes what a vendor wants to sell this year. A requirement describes what the email programme must be able to do, in a form that can be checked: "a person who unsubscribed stays suppressed when their address arrives again in a contact import" is a requirement; "advanced list management" is not. Write the requirements from the programme the business runs and the one it intends to run within the contract term: the flows it sends, the data those flows depend on, the consent records on its list, the people who will operate the platform and the systems it must talk to.

Two decisions come before the requirement list. The first is the category. The comparison of a CRM-centred suite and an email-first platform explains why a business whose marketing hands leads to a sales team usually needs a shared customer record, and one that sells directly to the person reading the email usually needs a platform built around sending. Choose the category first, then compare products within it. The second is the method. The guide to choosing and evaluating marketing tools sets out requirements before demos, scoring with evidence, a proof of concept, integration checks, total cost and a decision record, and the marketing tool evaluation template is its workbook. This guide does not repeat that method; it supplies the email-specific rows.

Mark each requirement essential, important or useful, as that method does. For an email programme, the essentials are usually the ones that protect people and the sending reputation, because they cannot be patched with a workaround after the move.

Requirement groupWhat the programme needsHow to verify it
Sending and authenticationMail signed with the business's own domain, aligned with the From address, carrying one-click unsubscribe headersVendor documentation, then test messages to seed addresses with full headers read
Consent and suppressionA consent record on every contact, preferences enforced as segments, one suppression list that survives every importImport a sample and the suppression file, re-import the sample, count who became mailable
Segments and flowsSegments from standard attributes; triggers from real events; exits checked before each send; priority between flowsBuild one real flow and push test contacts through every branch
Testing and measurementRandom splits, holdouts for flows, reporting on clicks and outcomes rather than opensSet up a holdout in the trial and read where the result is reported
Transactional separationMarketing and service mail kept on separate streams, with a marketing unsubscribe never stopping a receiptDocumentation and a test unsubscribe followed by a test order
Data and exitEvents from the shop or product, sync with the CRM, and a full export including suppressions and consent fieldsConnect a test event source and run a complete export before signing

Sending and deliverability requirements

No platform can promise the inbox. The deliverability guide explains that mailbox providers decide placement from identity, reputation and behaviour, and that only the first is purely technical. The platform's job is to make identity correct and to make good behaviour easy, so these requirements are about setup rather than placement claims.

Signing with the business's own domain. The platform must sign mail with DKIM using the business's domain, not only its own shared domain, and must let the business send from a domain or subdomain that aligns with the visible From address, so that DMARC passes. Its SPF include has to fit into the domain's existing record. Ask how the platform handles a dedicated subdomain for marketing mail, which the deliverability guide recommends so that marketing reputation is kept apart from the domain used for other correspondence.

One-click unsubscribe. RFC 8058 specifies a List-Unsubscribe header carrying an HTTPS address and a List-Unsubscribe-Post header with the value List-Unsubscribe=One-Click, so that a mail client can send a single POST request that the sender processes without further interaction, with both headers covered by the DKIM signature. Google's sender guidelines document one-click unsubscribe as a requirement for bulk senders of marketing and subscribed messages, alongside a clearly visible unsubscribe link in the body and processing of requests within a documented window; the list building and consent guide covers the subscriber's side of that mechanism. Verify that the headers appear on marketing sends and that a request takes effect at once.

Bounces, complaints and staged sending. Hard bounces and complaints should move addresses to the suppression list automatically. The platform should report bounces by type and complaints per send, so that a problem can be traced to a list source, and should make it easy to send to segments in stages, because the deliverability guide advises staging large sends and starting with engaged subscribers. The email sending domain setup checklist lists every line of this setup, and it is worth running against each shortlisted platform's documentation before the trial begins.

Authentication proves who sent the mail; the consent record proves the recipient asked for it. The list building and consent guide sets out what that record holds for every address: the source, the timestamp, the wording the person saw, the choices they made and, where double opt-in is used, the confirmation timestamp. The platform must store those as fields on the contact, let flows and segments read them, and include them in every export. A platform that keeps consent only as a yes or no flag cannot answer how anyone joined.

For the sign-up itself, check that the confirmation step can be designed rather than left as a default, that unconfirmed addresses can expire, and that each form can carry its own wording into the record. For the preference centre, check that it needs no password, applies changes immediately and maps each choice to a segment the sending process enforces automatically, because a preference honoured by memory is broken within months, as the segmentation guide warns.

The suppression list is the requirement most worth testing rather than reading about. It should be global, applying to every campaign and flow; it should keep unsubscribes, hard bounces and complaints as distinct types; and a suppressed address must stay suppressed when it arrives again in a contact import, a form submission from a different source or a CRM sync. The list building guide names that persistence as one of three things to confirm whatever the platform. Ask also how a suppression file from the old platform is imported, since the tutorial on migrating to a new email platform loads suppressions before a single contact.

Segments, flows and testing

Segments. The segmentation guide recommends a small set of standard attributes, such as lifecycle stage, engagement tier and stated preference, combined at send time rather than saved in every combination. The platform should support that, build engagement tiers from clicks and site or purchase activity rather than opens alone, and let a segment use purchase and product data from the shop or the product.

Flows. The automation hub describes every flow as a trigger, timing and exits, and names exits as the weakest point. Check that triggers fire from real events as they happen rather than from a nightly batch, that every exit is evaluated before each send and not only at entry, that one flow can take priority over another for the same person, and that a frequency cap can apply across flows and campaigns. Build one real flow during the trial, usually the welcome series, and push test contacts through every branch, including a purchase part-way through and an unsubscribe.

Testing and measurement. The email metrics and testing guide treats opens as an approximate signal, clicks as the primary engagement measure and outcomes as the goal. A platform should let a test be judged on clicks or conversions, split recipients at random, and tag links so that analytics records the outcome. For flows, the honest measure is a holdout group: a random share of qualifying people entered into the flow but sent nothing, with their outcome compared over the same window. Check whether the platform can build that split at entry, or whether it needs a workaround such as a random field on each contact, and write the workaround down as a cost.

Transactional mail. The promotional versus transactional comparison recommends separate streams: transactional email on its own authenticated subdomain and system, marketing on the consented list. Decide whether the new platform will send both or only marketing. Either way, a marketing unsubscribe must not stop a password reset, and a hard bounce should suppress both streams.

Data, integrations and the right to leave

An email platform is only as current as the data it receives. The data flow and integrations guide explains how to specify what a tool receives, what it sends back and which identifier it keys on. For email, the inbound list is usually: sign-ups from every form, product views, cart and checkout events and orders from the shop, or account and usage events from a software product, each with identifiers and values; and contact and consent updates from the CRM, with one system named as the owner of consent and unsubscribes so that the two cannot disagree. Outbound, the platform should send results back in a form that can be joined to the person: sends, clicks, unsubscribes and suppression changes.

The right to leave is a requirement, not a contract clause to read later. Before signing, run a complete export from the trial account and check that it contains active contacts with every consent field, each suppression type as a separate list, engagement history and enough of each flow's definition to rebuild it. The migration tutorial shows what a programme loses when the export is a contact list and nothing else, and the same gaps will apply when the business eventually leaves this platform. Contract terms on export and deletion belong in the total cost and contract section of the martech method. When an agency or freelancer will run the platform, the guide to hiring and evaluating an email marketing agency keeps the account in the business's name and lists what to ask the provider before any access is granted.

Trial with your own list

A demo uses the vendor's data; a trial uses yours, and only the second produces evidence for the essential requirements. Ask each shortlisted vendor for a trial or sandbox account, and treat a refusal as a finding to score. Then run the same checks on each:

  • Load a sample of real contacts with their consent fields, and the full suppression file. Re-import the sample with a few suppressed addresses added and count how many became mailable.
  • Set up authentication on a test subdomain, send to seed addresses at the major mailbox providers and read the headers: the DKIM signing domain, alignment with the From address and the two unsubscribe headers.
  • Build the welcome series with a purchase exit and a holdout, and push test contacts through every branch.
  • Connect one real event source, such as test orders from the shop, and check that a flow exits on the order.
  • Run a complete export and compare it with what was loaded.
  • Have the person who will run the platform do the work, with the vendor helping rather than driving.

Record each result against its requirement. The weighted scoring matrix turns the record into a comparison, with essential requirements applied as gates before any weighted total is added up, and the martech method adds total cost and the decision record. When the choice is made, the migration tutorial moves the programme across.

A baking supplier's shortlist (illustrative)

Illustrative example — not a real result

Flourwick Baking Supplies tests two platforms with its own list

Flourwick Baking Supplies, a wholesale supplier to home bakers with 14,600 subscribers, is replacing a basic newsletter tool that cannot run flows. It shortlists two platforms, called A and B here, and scores them from documentation first and then from a two-week trial in which its marketer loaded 2,000 real contacts with consent fields and its full suppression file of 1,140 addresses into each account. Weights run from 3 (essential) to 1.

RequirementWeightA from documentationB from documentationA after trialB after trial
Own-domain DKIM signing, aligned From, unsubscribe headers3 (gate)333: seed headers pass3: seed headers pass
Suppression survives re-import3 (gate)333: 0 of 40 re-subscribed0: 14 of 40 became mailable
Flow exits checked before each send2233: test order stopped the flow3: test order stopped the flow
Random holdout in a flow2232: needs a random contact field3: split at entry
Full export with suppressions and consent fields2333: complete2: consent timestamps missing
Weighted total323634Excluded at gate

On paper B led by 36 to 32. The trial reversed it: B's re-import turned 14 suppressed test addresses back into subscribers, which fails an essential requirement however the rest scores. Flourwick chose A, recorded the holdout workaround and B's export gap in the decision record, and moved its list using the migration tutorial.

Common mistakes

  • Letting the demo write the requirements. A requirement added after the demo is one the demo was built to avoid.
  • Comparing feature names. Two platforms can call the same capability by different names, or the same name by different capabilities; test the behaviour.
  • Trusting a placement figure. A vendor's inbox rate describes other senders' lists, not yours.
  • Testing suppression by reading about it. Re-import a sample with suppressed addresses in it and count.
  • Treating consent as a single flag. Without source, timestamp and wording, nobody can show how a contact joined.
  • Skipping the holdout question. A platform that cannot hold anyone out leaves every flow taking credit for people who would have bought anyway.
  • Leaving the export until the contract ends. Run a complete export during the trial, while there is still a choice.
  • Choosing the platform and the category in one step. Decide between a CRM-centred suite and an email-first platform before comparing products.

The fundamentals hub sets out the hygiene routine any platform will need to support once the programme is running on it.

Frequently asked questions

Should a small business simply pick the cheapest email platform?

Price is a fair tie-breaker between platforms that meet every essential requirement, and a poor reason to accept one that does not. The requirements that are hardest to fix after the move are signing mail with the business's own domain, a suppression list that survives re-imports, consent records that travel with each contact and a complete export. Check those first, then compare the total cost of the platforms that pass, as the general method for choosing marketing tools describes.

How can we judge a platform's deliverability before we buy it?

Mostly you cannot, and a vendor's figure for inbox placement describes other senders' lists. What a platform contributes is the sending setup: signing with your domain, an aligned From address, the one-click unsubscribe headers and automatic suppression of bounces and complaints. Verify those with test messages to seed addresses during the trial. Placement after that depends on the list, the consent behind it and how the programme sends, which is why the deliverability guide treats authentication as only one of three groups of signals.

Does the email platform also have to send our receipts and password resets?

No. Many businesses send transactional mail from the shop, the product or a separate transactional service on its own subdomain, and keep the marketing platform for campaigns and flows. What the marketing platform does need is the order and account events, so that flows can exit on a purchase, and suppression logic in which a marketing unsubscribe never stops a service message. The promotional versus transactional comparison sets out why the two streams are kept apart.

Terms used on this page

Frameworks

Where this page is used

Sources

  1. Email sender guidelines — Google Workspace Admin Help
  2. RFC 8058: Signaling One-Click Functionality for List Email Headers — IETF

Related