whats-best.ai
Search Sign in

Email Marketing & Newsletter

Sender

Provenance unknown 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 SIA Sender · www.sender.net

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 drag-and-drop journey builder documents triggers, actions and If/Else conditions across eleven trigger types plus custom events fired via API or Zapier — event-driven entry is exactly what I need — and testing reports statistical significance rather than raw counts, with workflow split testing and send-time testing alongside it. We found no public information on holdout groups or measurement isolation for journeys, which is what separates this from the top of the range. 4 5 3

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, DKIM and DMARC are documented down to exact record values with a verification recheck button, hard bounces are suppressed automatically, soft bounces retried with suppression after persistence, and purchased or scraped lists are screened before sending. We found no public information on complaint-loop handling, dedicated IP options with warm-up, seed or inbox-placement testing, or engagement-based sunsetting — and the "up to 99% deliverability" figure is a marketing number I can't build against. 6 7 3 1

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 takes CSV, Excel and TXT with custom fields and templates, and export covers contact data, email and SMS subscription status, group assignments, custom fields and registration and activity dates in CSV or xlsx, filterable by status, group and segment; profile deletion carries a clean audit record. We found no public information on exporting per-campaign engagement history, campaigns or templates, and no statement either way on export throttling. 10 11 3

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

The webhook layer is genuinely buildable — eight topics including bounces, HMAC signing with rotatable secrets, pause, failure counters and response-time monitoring — beside a bearer-authenticated API with code examples, custom events feeding automation triggers, and named shop integrations including WooCommerce, Shopify and PrestaShop. But retries are described only as "may retry" on timeout rather than a delivery policy with a schedule, and we found no public information on documented rate limits, a sandbox, or an API deprecation policy — the difference between a stack component and a connector list. 13 12 4 5

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 contracting party is named as UAB Sender.lt with a DPA under GDPR Article 28 and a designated DPO, and EU hosting is claimed as default on every plan including the free tier — but that claim appears only in marketing copy, and the privacy policy names no server location or hosting provider. The subprocessor picture is incomplete: Google reCAPTCHA and Cloudflare Turnstile are named with no legal basis, and a third-party web analytics partner is explicitly placed outside the privacy policy; we found no public information on the data-centre provider or the jurisdiction of the contracting entity. 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 Integrator

The only public numbers are the free plan — no credit card required, cancel anytime, automate up to 15,000 emails/month — plus a "no hidden costs or usage limits" claim that is positioning, not a price. We found no public information on paid tier prices, contact tiers, billing periods, overage rates or VAT treatment, so a real invoice for a given list size cannot be computed from public pages. 4 1 3

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 Not determined — uncited Report an error
Data residency EU only ⚠ unverified 3/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.

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

Sources (13)

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

  1. 1 Vendor page www.sender.net Checked 29 Sep 2026 Details →
  2. 2 Privacy policy — found from the homepage www.sender.net Checked 30 Sep 2026 Details →
  3. 3 Data processing agreement (dpa) — found from the homepage www.sender.net Checked 30 Sep 2026 Details →
  4. 4 Campaigns & automation — found from sitemap www.sender.net Checked 30 Sep 2026 Details →
  5. 5 Campaigns & automation — found from sitemap www.sender.net Checked 30 Sep 2026 Details →
  6. 6 Deliverability infrastructure — found from sitemap www.sender.net Checked 30 Sep 2026 Details →
  7. 7 Deliverability infrastructure — found from sitemap www.sender.net Checked 30 Sep 2026 Details →
  8. 8 Consent, proof & tracking limits — found from sitemap www.sender.net Checked 30 Sep 2026 Details →
  9. 9 Consent, proof & tracking limits — found from sitemap www.sender.net Checked 30 Sep 2026 Details →
  10. 10 List ownership, import & exit — found from sitemap www.sender.net Checked 30 Sep 2026 Details →
  11. 11 List ownership, import & exit — found from sitemap www.sender.net Checked 30 Sep 2026 Details →
  12. 12 Integrations & API — found from sitemap www.sender.net Checked 30 Sep 2026 Details →
  13. 13 Integrations & API — found from sitemap www.sender.net Checked 30 Sep 2026 Details →