Omnisend

The CRM Manager

The automation editor is a real journey builder — conditional splits, exit conditions, lifecycle stages, frequency capping, custom-event triggers and email/SMS/push paths in one flow — and behavioural segmentation plus AI send-time picking are documented, with pre-built cart abandonment, browse abandonment and win-back flows showing lifecycle thinking. What I found no public information on is testing that reports statistical significance: the A/B copy stops at which channel, incentive or subject line "drives you most conversions", and holdout groups go unmentioned, so it falls short of the highest level. 1 3 4 12

Report an error

The Deliverability Engineer

The automation editor is documented in depth — conditional splits, channel branching across email, SMS and push, event-based triggers including custom events, and AI send-time optimisation — which is real journey building rather than a welcome mail. A/B testing of channel, incentive and subject line is stated, but we found no public information on whether results are reported with statistical significance, and no holdout groups for measurement. 3 4 1 12

Report an error

The Data Protection Officer

A no-code drag-and-drop editor with conditional splits, channel branching, exit conditions and entry on shopping, browsing, form or custom events is a genuine journey builder, and send-time optimisation plus per-message reports in the editor go beyond the middle of the scale. We found no public information on holdout groups or significance reporting for tests, which is what the top of this criterion turns on. 3 4 1

Report an error

The Shop Owner

This is built for a shop like mine: real-time triggers on browsing, cart activity and orders, conditional and channel splits, exit conditions, frequency capping and a product recommender block, with abandoned-cart, order-confirmation, shipping and cross-sell workflows named on the page, plus send-time optimisation from the AI assistant. Custom events can trigger automation workflows through the API, which is the event-driven entry I need from my shop systems. I found no public information on testing that reports statistical significance, on holdout groups for measurement, or on dynamic content variants per segment beyond the recommender. 1 3 4 12

Report an error

The Integrator

The no-code editor documents conditional splits, channel branching, exit conditions, event-based triggers including custom events, and send-time optimisation via the AI assistant, with per-segment product recommendations on top — that is a real journey builder. We found no public information on holdout groups or testing that reports significance rather than raw counts, which is what separates this from the top of the scale. 3 4

Report an error

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

Authentication is documented properly — SPF, DKIM and DMARC all required valid before a domain can send, in-app SPF error diagnosis, subdomain signing — alongside a dedicated-IP recommendation with a 2–4 week warm-up schedule and genuinely useful hygiene guidance like the 6–12 month engagement window and keeping complaints under 0.1%. The captured pages are silent, though, on hard-bounce suppression, complaint-loop handling and seed or inbox-placement testing, and those operational pieces are what separate good documentation from operated deliverability. 5 6

Report an error

The Deliverability Engineer

Authentication is taken seriously: SPF, DKIM and DMARC are documented with per-provider DNS tutorials, domain verification fails if any record is invalid, and in-app SPF error diagnostics are described. Dedicated IPs with a documented 2–4 week warm-up and published list-hygiene guidance on engaged-only sending put this past the middle band, but we found no public information on automatic hard-bounce suppression, complaint-loop handling, or seed and inbox-placement testing — the rates on the deliverability pages are averages, not policy. 5 6

Report an error

The Data Protection Officer

SPF, DKIM and DMARC are documented with free domain signing, in-app SPF error guidance, dedicated IP options with a two-to-four-week warm-up schedule, and published hygiene guidance on engaged-contact windows and complaint rates. We found no public information on automatic hard-bounce suppression, complaint-loop handling or inbox-placement testing, which is what the higher rungs of this criterion require. 5 6

Report an error

The Shop Owner

Authentication is documented thoroughly and enforced — signing a domain adds SPF, DKIM and DMARC records, the domain cannot be verified while any of them is invalid, and a verified sender address is required before any campaign or automation mail goes out; dedicated IPs are covered for high-volume senders with a 2–4 week warm-up, alongside published guidance on list hygiene, a 6–12 month engagement window and a complaint ceiling. That enforcement before the first send is a serious practice. I found no public information on automatic hard-bounce suppression, complaint-loop handling, or seed and inbox-placement testing. 5 6

Report an error

The Integrator

SPF, DKIM and DMARC setup is documented with a custom sending domain, in-app SPF error guidance, subdomain signing, dedicated-IP guidance for senders of 300,000+ emails per week, and a written 2–4 week warm-up plus list-hygiene best practice. We found no public information on automatic hard-bounce suppression, complaint-loop handling or inbox-placement testing, so the operational middle of the scale rests only on benchmarks and advice. 5 6

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

Double opt-in stores a consent record with a source value, consent segments can drive campaigns and workflows, and opt-in/opt-out dates survive export — better than a bare timestamp. But double opt-in is optional rather than the default, and it never reaches subscribers collected through Shopify checkout, WooCommerce or third-party forms, which for an e-commerce tool is exactly where risky consent concentrates. We found no public information on one-click unsubscribe handling, tracking that can be limited or switched off, or preference-centre granularity. 7 8 10

Report an error

The Deliverability Engineer

Consent is stored with its source and opt-in and opt-out dates, visible per contact and filterable by GDPR or TCPA type, which is more than a bare timestamp. But double opt-in is optional rather than the default and only works for Omnisend's own signup forms — subscribers from Shopify checkout or third-party forms receive no confirmation mail. We found no public information on unsubscribe mechanics, per-campaign tracking switches, or retention rules for inactive subscribers. 7 8 10

Report an error

The Data Protection Officer

Double opt-in is optional and configured per form rather than a documented default, applies to email only, and subscribers collected through Shopify checkout or third-party forms will not receive a confirmation email at all; the consent record does store a source visible in the contact profile, and re-consent for existing contacts is possible. We found no public information on turning open or click tracking off, pixel-free sending, or how access and erasure requests are handled, so the burden of proof rests on less than the captured pages show. 7 8

Report an error

The Shop Owner

Double opt-in is optional and per-form, and it reaches only the vendor's own signup forms — the page states subscribers collected through Shopify checkout, WooCommerce or third-party forms will not receive a confirmation email, which is precisely where my shop's signups happen. What is stored is genuinely useful for proof: a consent record per contact with its source (form:popup, shopify:checkout and the like) and opt-in and opt-out dates in the export. I found no public information on unsubscribe mechanics such as one-click handling, on switching open and click tracking off, or on preference-centre granularity. 7 8

Report an error

The Integrator

Double opt-in is documented as optional rather than the default and only works for the vendor's own signup forms — subscribers from Shopify checkout, WooCommerce or third-party forms get no confirmation email — though a consent record with source is visible per contact and re-consent via a landing page form is possible. We found no public information on one-click unsubscribe mechanics, or on limiting and switching off open and click tracking. 7 8

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

Import is well designed — opt-in and opt-out dates map as default properties, duplicates update rather than duplicate, and export carries subscription status, consent, custom properties, tags and even total spent. But the export surface is contacts-only: engagement history, campaigns and templates have no documented way out, scheduled exports are not supported, and documented deletion appears only contractually at end of service with a certificate. The free five-day migration that rebuilds flows is help arriving, not an exit path. 2 9 10

Report an error

The Deliverability Engineer

Subscriber export is genuinely full — custom properties, subscription status, consent and opt-out dates, tags and segments in CSV — and the API's contacts scope allows syncing elsewhere; the processing agreement additionally promises deletion or return of all data with certification at contract end. We found no public information on exporting engagement history, campaigns or templates, and scheduled exports are not supported; inbound migration is free and documented, but exit is a manual export rather than a feature. 10 12 2 9

Report an error

The Data Protection Officer

CSV export covers the full contact record including consent, opt-in and opt-out dates, tags, segments and custom properties, with four export routes, and the processing agreement promises deletion with a certificate or full return at the end of the service. We found no public information on exporting engagement history per campaign, or campaigns and templates out of the account, and deletion is addressed only at contract end rather than documented per subscriber. 9 10 2 1

Report an error

The Shop Owner

Export is documented in detail — CSV of all contacts or by segment and tag, with custom properties in multiple columns, consent and opt-out dates and total spent — and import handles duplicates with explicit update rules; the processing agreement commits, at the end of the service, to return my data or delete it and certify the deletion, which is exit evidenced rather than promised, and free migration of lists, flows and templates in five days is real inbound help. I found no public information on exporting engagement history or campaigns and templates, and scheduled or automated exports are stated as not currently supported. 1 2 9 10

Report an error

The Integrator

CSV export covers subscription status, consent and opt-in/out dates, custom properties, tags and total spent, import handles up to 200 properties with clear duplicate rules, the contacts API scope supports syncing elsewhere, and the DPA promises deletion with a certificate at end of service. We found no public information on exporting engagement history, campaigns or templates, and the help centre states scheduled or automated exports are not supported. 9 10 2

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

Named native platforms include Shopify, BigCommerce, WooCommerce and Wix, and the API key model is unusually strong — scoped permissions across campaigns, contacts, orders, products, carts and events, unlimited keys, revocation, and setup wizards for recognised apps. But the captured pages give me no webhooks, no documented rate limits, no sandbox and no versioning or deprecation policy, and "280+ integrations" is a count I cannot inspect rather than a maintained surface I can rely on. 1 11 12

Report an error

The Deliverability Engineer

The native surface is broad — Shopify and seven other commerce platforms plus a claimed 280-plus integrations — and API keys are scoped, revocable and unlimited, with write access to contacts, orders, products, carts and events that can trigger automation workflows. But we found no public information on webhooks for subscriber events, documented rate limits, or a sandbox, and no CRM is named among the integrations. 1 12 11

Report an error

The Data Protection Officer

Eight named commerce platforms including Shopify, 280-plus integrations, and scoped API keys covering contacts, orders, products, carts and custom events in and out give a real build surface without a partner agreement. We found no public information on webhooks, documented rate limits or a sandbox, which a buyer building against this would need documented. 1 12 11

Report an error

The Shop Owner

The connection surface I care about is named: Shopify, Shopify Plus, BigCommerce, WooCommerce, Wix and more among 280+ integrations, with API key scopes covering Orders, Products, Carts and Events — creating, editing, downloading, deleting — and custom events able to trigger automation workflows; recognised apps get a setup wizard and keys can be scoped per integration. I found no public information on webhooks, documented rate limits, a sandbox environment, or an API versioning and deprecation policy, which is what the upper end of this criterion rests on. 1 11 12

Report an error

The Integrator

There is a documented API-key system with composable permission scopes — campaigns, contacts, orders, products, carts, and triggering custom events for automation workflows — plus native integrations for every major shop platform including Shopify. We found no public information on webhooks and retry behaviour, documented rate limits, a sandbox or a deprecation policy, and the Zapier path reads to me as outsourcing the long tail of connections. 1 11 12

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

A Lithuanian entity with a Vilnius address and incorporated Controller-to-Processor standard clauses are real, but the DPA describes a group that also includes a London company and a Charleston, South Carolina company without stating which entity contracts with a given customer, and the subprocessor names themselves did not appear in what was captured — only their purposes. We found no public information on hosting location, data residency or ownership, and for a buyer who weighs this heavily, standard clauses as the only stated safeguard are not something I can score kindly. 2

Report an error

The Deliverability Engineer

A Lithuanian entity is first-listed in the processing agreement, but the same agreement names a London and a Charleston, South Carolina company and does not state which one contracts with a given customer. We found no public information on where subscriber data or behavioural tracking is hosted, and while sub-processor purposes are listed, the names behind the referenced annex are absent from what we captured. Standard contractual clauses module two and a UK transfer addendum confirm non-EEA transfers are part of the chain. 2

Report an error

The Data Protection Officer

The processing agreement names a group of three companies in Vilnius, London and Charleston, South Carolina without saying which one a given customer contracts with, and hosting location is not stated anywhere we captured. The subprocessor list sits in an annex we could not see, and the presence of Standard Contractual Clauses with a UK transfer addendum signals non-EU legs this buyer would have to argue safeguards for. 2

Report an error

The Shop Owner

The captured processing agreement names a group of three companies — UAB Omnisend in Vilnius, Omnisend Limited in London and Omnisend, Inc. in Charleston, SC — and does not state which of them contracts with a given customer, though Standard Contractual Clauses module two, a UK transfer addendum and a duty to notify on public-authority requests are incorporated. Sub-processor purposes are published as collaboration, marketing and eCommerce, accounting and analytics, but the named list behind them is not in the capture. I found no public information on data residency for hosting, sending or tracking, or on ownership — for a criterion I weigh heavily, that silence is the deciding fact. 2

Report an error

The Integrator

The contracting picture is a group of three companies across Lithuania, the UK and South Carolina with no statement of which one a given customer signs with, and SCCs Module Two plus the UK addendum carry the transfers. We found no public information on data residency, ownership, or the named subprocessors behind the marketing, analytics and accounting purposes the DPA lists in its annex. 2

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

What is public is a free tier with full access and no credit card, a claim of paying "up to 35%" less than Klaviyo for comparable features, and a $79-ROI-per-dollar marketing figure — none of which lets me compute an invoice. A monthly email limit is implied by the note that confirmation emails do not count toward it, but the limit itself, contact-tier prices, overage rates and VAT treatment never appear on the captured pages. 1 3 7

Report an error

The Deliverability Engineer

The captured pages state a free tier with full access and no credit card required, that domain signing and double opt-in carry no additional cost, and a claim of paying up to 35% less than Klaviyo — but no paid tier price appears anywhere. A monthly email limit is implied by the note that confirmation emails do not count toward it, yet we found no public information on tier prices, send limits, overage rates or VAT treatment, so a buyer cannot compute an invoice from these pages. 7 1 3 5

Report an error

The Data Protection Officer

The captured pages show a free tier with full access and no credit card, and that confirmation emails do not count toward a monthly email limit, which confirms limits exist without stating them. No contact-tier price, send limit or overage rate appears, so a real invoice cannot be computed from public information. 1 3 4 7

Report an error

The Shop Owner

The captured pages carry comparison and outcome claims — 'Pay up to 35%* less' for features comparable to Klaviyo's, '$79* ROI For every $1 spent' — and a free start with full access and no credit card, but no contact-tier prices, send limits, overage rates, feature boundaries or VAT treatment appear anywhere. The only metering disclosed is that double opt-in confirmation emails come at no additional cost and do not count toward the monthly email limit, and the limit itself carries no number. I cannot compute my invoice for my list size and send volume from these pages. 1 3 7

Report an error

The Integrator

Beyond a free trial with no credit card and cost-free items like migration, domain signing and double opt-in confirmation emails, the public pages give only relative claims — up to 35% less than Klaviyo — with no contact-tier price, no send-limit figure and no overage rate. A buyer cannot compute any invoice for their list size from this. 1 3 7

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