Email Marketing & Newsletter

MailerLite

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The CRM Manager v1.0 · The Deliverability Engineer v1.0 · The Data Protection Officer v1.0 · The Shop Owner v1.0 · The Integrator v1.0 · The Skeptic v1.0 · rubric v1 · evaluated 30 Sep 2026

Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Deliverability Engineer

Weighted verdict

Cares about one number nobody publishes honestly: what reaches the inbox. Reads for authentication, IP and domain reputation, bounce discipline and sunsetting. Ignores every advertised delivery rate on principle — the infrastructure either is documented or it is not.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Deliverability Engineer

Campaigns & automation

How this is scored

Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.

0 — One-off broadcasts from a fixed template; no segmentation and no automation of any kind.

3 — A drag-and-drop editor and simple list segmentation, but automation is a single welcome mail and there is no testing.

5 — Reusable templates, attribute and behaviour segmentation, multi-step automations on common triggers, and subject-line A/B testing.

8 — A visual journey builder with branching on behaviour and data, dynamic content per segment, send-time optimisation, and testing that reports significance rather than raw counts.

10 — Journeys treat the whole lifecycle: event-driven entry from other systems, branching on any attribute or event, holdout groups for measurement, and automations a marketer can read months later without a diagram.

Report an error

The Deliverability Engineer

The captured pages document a drag-and-drop editor with segmentation by engagement, geography, interests, purchase history and signup source, plus multi-step automations with per-tier limits and a webhook action usable inside workflows. I found no public information on subject-line A/B testing for campaigns or a journey builder that branches on behaviour, so this sits solidly mid-table rather than higher. 2 6 14

Report an error

Deliverability infrastructure

How this is scored

Whether the mail arrives — authentication, sending reputation, bounce and complaint handling — judged on what the vendor documents rather than the inbox rate it advertises.

0 — No documentation of authentication or bounce handling; deliverability appears only as a marketing number.

3 — SPF and DKIM setup documented, but no DMARC guidance, no stated bounce policy and shared sending only.

5 — SPF, DKIM and DMARC documented with a custom sending domain, automatic hard-bounce suppression, and complaint-loop handling stated.

8 — The above plus dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, and published guidance on list hygiene.

10 — Deliverability is operated as a service: reputation monitoring surfaced to the customer, per-domain and per-ISP diagnostics, enforced authentication before first send, and postmaster or blocklist handling the vendor documents doing on the customer's behalf.

Report an error

The Deliverability Engineer

Authentication is documented end to end — DKIM, SPF and domain verification records with an automated DNS setup path — and bounce discipline is real: hard bounces auto-suppressed, three consecutive soft bounces treated as hard, and a list-verification tool recommended. I found no public information on DMARC guidance, on warm-up for the dedicated IP that appears in the enterprise tier, or on inbox-placement testing, so the documented stack stops short of the top. 2 7 8

Report an error

Consent, proof & tracking limits

How this is scored

How subscribers arrive and what the sender can prove afterwards: double opt-in, logged consent, unsubscribe handling, and whether open and click tracking can be limited or switched off.

0 — Single opt-in with no consent record; tracking is always on and cannot be disabled.

3 — Double opt-in available but not the default, and the consent record is a timestamp without the source, IP or the wording consented to.

5 — Double opt-in as the documented default with a stored consent record including source and timestamp, one-click unsubscribe, and tracking that can be turned off per campaign.

8 — Consent is reproducible as evidence: the confirmation mail and form wording versioned and retrievable per subscriber, unsubscribe honoured across lists, tracking off-by-default available, and retention rules for inactive subscribers.

10 — Built for the burden of proof: a per-subscriber consent history an authority would accept, documented handling of Art. 15 access and Art. 17 erasure requests, pixel-free and link-tracking-free sending as a supported mode, and preference-centre granularity rather than all-or-nothing.

Report an error

The Deliverability Engineer

Double opt-in is the documented default on forms with a customizable confirmation email per form, every mail carries an opt-out link, and a subscriber preference centre appears in the paid tiers. I found no public information on a stored consent record showing source or the wording consented to, and nothing on turning open and click tracking off; the captured pages also state Do Not Track signals are not honoured. 3 2 3 9

Report an error

List ownership, import & exit

How this is scored

Whether the list and its history remain the sender's: import with attributes intact, full export including engagement history, deletion that executes, and no metering that prices leaving out of reach.

0 — Export is addresses only; engagement history, segments and automations cannot leave.

3 — CSV import and export of subscriber fields, but engagement history and unsubscribe state are not exportable.

5 — Full subscriber export including custom attributes, subscription status and unsubscribe state, plus API access sufficient to sync elsewhere.

8 — Everything exportable in open formats — subscribers, engagement history, campaigns and templates — with documented deletion of a subscriber across all records, and no export throttling.

10 — Exit is a documented feature: full-fidelity export of the whole account, contractual data return, deletion that is evidenced rather than asserted, and migration tooling in both directions.

Report an error

The Deliverability Engineer

Import arrives with field mapping, duplicate cleanup, banned-address screening and a direct Mailchimp path, and export covers custom fields, group membership, unsubscribed and bounced status, campaign opens and clicks, and automation activity, with deletion promised within 30 days of an eligible request. Campaigns and templates are not shown as exportable and the export function is administrator-only, so exit is workable but not a documented feature. 3 11 12

Report an error

Integrations & API

How this is scored

The connection surface a newsletter lives on: shop and CRM systems, events in and out, webhooks, and an API somebody can build against without a partner agreement.

0 — No API and no named integrations; the list is maintained by CSV upload.

3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.

5 — Named integrations for common shop and CRM systems, a documented REST API with keys, and webhooks for the core subscriber events.

8 — Maintained bidirectional integrations with named systems including at least one major shop platform, event webhooks with retries, documented rate limits, and a sandbox.

10 — The tool is a component rather than a destination: transactional and marketing sending on one API, events flowing both directions, versioned API with a deprecation policy, and integrations the vendor maintains rather than lists.

Report an error

The Deliverability Engineer

Shopify, WooCommerce, WordPress, Zapier and Canva are named among a claimed hundred-plus integrations, webhooks cover fifteen subscriber and campaign events with three retries, HMAC signatures and full create-read-update-delete management, and there is a batch endpoint plus an MCP server. I found no public information on a sandbox or on concrete rate-limit numbers beyond the batch cap, and transactional sending requires a separate MailerSend account rather than one API. 1 3 13

Report an error

European sovereignty

How this is scored

Where subscriber data and behavioural tracking live, who the contracting entity is, and which subprocessors touch the send. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily.

0 — US vendor and contracting entity, US hosting, subprocessors unnamed; subscriber behaviour leaves the EU with no stated basis.

3 — EU hosting offered as an option or for storage only, while sending, tracking or support access remains non-EU, or the subprocessor list is absent.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — sending infrastructure, analytics, support tooling — are non-EU without an explained safeguard.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, complete subprocessor list published, and any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting, sending and every subprocessor in the EU, certification published, and no transfer that needs a Schrems II argument to survive.

Report an error

The Deliverability Engineer

Hosting is documented in Germany and the Netherlands with a named infrastructure provider, an Irish contracting entity covers EEA, UK and Swiss billing addresses, and a long subprocessor list is published. A second Delaware entity with Data Privacy Framework certification and FTC authority serves everyone else, US-headquartered processors — Intercom for support, OpenAI and Google Vertex AI for AI features, Stripe for payments — appear with hosting regions unstated, and the EU-only hosting claim sits in FAQ and trust-page copy rather than contract text. 3 3 4

Report an error

Pricing transparency

How this is scored

Whether a sender can compute the real invoice for their list size and send volume — including overage, extra domains and automation limits — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A headline price per contact tier exists, but send limits, overage rates or the tier where automation begins are not stated.

5 — Contact-tier prices public with the billing period stated and send limits given, but at least one commonly needed capability sits in an unpriced tier or add-on.

8 — Every tier priced publicly with contact and volume limits, overage rates, feature boundaries and VAT treatment stated; only genuinely custom volume lacks a number.

10 — Complete price computability: a calculator producing the annual invoice for a given list size and send frequency, including overage, additional domains and dedicated IPs.

Report an error

The Deliverability Engineer

Entry prices are public with billing period and currency — $0 for up to 250 subscribers, $12 listed and $10.80 per month billed yearly for the entry paid tier, $25 and $22.50 for the next — send limits are stated per tier, and overage behaviour is spelled out as an automatic upgrade and charge. The enterprise tier carrying the dedicated IP shows no captured price, taxes are covered only as "may be subject to applicable taxes", and I found no public information on tier prices beyond the 500-subscriber entry point. 2 2 2

Report an error

European sovereignty — proven facts

1 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Legal entity	Not determined ⚠ unverified	—	uncited Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	Not determined ⚠ unverified	—	uncited Report an error
Subprocessors	US CLOUD Act reach ⚠ unverified	0/2 pts	3 Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 30 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Legal entity, Data residency. Not confirmed on the vendor’s own pages as captured.
Weak sourcing — Subprocessors. Intercom is US-headquartered and the policy does not state its hosting region; the policy also names other US-based processors of product data (OpenAI, Google Vertex AI, Stripe for payments), while no subscriber Personal Data goes to Intercom unless the customer uploads it to the live chat.
AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

46 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
27 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
23 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
13 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
8 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
3 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. Know more? Tell us

Do you know more about MailerLite? Tell us Report an error on this page

Sources (14)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

1 Vendor homepage www.mailerlite.com Checked 5 Oct 2026 +3 earlier captures: 28 Sep 2026, 16 Sep 2026, 30 Aug 2026 Details →
2 Pricing www.mailerlite.com Checked 5 Oct 2026 +3 earlier captures: 16 Sep 2026, 15 Sep 2026, 30 Aug 2026 Details →
3 Privacy policy www.mailerlite.com Checked 5 Oct 2026 +1 earlier capture: 16 Sep 2026 Details →
4 Security / trust page www.mailerlite.com Checked 5 Oct 2026 Details →
5 Campaigns & automation — found from sitemap www.mailerlite.com Checked 5 Oct 2026 +1 earlier capture: 30 Sep 2026 Details →
6 Campaigns & automation — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
7 Deliverability infrastructure — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
8 Deliverability infrastructure — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
9 Consent, proof & tracking limits — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
10 Consent, proof & tracking limits — found from sitemap www.mailerlite.com Checked 5 Oct 2026 +1 earlier capture: 30 Sep 2026 Details →
11 List ownership, import & exit — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
12 List ownership, import & exit — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
13 Integrations & API — found from sitemap developers.mailerlite.com Checked 5 Oct 2026 Details →
14 Integrations & API — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →