whats-best.ai
Search Sign in

Email Marketing & Newsletter

GetResponse

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 GetResponse Sp. z o.o. · www.getresponse.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 CRM Manager

Weighted verdict

Owns the lifecycle programme and measures it. Wants segmentation on real behaviour, journeys that branch, and testing that reports significance rather than a bigger number. Treats a tool that can only broadcast as a mailing list with invoicing.

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

Scored by The CRM Manager

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

Behaviour-based segmentation with dynamically updated segments, tags and scores on contact behaviour, and journeys for welcome, cart recovery and win-back with AI send-time recommendations — that is genuine lifecycle work, and purchase-history segmentation on Shopify data is documented. What holds it back is the measurement layer: A/B testing is documented for landing pages and signup forms, and I found no public information on email subject-line testing that reports significance, on branching journeys, or on holdout groups. 1 4 8 11

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

Dedicated IP addresses on MAX, documented standard and assisted warm-up with an automatic send threshold, list-hygiene tooling that processes undeliverable addresses, and a Deliverability Team working with mailbox providers and blocklist operators — operational substance, not just the advertised 99% figure. But the foundation is undocumented: I found no public information on SPF, DKIM or DMARC setup, custom sending domains, or complaint-loop handling, and the strongest material sits on the MAX pages. 1 5 6

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

Import is well covered — file upload, manual copy-paste and nearly twenty sources, with names, emails and custom fields arriving intact, plus a documented API and CRM sync for keeping contacts current elsewhere. The exit side is thin: portability is documented only as personal data delivered in.CSV format, and I found no public information on exporting engagement history, unsubscribe state, campaigns or templates, or on documented deletion of a subscriber across all records. 8 11 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 CRM Manager

A maintained directory of 150-plus integrations with CRM, ecommerce and analytics categories, a deep Shopify connection importing customers, product catalog, orders and abandoned checkouts, and an advanced API for building your own integration with a partner programme behind it. I found no public information on webhooks, retries, documented rate limits or a sandbox — the difference between a broad catalogue and one I can build a lifecycle programme on. 1 10 11

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

The contracting entity is GetResponse S.A., a Polish joint-stock company in Gdansk, with a designated Data Protection Officer, GDPR compliance certified by Bureau Veritas, and the one named non-EEA processor — Google LLC in the USA — carrying Data Privacy Framework membership and standard contractual clauses. Weighing this as heavily as I do: the policy itself says transfers outside the EEA are possible for chat, SMS, analytics, marketing, sales and CRM functionality, and I found no public information on where subscriber data is hosted, on a named data-centre provider, or on a complete published subprocessor list. 2 9

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

A free tier with a 500-contact cap and named features is public, and marketing automation and segmentation are listed in the paid plans with the lowest plan starting at $13.30 /mo — though a captured page gives the Basic plan entry as 19 USD per month, so the pages give different figures for the entry price. I cannot compute a real invoice from what is published: no contact-tier ladder for larger lists, no overage rates, no VAT treatment, and the MAX2 plan is custom pricing. 9 4 7

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

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.

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

Sources (11)

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

  1. 1 Vendor page www.getresponse.com Checked 22 Sep 2026 Details →
  2. 2 Legal notice — found from the homepage www.getresponse.com Checked 30 Sep 2026 Details →
  3. 3 Campaigns & automation — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
  4. 4 Campaigns & automation — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
  5. 5 Deliverability infrastructure — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
  6. 6 Deliverability infrastructure — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
  7. 7 Consent, proof & tracking limits — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
  8. 8 List ownership, import & exit — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
  9. 9 List ownership, import & exit — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
  10. 10 Integrations & API — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
  11. 11 Integrations & API — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →