Email Marketing Evaluation Criteria

Turn this article into takeaways for your work.

Each assistant summarizes the article only for you and suggests best practices for your work.

Updated September 2026.

Most email marketing evaluations fail on one thing: the buyer scores features they can see in a demo and skips the two that actually determine whether the platform works, deliverability and the pricing basis. This checklist covers both, plus the criteria that separate a platform that fits your sending pattern from one that gets expensive or gets your mail routed to spam.

What email marketing evaluation criteria are (and why deliverability and pricing basis top the list)

Email marketing evaluation criteria are the specific, testable capabilities you score each vendor against before you migrate your list and your sending reputation. They are not the feature checklist on the vendor's homepage. A homepage checklist tells you a platform "has automation." An evaluation criterion tells you whether that automation can branch on a purchase event, hold for three days, then check a different condition, because that's the actual workflow your business needs.

Two criteria matter more here than in almost any other software category, and both are easy to skip in a demo. The first is deliverability: whether your email lands in the inbox at all, which depends on infrastructure decisions the sales rep won't volunteer. The second is the pricing basis itself. Some platforms charge by contacts on your list; others charge by emails sent per month, and that single difference can flip which vendor is cheaper, independent of the sticker price. Our full guide to choosing email marketing software covers the broader selection process; this piece is about scoring the criteria once you have built a shortlist.

Key Facts: email marketing evaluation

  • Apple's Mail Privacy Protection, active since iOS 15, pre-fetches images in Apple Mail so open rates from Apple Mail users are artificially inflated and can no longer be trusted as a standalone metric (Apple Developer documentation on Mail Privacy Protection).
  • Email marketing returns $36 to $42 for every $1 spent, according to Litmus's State of Email survey data, a figure widely cited in the industry though it should be treated as a directional benchmark, not a guarantee for any specific list or platform (Litmus, cited via Constant Contact).
  • Brevo prices by emails sent per month rather than contacts on your list, while Mailchimp and Klaviyo price by contact or profile count, a structural difference that changes which vendor is cheaper depending on your send frequency (Brevo pricing, Mailchimp pricing).

The email marketing evaluation criteria checklist

Score each criterion 1-5 during a trial and vendor calls, then multiply by weight. Do not score from the demo alone. Several of these only reveal themselves once you send real mail to a real list.

Criterion What good looks like Watch out for
Deliverability and sending reputation Shared IP pool actively monitored by the vendor, with a documented dedicated-IP option once you cross a volume threshold. Automatic list-hygiene features: bounce handling, spam-complaint suppression, inactive-subscriber flagging. Vendors that treat deliverability as entirely your problem. No visibility into your own sender score or bounce classification. Dedicated IPs offered with no guidance on the warmup period needed to use them safely.
Authentication support One-click or guided setup for SPF, DKIM, and DMARC on your sending domain, with a dashboard that shows current authentication status. Authentication buried in developer docs with no in-app verification. No DMARC guidance at all, which matters more since Google and Yahoo's 2024 bulk-sender rules made it a practical requirement.
Pricing basis (contacts vs. email volume) A pricing model that matches how you actually send. High-frequency senders with a small list want volume-based pricing; large lists with infrequent sends want contact-based pricing with a generous send allowance. Contact-based pricing that charges for unsubscribed or unengaged contacts you cannot easily purge. Volume-based pricing with no visibility into how close you are to the monthly cap until you get throttled.
Automation and branching logic Multi-step, multi-condition workflows: branch on link click, purchase value, or time delay, with the ability to re-enter or exit a flow based on new behavior. Automation that only supports linear sequences (send A, wait, send B) with no true branching. Advanced triggers gated to the top pricing tier.
Segmentation and behavioral triggers Segments built from behavior (opened, clicked, purchased, browsed) combined with profile data, updated in real time. Triggered sends fire within minutes of the qualifying event. Segmentation limited to static list membership or basic demographic fields. Behavioral segments that only refresh on a daily batch, which kills time-sensitive triggers like cart abandonment.
Data model depth Native support for ecommerce and product-level events (purchases, browsed products, cart contents), not just contact fields like name and email. Custom event tracking via API. A contact-fields-only data model that forces ecommerce data into generic custom fields, breaking dynamic product recommendations and revenue attribution.
Template and editor quality A drag-and-drop editor that renders consistently across major email clients, with mobile preview and a real HTML/code editing mode for anyone who needs it. Templates that look fine in the builder but break in Outlook. No raw HTML access, which blocks anyone who wants precise control.
Integrations (store and CRM) Native, vendor-maintained connectors for your ecommerce platform or CRM, syncing two-way (orders and customer data flow in, engagement data flows back out). Integrations that only push data one direction, or that rely entirely on Zapier for a connection this central to the tool's value.
Reporting beyond open rate Click-through rate, conversion and revenue attribution, list growth and churn, and deliverability metrics (bounce rate, spam complaint rate) all visible without an export. A reporting dashboard still built around open rate as the headline metric, with no acknowledgment that Apple Mail Privacy Protection has made it unreliable.
Deliverability reporting you can audit Placement testing (inbox vs. spam vs. missing), sender reputation scoring, and domain-level authentication status, all in one view you can check before a send, not just after. No placement testing at all, or placement data buried behind a paid add-on with no free way to sanity-check a new domain.

The three authentication protocols, and what each one actually does

Vendors mention SPF, DKIM, and DMARC in the same breath, but they solve different problems and a platform can support one without the other two.

Protocol What it verifies Why it matters for deliverability
SPF (Sender Policy Framework) Which mail servers are allowed to send on behalf of your domain Blocks the crudest spoofing; most receiving servers check it before anything else
DKIM (DomainKeys Identified Mail) A cryptographic signature proving the email content wasn't altered in transit Confirms message integrity, which builds sender trust over time
DMARC (Domain-based Message Authentication) Tells receiving servers what to do when SPF or DKIM checks fail, and reports back to you Required in practice since Google and Yahoo's 2024 bulk-sender rules; without it, legitimate mail can get quarantined right alongside spoofed mail

A platform that only helps you set up SPF is doing a third of the job. Score this criterion on all three, not just the one that's easiest to configure.

How to weight the criteria

Weighting shifts more by sending pattern here than by company size. A high-volume transactional sender and a small list with weekly newsletters should not use the same weights.

Criteria group Criteria included Small list, frequent sends Large list, ecommerce Occasional newsletter sender
Deliverability and authentication Sending reputation, SPF/DKIM/DMARC, deliverability reporting 30% 20% 15%
Pricing basis fit Contacts vs. volume match to your sending pattern 20% 15% 20%
Automation and segmentation Branching logic, behavioral triggers 15% 25% 10%
Data model and integrations Ecommerce/CRM data depth, native connectors 10% 25% 10%
Templates and reporting Editor quality, reporting past open rate 15% 10% 25%
Support and ease of use Onboarding, documentation, support responsiveness 10% 5% 20%

A small list sending daily lives or dies on deliverability, since a shared IP pool's reputation is shaped by every sender on it. An ecommerce brand with a large list weights automation and data model highest, since abandoned-cart and product-triggered sends are where the revenue comes from. An occasional sender, think a quarterly newsletter, should weight ease of use and reporting clarity highest, since the tool needs to be re-learnable every time someone opens it.

If your list includes contacts from an ecommerce platform, check our guide to choosing email marketing for ecommerce before finalizing weights, since the ecommerce-specific data model criteria carry more weight there than a generic checklist assumes.

Contact-based vs. volume-based pricing

Settle this before comparing a single dollar figure. Get it wrong and the "cheaper" vendor on paper can end up costing more once your sending pattern hits their pricing model.

Pricing basis How it works Best fit Watch out for
Contact-based You pay by the number of contacts on your list, generally with a send allowance included at each tier. Mailchimp and Klaviyo both use this model. Large lists sent to infrequently, or businesses whose costs should track audience size, not send frequency. Unengaged and unsubscribed contacts that still count against your tier unless you actively prune the list.
Volume-based You pay by emails sent per month, regardless of list size. Brevo is the clearest example in this category. High-frequency senders, transactional email, or smaller lists emailed daily. Hitting the monthly send cap mid-campaign with no visibility into how close you are until you're throttled.

Key questions to ask vendors

Ask these after the demo, when the rep has to answer without a script.

  1. "Is my sending IP shared or dedicated, and who else is on that shared pool?" The vendor won't name names, but they should explain how they vet who gets onto a shared pool, since its reputation depends on every sender using it.

  2. "At what volume does a dedicated IP make sense, and who manages the warmup?" An unmanaged dedicated IP can tank deliverability worse than a well-managed shared pool.

  3. "Does your price scale by contacts on my list, or emails I send per month?" Ask what happens to unengaged or unsubscribed contacts under contact-based pricing: do they still count against your tier?

  4. "Can I branch an automation on a purchase event and a link click in the same flow?" This tests real branching logic versus a linear sequence builder wearing an "automation" label.

  5. "What does your data model do with ecommerce events like abandoned cart or repeat purchase?" If the answer involves stuffing order data into a generic custom field, the data model wasn't built for commerce.

  6. "What reporting do you have on deliverability and inbox placement, not just opens?" A vendor with no placement or bounce-rate reporting is asking you to fly blind now that Apple Mail Privacy Protection has inflated opens.

  7. "Can you run a live send to a small seed list right now so I can check placement?" Resistance to a live test during the sales process is a signal worth weighing on its own. Our SaaS vendor evaluation scorecard has more on reading vendor behavior during diligence.

What to test during the trial

Score sheets and demos only get you so far. Run these tests with real data before you commit.

Test What it reveals How long it takes
Seed-list deliverability test Actual inbox placement across Gmail, Outlook, Yahoo, and Apple Mail, not just a "sent" confirmation About an hour to set up, a day to check results
Authentication verification Whether SPF, DKIM, and DMARC are actually configured correctly, checked with an external tool 30 minutes if the platform's onboarding is good
Automation branching test Whether the automation builder handles true conditional branching or just linear sequences One afternoon to build and trigger both branches
Segmentation refresh speed How long a behavioral trigger takes to move a contact into a live segment or automation A few minutes per trigger, once set up
List import and hygiene check How the platform handles duplicates, malformed addresses, and role-based inboxes on import 15 to 30 minutes with a real sample list

Run each of these with real data, not the platform's own sample dataset. A sample list is clean by design and will not show you how the platform behaves with the duplicates, typos, and role addresses your actual list carries.

The seed-list test is the one to prioritize if you only have time for one: build 15 to 20 addresses across Gmail, Outlook, Yahoo, and Apple Mail, send a real campaign through the platform's normal flow, and check each inbox directly rather than trusting a "sent" confirmation. It surfaces infrastructure problems that a sales demo will never show you, and it costs about an hour.

Pricing: what to expect, and why the basis matters more than the number

Email marketing pricing splits on a structural question before it splits on dollar amount: does the vendor charge for contacts on your list, or emails sent per month? Get this wrong and you can end up paying for headroom you don't use, or hitting a volume cap on a plan that looked cheap on paper.

Vendor Entry price Billing term Based on
Mailchimp Free ($0, up to 250 contacts and 500 sends/mo capped at 250/day); Essentials from $13/mo; Standard from $20/mo as stated, at the smallest paid contact tier Contacts on your list
Klaviyo Free (up to 250 active profiles, 500 emails/mo) n/a for free tier; paid tiers via configurator Active profiles
Brevo Free ($0, 300 emails/day cap); Starter $9/mo monthly or $8.08/mo paid yearly monthly or annual, as stated Emails sent per month
MailerLite Free (up to 250 subscribers, 2,500 emails/mo); Comfort from $12/mo monthly, discounted paying annually Active subscribers
Constant Contact Lite from $12/mo monthly ($10.20/mo annually) monthly or annual (15% discount) Contacts, with a send cap scaled to the tier
ActiveCampaign Not disclosed by a direct fetch today; tiers are Starter, Plus, Pro, Enterprise 14-day free trial, no credit card Contact-count multiplier per tier
Kit Automated access blocked; check the vendor's own pricing page n/a Subscriber count

Mailchimp and Klaviyo both price by list size (contacts and active profiles, respectively), with Klaviyo's paid tiers running through an interactive configurator rather than a fixed price list. Brevo is the clearest volume-based example: its cost tracks emails sent per month, not how many contacts sit on the list, which is why a large but infrequently emailed list can come out cheaper on Brevo than on a contact-based competitor of the same size. MailerLite prices by active subscriber count, and Constant Contact by contact count with a send allowance that scales per tier (10x for Lite, 12x for Standard, 24x for Premium); Constant Contact doesn't publish the exact contact count behind each starting price on the page itself.

ActiveCampaign's pricing page renders dollar amounts through an interactive, region-aware calculator that returned no fixed numbers on a direct fetch today; its model tiers Starter, Plus, Pro, and Enterprise by a contact-count multiplier, with a 14-day free trial, no credit card required. Kit's pricing page blocked automated access entirely. Check both vendors' own pages directly for current figures rather than a third-party listicle, since this category re-prices often enough that secondhand numbers go stale fast.

Frequently asked questions

What's the single most important email marketing evaluation criterion?

Deliverability, ahead of every feature on the checklist. A platform with the richest automation and segmentation is worthless if your mail lands in spam. Run the seed-list test before you weight anything else, and treat a vendor's evasiveness about shared-IP reputation as a real signal.

Should I care about open rate at all anymore?

Use it as a rough trend indicator, not a precise metric. Apple Mail Privacy Protection pre-fetches images for a large share of Apple Mail users, which inflates opens and makes cross-platform comparisons unreliable. Weight click-through rate, conversion, and revenue attribution higher when you score the reporting criterion.

Is contact-based or volume-based pricing better?

Neither is universally better; it depends on your ratio of list size to send frequency. A large list emailed once a month favors volume-based pricing, since you're not paying per contact for mail you rarely send. A smaller list emailed daily favors contact-based pricing with a generous send allowance. Calculate both against your actual 12-month sending plan, not just this month's numbers.

How many email platforms should I trial before deciding?

Two, run in parallel if you can. Trialing three or more email platforms means splitting your list or running duplicate sends, which muddies your deliverability test results. Pick your top two from the criteria table, run the seed-list and automation tests on both, and decide.

Do I need a dedicated IP?

Not until you're sending consistent volume, generally above 50,000 to 100,000 emails a month, and only if sending is frequent enough to keep the IP warm. Below that, an intermittently used dedicated IP often performs worse than a well-managed shared pool, since a cold IP looks suspicious to receiving mail servers. For a broader view of email inside a wider automation stack, see our marketing automation software guide.

About the author

Calvin D.

Calvin D.

Head of Enterprise Solutions

Calvin D. is Head of Enterprise Solutions at Rework, with 5+ years and 40+ enterprise engagements spanning 20 to 500+ user deployments. Calvin helps Heads of Operations, IT Directors, and VPs connect CRM, workflow automation, and data into one stack that actually fits together. Readers get field-tested architecture decisions they can apply as their teams scale.