whats-best.ai

Email Marketing & Newsletter

Dotdigital

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 4 dimensions proven

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

by Dotdigital Group plc · dotdigital.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 Shop Owner

Weighted verdict

Runs a shop where the newsletter is a revenue channel. Wants the shop connected properly — orders, carts, products flowing in, abandoned-cart and post-purchase flows out — and revenue attributed per campaign. Judges price against contribution, not against a competitor's tier.

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

Scored by The Shop Owner

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 Shop Owner

The no-code program builder runs multi-step journeys with exit conditions, and the documented abandoned-cart program is exactly the flow that earns its keep in my shop; triggered campaigns across email, SMS and MMS, welcome-on-list-join, autoresponders, A/B testing of copy, CTAs and design, and segments built from order and behaviour data are all evidenced. I found no public information on send-time optimisation, significance reporting for tests, dynamic content per segment, or holdout groups, so I stop short of the higher marks. 1 4 5 7

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 Shop Owner

SPF, DKIM and DMARC are documented in detail — default policy levels, 2048-bit keys, records provided during setup — with stated compliance to the Gmail, Yahoo and Microsoft authentication requirements, and hard bounces are suppressed automatically while persistent soft bounces are converted. A sender-reputation screen, evaluated every 30 days from opens, clicks, complaints, bounces and Data Watchdog scores, is surfaced in the account for shared-IP senders. I found no public information on dedicated-IP warm-up, seed or inbox-placement testing, or engagement-based sunsetting. 6 7

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 Shop Owner

Contacts can be exported singly, in bulk, from a list or from a program, with every contact data field in CSV and Insight data as JSON, and the CSV import path handles partial updates and field corrections — my customer attributes can leave with me, over an API documented well enough to sync elsewhere. Deletion of contacts is available through programs and manual suppression-area actions. I found no public information on exporting engagement history or past campaigns and templates, or on deletion evidenced across all records; export files are retained for 7 days and gated behind exporter permissions. 4 10 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 Shop Owner

Shopify, BigCommerce, Adobe Commerce and Shopware are named among over 200 integrations, and consent-based e-commerce linking is documented — the orders-and-carts plumbing I need. Program webhooks reach almost any RESTful API with authentication options, per-request rate limiting, reusable templates and testing against a contact, and API rate limits are published per package down to the tier, with transactional mail on SMTP or API. I found no public information on webhook retries or a sandbox, the vendor leaves request code to your own developers, and e-commerce integration runs partly through named suppliers rather than entirely in-house. 1 2 3 12 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 Shop Owner

The contracting entity is UK-registered with a Dutch subsidiary as EEA representative; EU hosting exists as an account region on named Azure and Google facilities, while the privacy policy states information may be stored and processed in any country with facilities or service providers, including the United States. A subprocessor list with names and purposes is published, transfers rest on standard contractual clauses and the Data Privacy Framework, and ISO 27001, ISO 27701 and Cyber Essentials Plus are verifiable. I weigh this heavily, and region-dependent residency with non-EU support and sales tooling keeps me at a middling mark. 2 3

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 Shop Owner

I found no public information on prices anywhere in the captured pages: no contact tiers, no send limits, no overage rates, no VAT treatment. Packages appear only as names — Email & SMS marketing and CXDP — each attached to API rate limits, and anything beyond runs through a Customer Success Manager. As a shop that has to know the invoice before committing, I have nothing to compute from. 1 12

Report an error

European sovereignty — proven facts

2 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 EU optional ⚠ unverified 1/3 pts 3 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.

Sources (13)

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

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