Omnisend

The Skeptic

The journey builder is real, not brochure-ware: conditional splits, channel branching across email, SMS and push, event-based triggers, exit conditions, lifecycle stages and a product recommender block are all documented. Send-time optimisation, though, appears only as a homepage line — "Let AI write copy, pick send times, and segment your audience" — and we found no public information on testing that reports statistical significance rather than raw conversion claims. 1 3 4

Report an error

The Skeptic

Authentication documentation is unusually concrete — SPF, DKIM and DMARC with subdomain inheritance, the SPF 10-lookup limit, in-app SPF error guidance, a documented 2–4 week warm-up and dedicated-IP advice for 300,000+ weekly senders. But the bounce and complaint figures are given as averages ("~0.3%", "~0.03%") rather than a stated handling policy, and we found no public information on automatic hard-bounce suppression, complaint-loop handling or inbox-placement testing. 5 6

Report an error

The Skeptic

The consent record is better than a bare timestamp — it stores source and opt-in/opt-out dates, is visible per contact, and consent segments can gate campaigns and workflows — but double opt-in is optional and per-form rather than the default, and subscribers collected through Shopify checkout, WooCommerce or third-party forms never receive a confirmation email. We found no public information on whether open and click tracking can be limited or switched off, or on handling of access and erasure requests. 7 8

Report an error

The Skeptic

Contact export is a full CSV — custom properties in multiple columns, consent, opt-in and opt-out dates, tags and segments — and import handles duplicates with four update options, so attributes survive the trip in both directions. The exported-fields list stops at contacts, though: we found no public information on exporting engagement history, campaigns or templates, scheduled exports are explicitly not supported, and the delete-and-certify clause sits at contract end in the processing agreement rather than as a documented per-subscriber execution. 2 9 10

Report an error

The Skeptic

Shopify, Shopify Plus, BigCommerce, WordPress, WooCommerce, Wix, Shoplazza and Ecwid are named, and the API key system is genuinely granular — six permission scopes, unlimited keys, custom combinations, revocation — with custom events flowing into automation workflows, which is well past a read-mostly surface. What we found no public information on is webhooks, documented rate limits, or a sandbox, which is exactly what separates a competent API from a dependable one. 1 11 12

Report an error

The Skeptic

The processing agreement describes a group of three companies — UAB Omnisend in Vilnius, Omnisend Limited in London, Omnisend, Inc. in Charleston — and does not say which entity contracts with a given customer, while Standard Contractual Clauses module two plus a UK transfer addendum signal that data leaves the EU by design. We found no public information on hosting location, ownership, or a named subprocessor list; the agreement references an annex of purposes (communication, eCommerce, accounting, analytics) but the captured documents name no subprocessors. 2

Report an error

The Skeptic

A free tier with no credit card and free five-day migration are public, but beyond that the money pages are comparative fog: "Pay up to 35%* less" against an unstated Klaviyo baseline and a "$79* ROI for every $1 spent" claim stand in for actual figures. We found no public information on paid-tier prices, contact tiers, send limits beyond the passing mention of a "monthly email limit", or overage rates — nothing a buyer could compute an invoice from. 1 7

Report an error