ExpertSender

The Skeptic

The workflow builder is genuinely documented — drag-and-drop elements, predefined templates, draft saving, validation before activation, multiple connections per element — and segments update automatically on behaviour and events, with personalisation, recommendations and on-site automations around them. But A/B testing appears only as an API call to create and send a test newsletter, and I found no public information on branching on attributes, send-time optimisation, significance reporting or holdout groups, so this sits above the mid point and clearly below the top one. 1 3 10 11

Report an error

The Skeptic

Bounce handling is properly documented — categorised reasons, grouping by domain, message, list and IP address, CSV export of bounced addresses, automatic removal of hard bounces after each send, and re-sending to soft-bounce subscribers — which is the strongest half of this picture. The authentication half is missing: I found no public information on SPF, DKIM or DMARC setup, custom sending domains, dedicated-IP options or complaint-loop handling, so the score lands between the documented-bounce and fully-documented-authentication marks. 4 5

Report an error

The Skeptic

Consent infrastructure is real and visible — consent types linked to channels, consents that can be marked required by default, confirmation messages for actions like newsletter subscription, exportable consent flags, and a preference centre claimed as a capability. What I cannot see is the proof: I found no public information on double opt-in as a documented default, on what a stored consent record contains (source, wording, IP), or on one-click unsubscribe, and tracking preferences are documented for confirmation messages only. 1 6 8

Report an error

The Skeptic

Import maps CSV, TXT, Excel and ZIP files onto system and custom attributes with duplicate handling and matching modes, export covers system attributes, custom attributes and consents from the interface or from a segment, and the API exports raw engagement events — sends, opens, clicks, unsubscribes, orders — as CSV, so engagement history can leave the platform. I found no public information on deleting a subscriber across all records or on exporting campaigns and templates, and the migration service is documented as inbound, with nothing on exit; the engagement export is also capped at 90-day windows. 1 8 9

Report an error

The Skeptic

Six named e-commerce integrations including Shopify, Magento and WooCommerce, a documented REST API with keys, Swagger pages and API-key management, and the API is write-capable — it creates and sends newsletters and A/B tests, not just reads. I found no public information on webhooks for subscriber events, documented rate limits or a sandbox, which keeps this at the solid mid mark rather than higher despite the breadth. 1 9 10 11

Report an error

The Skeptic

No sovereignty attributes are on record: I found no public information on where subscriber data or the sending infrastructure are hosted, on the contracting entity's jurisdiction, or on any subprocessor list. The European-style company suffix and an API host with no stated location are not evidence of EU processing, and for a buyer who weighs this heavily, silence on hosting, entity and subprocessors is itself the information. 1 9 10

Report an error

The Skeptic

No price appears on any captured page — no tiers, no contact prices, no send limits, no overage rates, no VAT treatment. The only commercial datum anywhere is a qualification line that the buyer gets at least 30,000 unique visits per month, which reads as the entrance to a sales conversation, so a sender cannot compute any invoice from public pages. 1

Report an error