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