Email Marketing & Newsletter

Moosend

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Proven sovereignty

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

A visual workflow builder with branching logic, multiple triggers, real-time behaviour entry, segmentation and dynamic content, backed by 130-plus templates and A/B testing — that is a genuine journey builder, not a welcome mail. We found no public information on send-time optimisation or testing that reports significance, so it stays short of the top band. 4 5 10 1

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

SPF, DKIM, DMARC and even BIMI are documented, a custom sending domain is stated, there is a public DMARC policy checker with DNS recommendations, and M3AAWG and Certified Senders Alliance membership is claimed. But we found no public information on a bounce or hard-bounce suppression policy, complaint-loop handling, dedicated IP options or warm-up, and the 98% delivery guarantee and 0.02% spam rate are advertised numbers I disregard on principle. 6 7 3

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 documented as available with GDPR relevance, and a GDPR addendum page exists, but nothing shows it is the default or what the consent record stores. We found no public information on unsubscribe mechanics, consent logging, or any way to limit open, click or website tracking — the cookie-based tracking that identifies individual users is promoted as a feature, never as something a sender can switch off. 6 9 10

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

Inbound is documented — a MailChimp list import, an API to create and manage campaigns and lists programmatically — and the terms pages say they cover data ownership and account termination. We found no public information on subscriber export, whether engagement history or unsubscribe state can leave the platform, or deletion that is evidenced rather than asserted. 11 3 2

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

Forty-two native integrations counted on the page including WooCommerce and Magento, a thousand more via Zapier, and SMTP plus a transactional API alongside marketing sending — respectable breadth on one platform. We found no public information on event webhooks with retries, documented rate limits, or a sandbox, which is what separates a solid surface from a buildable one. 11 12 7

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

The trust page states customer contact data is hosted in the EU through AWS, and the contracting entity is a London company under UK law — but the same pages state Moosend is now a Constant Contact company without stating that parent's jurisdiction, and we found no published subprocessor list. AWS being a US-headquartered provider puts the stored data within reach of the US CLOUD Act, and the EU-hosting claim covers only contact data in marketing copy. 3 2 5 10

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

Prices of $7 and $9 per month are public with monthly, biannual and annual billing periods at exact stated discounts, and unlimited campaigns and sends are stated alongside a free trial. But the captured pages give no contact counts for those tiers, no VAT treatment and no overage rates, so a sender cannot compute the real invoice for their list size from these pages alone. 1 7

Report an error

European sovereignty — proven facts

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	Incorporated in GB ⚠ unverified	1/3 pts	2 Report an error
Ownership	Foreign-controlled ⚠ unverified	0/2 pts	3 Report an error
Data residency	EU only ⚠ unverified	3/3 pts	3 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 29 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Ownership. The page never states Constant Contact's own jurisdiction or the deal structure; classifying it as foreign-controlled rests on outside knowledge that Constant Contact is a US company.
Weak sourcing — Legal entity. The imprint gives only a London address rather than a company register, and the site also states "Moosend is now a Constant Contact company", so the UK entity may no longer be the operative contracting party.
Weak sourcing — Data residency. The claim sits in trust-center marketing copy and covers only "customer's contact data"; no contractual statement in the excerpts confirms the region of all product data or that no non-EU default exists.
Weak sourcing — Subprocessors. AWS is a US-headquartered provider, so the US CLOUD Act reaches the customer data even though the same page states the hosting is EU-based.
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.

3 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
1 integrations 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
1 legal 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

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

Sources (12)

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

1 Vendor page www.moosend.com Checked 29 Sep 2026 Details →
2 Terms of service — found from the homepage moosend.com Checked 30 Sep 2026 Details →
3 Security / trust page — found from the homepage moosend.com Checked 30 Sep 2026 Details →
4 Campaigns & automation — found from sitemap moosend.com Checked 30 Sep 2026 Details →
5 Campaigns & automation — found from sitemap moosend.com Checked 30 Sep 2026 Details →
6 Deliverability infrastructure — found from sitemap moosend.com Checked 30 Sep 2026 Details →
7 Deliverability infrastructure — found from sitemap moosend.com Checked 30 Sep 2026 Details →
8 Consent, proof & tracking limits — found from sitemap moosend.com Checked 30 Sep 2026 Details →
9 Consent, proof & tracking limits — found from sitemap moosend.com Checked 30 Sep 2026 Details →
10 List ownership, import & exit — found from sitemap moosend.com Checked 30 Sep 2026 Details →
11 Integrations & API — found from sitemap moosend.com Checked 30 Sep 2026 Details →
12 Integrations & API — found from sitemap moosend.com Checked 30 Sep 2026 Details →