whats-best.ai

Email Marketing & Newsletter

Mailjet

EU origin, foreign-owned 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.

by Mailjet SAS · www.mailjet.com

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 Integrator

Weighted verdict

Has to wire this into a stack that already exists. Wants a documented API with rate limits, webhooks that retry, a sandbox and a deprecation policy. Treats a partner-form integration page as a missing API, and reads "Zapier supported" as an outsourced one.

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

Scored by The Integrator

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 Integrator

The visual builder is documented with event, timer, action and condition blocks that branch on customer behaviour, workflow templates are ready-made, A/B testing covers subject lines and content, and automation can enter on contact-property updates the API can write — so journeys react to data from other systems. We found no public information on send-time optimisation, on testing that reports significance, or on holdout groups, which is what separates this from the top band. 2 5 6 13

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 Integrator

SPF and DKIM setup is documented for custom sending domains, dedicated IPs on Premium and Custom come with a vendor-run warm-up plan, automatic spam-list removal is stated, and support teams plus technical account managers are documented as monitoring reputation and resolving blocklist issues on the sender's behalf. We found no public information on DMARC guidance, an explicit hard-bounce suppression policy, or engagement-based sunsetting, so the evidence lands mid-range. 2 7 8 13

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 Integrator

Import is fine for my purposes: CSV, TXT and XLS with properties and consents stored natively, error screening, duplicate filtering, property updates via API, and bulk delete of contacts is documented. We found no public information on subscriber export including custom attributes, subscription and unsubscribe state, on engagement-history or template export, or on export throttling — so exit stays unevidenced even though deletion is. 5 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 Integrator

This is a real connection surface: a documented send API and SMTP relay covering marketing and transactional mail on one platform, real-time event webhooks configurable per event type through both interface and API, push into external queuing systems, inbound parse, sandbox mode and SDKs in six languages. But we found no public information on rate limits, webhook retry behaviour, API versioning or a deprecation policy, and the captured pages give an integration count of over one hundred while we found no named shop or CRM systems among them — so I would be building against undocumented operational limits. 1 2 13 14

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 Integrator

The server region is customer-selected between the United States and Europe rather than EU-standard, the captured pages give different figures on whether data stays exclusively in the EU, and the contracting entity's jurisdiction is not confirmed on the vendor's own pages while the notice names US-headquartered hosts, US payment providers and a US-based Sinch company in the chain. Credit where due: the subprocessor list is published in detail, transfer mechanisms are stated, and a group data protection officer is reachable — but the chain rests on standard contractual clauses and the Data Privacy Framework rather than staying inside the EU. 3 4

Report an error

Pricing transparency not rated — the vendor publishes no price

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 Integrator

The billing model is stated — price by emails sent per month, with unlimited contacts on Essential and Premium — and dedicated IPs are placed in Premium and Custom. But we found no public information on tier prices, send limits, overage rates or VAT treatment in the captured pages, so no invoice for any list size and send volume can be computed from public pages alone. 1 2 8 13

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.

Ownership Publicly listed ⚠ unverified 1/2 pts 3 Report an error
Data residency Not determined ⚠ unverified — uncited Report an error
Subprocessors Not determined ⚠ unverified — uncited Report an error

Where this could be wrong

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.

Sources (14)

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

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