whats-best.ai

Email Marketing & Newsletter

Acumbamail

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

by Acumbamail · www.acumbamail.com

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

Link to this page

Acumbamail: AI-assisted analysis on whats-best.ai Acumbamail: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Acumbamail at a glance

Vendor
Acumbamail
Headquarters
Not stated on the vendor’s pages as of 20 Oct 2026
Data hosting
Not stated on the vendor’s pages as of 20 Oct 2026
Free plan
Yes, per the vendor’s own page source, captured 20 Oct 2026
Panel verdict
The AI panel rates Acumbamail 1.5/5, the mean of 6 judges. Acumbamail is an email marketing and newsletter platform with SMS marketing alongside, judged here on its public pages. how scores are made
As of
Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources

Acumbamail alternatives, European ones first →

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

The panel's verdict

Acumbamail is an email marketing and newsletter platform with SMS marketing alongside, judged here on its public pages. Its strongest showing is campaign and automation, where scores cluster at 4-5: flows whose nodes hold a template, a waiting time or a condition that branches the path in two, an editor with more than 861 editable responsive templates, custom HTML and in-editor image editing, with email and SMS combinable in one flow. Deliverability follows at 3-4, resting on a documented DMARC sender-verification configuration page and an explainer video on spam filters. The weak end is sovereignty at 1-2 — the pages name Acumbamail SL and claim GDPR compliance predating the regulation's mandatory date, and we found no public information on data residency, ownership or subprocessors — and pricing transparency at a flat 2: the free tier of 2,000 emails/month for life is stated, but no paid tiers, send limits, overage rates or VAT treatment, and high-volume pricing is a phone-call sale. Consent and proof spreads 2-3 on glossary definitions; list data control sits at 2 with only the inbound Mailchimp import documented.

Report an error

Speaks for it

  • Flow automations whose nodes hold a template, a waiting time or a condition branching the flow into two paths, with email and SMS combinable in one flow
  • Editor with more than 861 editable responsive templates, custom HTML and in-editor image editing
  • Free tier of 2,000 emails/month for life, plus 5 trial SMS and pay-per-send SMS in bonus packs that carry no expiry at the same price via API as via the platform
  • Native integrations with free downloadable plugins and an API documented as a simple HTTP POST callable from any programming language, with web/CMS, ERP and CRM named as targets
  • DMARC sender-verification configuration documented and described as indispensable for Gmail and Yahoo senders

Report an error

Held against it

  • Sovereignty scores sit at 1-2: beyond the Acumbamail SL name and GDPR claims, we found no public information on data residency, ownership or subprocessors
  • Pricing transparency sits at a flat 2: paid contact tiers, send limits beyond the free plan, overage rates and VAT treatment are not published, and high-volume pricing is routed to a sales call
  • Only the inbound side of list control is documented — a Mailchimp import tutorial — with no public information on exporting subscriber fields or engagement history or on documented deletion
  • We found no public information on whether double opt-in is a platform default, what a stored consent record contains, or on limiting or switching off open and click tracking
  • We found no public information on webhooks, documented rate limits, a sandbox, or a named shop-platform integration

Report an error

Best for

  • You need a permanent free tier — 2,000 emails/month for life — for a small list.
  • You want multi-step email and SMS automations built from a large no-code template library.
  • You want to send SMS programmatically from an HTTP POST API callable in any programming language.

Report an error

Avoid if

  • You weigh data residency, ownership and subprocessor disclosure heavily in a purchase decision.
  • You need documented terms for taking your list, attributes and engagement history with you when you leave.
  • You send at volume and need documented bounce handling, dedicated-IP options or warm-up practice.
  • You run a shop and need carts or purchases as automation entry triggers or a named shop-platform integration.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Campaigns & automation 2 of 5
Deliverability infrastructure 1.5 of 5
Consent, proof & tracking limits 1.5 of 5
List ownership, import & exit 1 of 5
Integrations & API 2 of 5
European sovereignty 1 of 5
Pricing transparency 1 of 5

Campaigns & automation

Show reasoning
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 CRM Manager

The flow product is real: nodes that hold a template, a waiting time, or a condition splitting the flow into two paths, with waits measured from the trigger event, and an editor backed by more than 861 editable templates. I found no public information on A/B testing, significance reporting, or dynamic content per segment, so this reads as a capable multi-step builder rather than a measured lifecycle programme. 1 2 9

Report an error

The Deliverability Engineer

Automation is real and documented: flows whose nodes hold a template, a waiting time or a condition branching the flow in two — for example paying versus non-paying customers — with delays configurable down to a welcome mail one minute after signup. The editor backs it with 861-plus responsive templates, custom HTML and in-editor image editing, but I found no public information on A/B testing, send-time optimisation or dynamic content per segment. 1 2 9

Report an error

The Data Protection Officer

Automations are genuinely multi-step: each node can hold a template, a waiting time or a condition that splits the flow into two paths, with email and SMS combined in one flow and triggers based on a chosen event. On top of that sits a no-code editor with more than 861 editable templates and custom HTML, so this clears the welcome-mail-only level. We found no public information on list segmentation outside the flow conditions, A/B testing, dynamic content per segment or send-time optimisation. 1 2 9

Report an error

The Shop Owner

The template editor with more than 861 designs plus an automation builder with waiting times and conditional branching — they use paying versus non-paying customers as the example — gets a shop partway there. I found no public information on A/B testing, send-time optimisation or dynamic content per segment, and nothing showing store events like carts or purchases as flow entry triggers, so it stays mid-range for my needs. 1 2 9

Report an error

The Integrator

There is a real editor — more than 861 editable templates, custom HTML, in-editor image editing — and flow automations whose nodes send a template, wait, or branch on a condition such as paying versus non-paying customers, which is a genuine multi-step journey rather than a single welcome mail. We found no public information on list segmentation tools, A/B testing, send-time optimisation or holdout groups, so it stops short of the mid-level definition. 1 2 9

Report an error

The Skeptic

The automation pages show genuine flows — nodes holding a template, a wait time or a condition that splits the path in two, with delays anchored to a trigger event such as a signup — and the editor offers more than 861 editable responsive templates, custom HTML and in-editor image work. I found no public information on list segmentation as a standalone capability, A/B testing, dynamic content or send-time optimisation, which keeps this short of a full journey builder. 1 2

Report an error

Deliverability infrastructure

Show reasoning
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 CRM Manager

A documented DMARC sender-verification configuration and a video explaining how spam filters work is genuine documentation rather than an inbox-rate claim. I found no public information on bounce handling and hard-bounce suppression, complaint loops, custom sending domains, dedicated IPs or warm-up, which leaves the documented surface thin for a serious sender. 3 4

Report an error

The Deliverability Engineer

DMARC sender-verification configuration is documented and described as indispensable for the large providers, and the vendor publishes an explainer on how spam filters work. I found no public information on bounce handling or hard-bounce suppression, complaint loops, dedicated IP options, warm-up or engagement-based sunsetting — the discipline that decides what reaches the inbox is not written down anywhere I can see. 3 4

Report an error

The Data Protection Officer

The captured deliverability material is a DMARC sender-verification configuration page, whose address also names DKIM, plus an educational video explaining how spam filters work. We found no public information on bounce or complaint handling, sending infrastructure options such as custom or dedicated domains and IPs, warm-up, engagement sunsetting, or list-hygiene guidance, so the claim that mail arrives rests on the vendor's word rather than documented practice. 3 4

Report an error

The Shop Owner

The captured page documents DMARC sender-verification configuration and there is an explainer video on how spam filters work, which is authentication guidance plus education. We found no public information on a stated bounce policy, complaint-loop handling, dedicated IP options or engagement-based sunsetting, so the documented surface does not go further. 3 4

Report an error

The Integrator

The documented surface is a DMARC sender-verification configuration page plus an educational video on how spam filters work. We found no public information on documented SPF or DKIM setup steps, custom sending domains, bounce or complaint handling, dedicated IPs or warm-up, so only the thin authentication-documentation level is evidenced. 3 4

Report an error

The Skeptic

The verification page covers DMARC configuration, described as indispensable for Gmail and Yahoo senders, and there is a video explaining how spam filters work and how to keep legitimate mail out of them. Beyond that we found no public information on SPF setup, a stated bounce or complaint-handling policy, custom sending domains or dedicated-IP options. 3 4

Report an error

List ownership, import & exit

Show reasoning
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 CRM Manager

The only exit-adjacent evidence points one direction of travel: a video tutorial for importing subscribers from Mailchimp. I found no public information on exporting subscriber fields, engagement history or unsubscribe state, on documented deletion of a subscriber, or on any export tooling, so I cannot treat the list as verifiably remaining the sender's. 7

Report an error

The Deliverability Engineer

The way in is published: a tutorial walks through importing subscriber lists from Mailchimp. The way out is not — I found no public information on exporting subscribers with attributes and unsubscribe state, on engagement history, or on documented deletion of a subscriber across records. 7

Report an error

The Data Protection Officer

A video tutorial covers importing subscribers from Mailchimp, so arrival is supported. We found no public information on export of subscriber data, engagement history or unsubscribe state, on deletion that executes across records, or on any export or migration capability in the other direction — leaving is asserted nowhere I can cite, and I will not assume it. 7

Report an error

The Shop Owner

There is a video tutorial for importing subscribers from Mailchimp, which covers arriving. We found no public information on exporting subscribers with their attributes and engagement history, on documented deletion across records, or on any migration path out, so exit remains a question mark for my customer list. 7

Report an error

The Integrator

What is public is the inbound side only — a video tutorial for importing subscriber lists from Mailchimp. We found no public information on exporting subscriber fields or custom attributes, engagement history, unsubscribe state, or on documented deletion of a subscriber; for the question that matters to me, whether the list and its history can leave, there is nothing published. 7

Report an error

The Skeptic

Getting in is documented — a video tutorial walks through importing subscriber lists from Mailchimp, and an API is listed in the footer. On the way out, we found no public information on exporting subscriber fields or engagement history, on deletion of a subscriber across all records, or on export throttling, so the terms of leaving cannot be judged from these pages. 7 1

Report an error

Integrations & API

Show reasoning
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 CRM Manager

The integrations page lists multiple native integrations with free downloadable plugins, and the API runs over plain HTTP POST from any programming language, positioned for CMS, ERP and CRM connections with an SMS gateway. I found no public information on webhooks, documented rate limits, a sandbox, or a named shop-platform integration, so the surface reads send-oriented rather than event-driven. 1 8 9

Report an error

The Deliverability Engineer

The integrations page lists multiple native integrations with free downloadable plugins, and an HTTP POST API usable from any programming language is documented for the SMS gateway, with API documentation linked in the footer. I found no public information on webhooks, documented rate limits, a sandbox, or maintained bidirectional integrations with named shop or CRM platforms. 1 8 9

Report an error

The Data Protection Officer

The integrations page lists multiple native integrations with downloadable free plugins alongside POWERED BY entries, and a documented API reachable from any language over HTTP POST for web, CMS, ERP, CRM and app connections, with SMS also sendable from a web panel. The API material centres on SMS sending, and we found no public information on webhooks, documented rate limits or a sandbox, which keeps this below the maintained bidirectional tier. 1 8 9

Report an error

The Shop Owner

The integrations page lists multiple native integrations with free downloadable plugins, and API support is reachable from the footer, documented as working over HTTP POST from any programming language with the SMS gateway spelled out and web/CMS, ERP and CRM named as targets. The captured pages name no specific shop platform, and we found no public information on webhooks, documented rate limits or a sandbox — so my orders, carts and products have no evidenced path in. 1 8 9

Report an error

The Integrator

The API story is an HTTP-POST interface usable from any programming language — documented for SMS sending and pitched for wiring into a website, CMS, ERP or CRM — plus an integrations page with downloadable native plugins and a set of "powered by" links that read as partner referrals rather than a maintained surface. We found no public information on webhooks, retry behaviour, rate limits, a sandbox, API versioning or a deprecation policy; for what I would have to build against this, that is thin. 1 3 8 9

Report an error

The Skeptic

The integrations page lists multiple native integrations with download buttons alongside "powered by" ones, all free of charge, and the API is documented as a simple HTTP POST callable from any programming language, with web/CMS, ERP and CRM named as targets. We found no public information on webhooks, documented rate limits, a sandbox, or a maintained integration with a major named shop platform. 8 9 1

Report an error

European sovereignty panel opinion

Show reasoning
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 CRM Manager

The contracting name carries a Spanish corporate form, Acumbamail SL, and the GDPR page claims compliance since before the regulation became mandatory — that points European, but it is not a residency statement. I found no public information on where subscriber data is hosted, who owns the company, or any subprocessor list, and as a buyer who weighs this heavily, that silence decides the score. 5 6 9

Report an error

The Deliverability Engineer

The contracting name is published as Acumbamail SL and a GDPR page exists, but that is the whole trail: I found no public information on jurisdiction, hosting or data residency, ownership, or a subprocessor list. For a criterion this buyer weighs heavily, nothing in the chain from subscription to send is traceable on the published pages. 5 6 9

Report an error

The Data Protection Officer

The copyright line names Acumbamail SL — a Spanish-form limited company, and GDPR compliance is claimed since before it became mandatory — but that is where the trail ends. We found no public information on where subscriber data and behavioural tracking are hosted, on ownership, or on any subprocessor touching the send, so there is no published answer for where the opens and clicks live, and no basis on which I could avoid a transfer argument. 5 6 9

Report an error

The Shop Owner

The copyright line names Acumbamail SL, which reads as a Spanish company, and the GDPR page claims compliance since before the regulation became mandatory. We found no public information on where subscriber data is hosted, the contracting entity's jurisdiction, or the subprocessors in the sending chain — and for a shop sending customer data, that silence weighs heavily. 5 6

Report an error

The Integrator

The captured pages name only the trading entity, Acumbamail SL, on a Spanish-language site with GDPR statements; we found no public information on contracting jurisdiction, data residency, hosting provider, or any subprocessor list. For a buyer who weighs this heavily, an entirely unevidenced chain cannot be scored on intent. 5 6 9

Report an error

The Skeptic

The one firm datum is the contracting name, Acumbamail SL, in the site footer; we found no public information on where subscriber data or behavioural tracking is hosted, on the entity's jurisdiction, on ownership, or on a single subprocessor. The GDPR page claims compliance predating the regulation's mandatory date but says nothing about data location, so a sovereignty-minded buyer has nothing here to verify. 6 9 5

Report an error

Pricing transparency

Show reasoning
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 CRM Manager

What is publicly verifiable is a free tier of 2,000 emails per month for life, five trial SMS, and pay-per-send SMS with a tariffs page whose figures the captured pages do not show; high volume is a sales call. I found no public information on paid contact tiers, send limits, overage rates, or where automation sits in the plans, so a real invoice cannot be computed from public pages alone. 4 7 8 9

Report an error

The Deliverability Engineer

What is public sits at the edges: a free tier of 2,000 emails/month for life, pay-per-send SMS with referenced rates, non-expiring bonus packs and 5 SMS to trial. No paid contact-tier price, send limits, overage rates or VAT treatment appear on the captured pages, and high-volume pricing is a phone-call conversation — a real invoice cannot be computed from what is published. 4 8 9

Report an error

The Data Protection Officer

The figures on the captured pages are the free tier of 2,000 emails/month for life and a trial of 5 SMS, with SMS sold pay per send through bonos the vendor says never expire at the same price. We found no public information on paid contact-tier prices, send limits, overage rates, VAT treatment or the tier where automation begins, and high-volume pricing is explicitly a leave-a-phone sales conversation. 8 9

Report an error

The Shop Owner

The one public number is the free tier — "2,000 emails/month for life" — alongside a pay-per-send SMS model and high-volume pricing routed through leaving a phone number for a call. I found no public information on paid contact-tier prices, send limits, overage rates or the tier where automation begins, so I cannot compute the real invoice for my list from these pages. 5 8 9

Report an error

The Integrator

The free tier is stated exactly and repeatedly — 2,000 emails/month for life — and SMS is pay per send with a rates page referenced and five trial SMS. We found no public information on paid contact tiers, send limits beyond the free allowance, overage rates or VAT treatment, and high-volume pricing is routed to a sales call, so a real invoice is not computable from public pages alone. 4 8 9

Report an error

The Skeptic

What is public is narrow but concrete: "2,000 emails/month for life" on the free plan, five trial SMS, and pay-per-send SMS with bonus credit that carries no expiry at the same price via API as via the platform. We found no public information on paid contact tiers, send limits beyond the free plan, overage rates or VAT treatment, and high-volume pricing is routed through a sales callback — so a real invoice for a real list cannot be computed from these pages. 8 9 4

Report an error

European sovereignty — proven facts

0 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 Not determined — uncited Report an error
Data residency Not determined — uncited Report an error
Subprocessors Not determined — uncited Report an error

Questions about Acumbamail

Is Acumbamail European?

Not determined: the vendor’s pages as captured do not say where Acumbamail is based.

Where does Acumbamail store data?

Not stated on the vendor’s pages as of 20 Oct 2026.

Does Acumbamail have a free plan?

Yes. Acumbamail has a free plan, per the vendor’s page captured 20 Oct 2026.

What are the best alternatives to Acumbamail?

As of 21 Oct 2026, the panel rates Brevo (3/5), CleverReach (3/5) and Mailchimp (3/5) highest among the other 27 Email Marketing & Newsletter products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Brevo (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Acumbamail alternatives.

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 (9)

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

  1. 1 Campaigns & automation — found from sitemap acumbamail.com Checked 20 Oct 2026 Details →
  2. 2 Campaigns & automation — found from sitemap acumbamail.com Checked 20 Oct 2026 Details →
  3. 3 Deliverability infrastructure — found from sitemap acumbamail.com Checked 20 Oct 2026 Details →
  4. 4 Deliverability infrastructure — found from sitemap acumbamail.com Checked 20 Oct 2026 Details →
  5. 5 Consent, proof & tracking limits — found from sitemap acumbamail.com Checked 20 Oct 2026 Details →
  6. 6 Consent, proof & tracking limits — found from sitemap acumbamail.com Checked 20 Oct 2026 Details →
  7. 7 List ownership, import & exit — found from sitemap acumbamail.com Checked 20 Oct 2026 Details →
  8. 8 Integrations & API — found from sitemap acumbamail.com Checked 20 Oct 2026 Details →
  9. 9 Integrations & API — found from sitemap acumbamail.com Checked 20 Oct 2026 Details →