Omnisend
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Omnisend, UAB · www.omnisend.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Omnisend at a glance
- Vendor
- Omnisend, UAB
- Headquarters
- Incorporated in Lithuania source, captured 2 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 26 Oct 2026
- Panel verdict
- The AI panel rates Omnisend 2.5/5, the mean of 6 judges. Omnisend is an email marketing and newsletter tool for ecommerce shops, and its highest scores land on campaign and automation, 7 to 8: a drag-and-drop editor with conditional splits, branching across email, SMS and web push, triggers from shopping, browsing and custom events, and AI send-time picking. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Omnisend is an email marketing and newsletter tool for ecommerce shops, and its highest scores land on campaign and automation, 7 to 8: a drag-and-drop editor with conditional splits, branching across email, SMS and web push, triggers from shopping, browsing and custom events, and AI send-time picking. Deliverability clusters at 6 on enforced SPF, DKIM and DMARC validation and a two-to-four-week warm-up. Judges genuinely split below that. Integrations span 5 to 7 — shop-facing judges credit native Shopify, BigCommerce and WooCommerce sync and 335+ integrations; technical judges found no public information on webhooks, rate limits or a sandbox. List data control spans 5 to 7, with strong import and contact export but no public information on exporting campaigns, templates or engagement history. Consent and proof spans 4 to 5: some credit the consent record; others weigh that double opt-in is optional, misses checkout-collected contacts, and sending is not restricted on consent alone. Sovereignty and pricing transparency sit at 3: hosting and data residency are unstated and no tier price is public beyond a claim of up to 35% less than Klaviyo.
Speaks for it
- Drag-and-drop automation editor with conditional splits, channel branching across email, SMS and web push, and triggers from shopping, browsing and custom events
- Sending domains cannot be verified unless SPF, DKIM and DMARC are all valid, with warm-up guidance of two to four weeks
- Contact import with field mapping and duplicate-handling options, CSV export carrying consent dates and custom properties, and API contact read, write and delete
- Native integrations with Shopify, Shopify Plus, BigCommerce, WooCommerce, Wix and others, plus 335+ integrations and scoped, revocable API keys
- Free start with full access, no credit card required, and a free five-day migration of lists, flows and templates
Held against it
- We found no public information on paid tier prices, contact-band scaling or overage rates — the only pricing signal is a claim of up to 35% less than Klaviyo
- The published data processing agreement names companies in Lithuania, England and the United States without saying which one contracts with the customer, and hosting location and data residency are unstated
- Double opt-in is optional and limited to Omnisend's own forms, checkout-collected contacts receive no GDPR consent record, and sending is not restricted based on consent alone
- We found no public information on webhook retries, documented rate limits or a sandbox, nor on significance reporting or holdout groups for A/B tests
- Scheduled or automated exports are not supported, and we found no public information on exporting engagement history, campaigns or templates
Best for
- You run a store on Shopify, BigCommerce or WooCommerce and want cart abandonment, product abandonment, order and shipping confirmation workflows in a no-code editor
- You are moving from Klaviyo or Mailchimp and want a free five-day migration of lists, flows and templates
- You want a portable contact list — field-mapped import, CSV export carrying consent dates and custom properties, and API-based contact deletion
- You sell on several shop platforms and rely on continuous store sync of orders, cart activity and account registrations
Avoid if
- You need to compute the invoice for your list size before committing — the only public pricing is a free start and a claim of up to 35% less than Klaviyo
- Your procurement needs a single named contracting entity and stated data residency — the agreement names companies in Lithuania, England and the United States without saying which one contracts with the customer
- Your compliance programme requires the platform to enforce consent before sending — Omnisend states that sending is not restricted based on consent alone
- You are building load-bearing integrations that need documented webhooks, rate limits or a sandbox — we found no public information on these
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 4 of 5 |
| Deliverability infrastructure | 3 of 5 |
| Consent, proof & tracking limits | 2 of 5 |
| List ownership, import & exit | 3 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 1.5 of 5 |
Campaigns & automation
Show reasoningHide reasoning
How this is scored
Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.
0 — Not a campaign tool; mail cannot be composed and sent to a list from the product.
3 — Broadcasts to a list built in an editor with templates, with simple list or tag segmentation; automation and testing are basic or not described.
5 — A drag-and-drop editor with reusable templates, segmentation on subscriber fields or behaviour, automated sequences on common triggers (sign-up, date, click), and A/B testing of campaigns.
8 — A visual journey builder with branching on behaviour and data, dynamic content per segment, send-time optimisation, event triggers from shop or app data, 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.
The CRM Manager
This is a real journey builder, not a broadcaster: a drag-and-drop automation editor with conditional splits and channel branching on shopping, browsing and custom-event triggers, behavioural segmentation, exit conditions, frequency capping and AI send-time picking, plus lifecycle templates like cart abandonment and win-back. What holds it back for me is the testing story — A/B tests of channel, incentive and subject line are documented, but we found no public information on significance reporting or holdout groups for measurement. 4 4 3 4
The Deliverability Engineer
A no-code, drag-and-drop automation builder with conditional and channel splits, triggers off shopping and browsing activity and custom events, behavioural segmentation and AI-picked send times is documented, with pre-built ecommerce workflows from welcome to shipping confirmation. Testing is described for channel, incentive and subject line, but we found no public information on significance reporting or holdout groups. 4 3 4
The Data Protection Officer
The drag-and-drop automation editor with conditional splits, channel branching, exit conditions and behavioural triggers from shopping, browsing and custom events is genuine journey-builder territory, and AI send-time picking plus per-message reports go beyond the basics. I found no public information on significance reporting for A/B tests or on holdout groups, so I stop short of the top of this band. 4 1 3 4
The Shop Owner
This is the shop-flows story I actually run: triggers off shopping and browsing activity plus custom events, cart abandonment, product abandonment, order and shipping confirmation, cross-sell, conditional splits, channel branching across email, SMS and push, and per-message sales reporting inside the drag-and-drop editor. AI picking send times and personalised product recommendations lift it further; the only gap is that testing is described as channel, incentive or subject-line splits with engagement reporting, and I found no public information on significance reporting or holdout groups for measurement. 3 4 4 1 1
The Integrator
The automation side is genuinely strong: a drag-and-drop editor with conditional splits, channel branching and exit conditions, triggers off shopping and browsing activity plus custom events, and AI-picked send times — a real journey builder my team could feed store events into. The captured pages stop short of showing A/B testing that reports significance, and the broadcast email editor itself is only lightly evidenced, so I settle just under the top band. 3 4 4 1
The Skeptic
The drag-and-drop automation editor is documented in real detail: conditional splits, channel branching, triggers on shopping activity, browsing activity, segment entry/exit and custom events, AI send-time picking, and A/B testing of subject line, channel or incentive inside workflows. We found no public information on whether tests report statistical significance, so this sits at the journey-builder level rather than above it. 4 3 4 1
Deliverability infrastructure
Show reasoningHide reasoning
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 — The product does not send mail itself; delivery runs through the customer's own mail server with no sending infrastructure provided.
3 — Sending through the vendor's infrastructure with SPF and DKIM set-up for the sender's domain documented; bounce handling and reputation measures are basic or not described.
5 — SPF, DKIM and DMARC guidance with an authenticated custom sending domain, automatic suppression of hard bounces and complaints, and help-centre guidance on deliverability and list hygiene.
8 — Dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, complaint feedback loops stated, and reputation reporting per sending domain.
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.
The CRM Manager
Authentication is taken seriously: a sending domain cannot be verified unless SPF, DKIM and DMARC are all valid, with in-app SPF error guidance, DNS provider tutorials and advice on subdomain separation, alongside help-centre guidance on warm-up over 2–4 weeks, keeping the complaint rate below 0.1% and sending only to contacts engaged in the last 6–12 months. We found no public information on automatic bounce suppression, complaint feedback loops, inbox-placement testing or per-domain reputation reporting, which is what separates guidance from an operated service. 5 6 5
The Deliverability Engineer
Authentication is documented properly and enforced at verification: SPF, DKIM and DMARC records must all be valid before a domain can send, with in-app SPF error guidance, the 10-lookup limit, subdomain signing for automations and a written 2–4 week warm-up. What holds it down: we found no public information on automatic hard-bounce suppression, complaint feedback loops, seed or inbox-placement testing, or per-domain reputation reporting, and engagement-based sunsetting appears only as advice to mail contacts active in the last 6–12 months. The published benchmark bounce and complaint rates I disregard on principle. 5 6 5
The Data Protection Officer
Domain signing enforces valid SPF, DKIM and DMARC before a domain may send, a verified sender address is required, and the help centre documents warm-up pacing over two to four weeks, a dedicated-IP threshold of roughly 300,000 emails per week and a 0.1 percent complaint ceiling — real substance. I found no public information on automatic suppression of hard bounces, complaint feedback loops, seed or inbox-placement testing, or per-domain reputation reporting, which is what the next band demands. 5 6 5
The Shop Owner
Authentication is documented in real depth — SPF, DKIM and DMARC added when signing the domain, in-app SPF error guidance, subdomain signing, dedicated IPs recommended above 300,000 emails a week with a two-to-four-week warm-up, and clear hygiene guidance on keeping complaints low and mailing only contacts engaged in the last six to twelve months. The operational side is thinner: I found no public information on automatic bounce and complaint suppression, feedback loops, or reputation reporting per sending domain. 6 5 5
The Integrator
Domain signing enforces SPF, DKIM and DMARC validity before a domain can send, with in-app SPF error guidance, a documented warm-up of two to four weeks and dedicated-IP guidance for senders above 300,000 emails a week — more than checklist level. But I found no public information on seed or inbox-placement testing, complaint feedback loops, or per-domain reputation reporting, which is what I would want before trusting the pipe. 5 6 5
The Skeptic
Domain signing with SPF, DKIM and DMARC must be valid before a domain can be used for sending, and the help centre covers warm-up over two to four weeks, dedicated IPs for senders above roughly 300,000 emails per week, complaint-rate limits and sunsetting to engaged contacts. We found no public information on automatic hard-bounce suppression, complaint feedback loops, inbox-placement testing, or reputation reporting per sending domain. 5 5 6
Consent, proof & tracking limits
Show reasoningHide reasoning
How this is scored
How subscribers arrive and what the sender can prove afterwards: double opt-in, logged consent, unsubscribe handling, and whether open and click tracking can be limited or switched off.
0 — Not built for consent at all: the vendor describes the list as imported addresses, with no sign-up forms and no opt-in confirmation in the product.
3 — Sign-up forms, double opt-in available and an unsubscribe link in every mail; the consent record and tracking controls are basic or not described.
5 — Double opt-in documented with a consent record per subscriber (timestamp and source), one-click unsubscribe, and open or click tracking that can be switched off.
8 — Consent is reproducible as evidence: double opt-in as the default, the confirmation mail and form wording stored per subscriber with IP, unsubscribe honoured across lists, a preference centre, tracking off by default available, and retention rules for inactive subscribers.
10 — Built for the burden of proof: a per-subscriber consent history an authority would accept, documented handling of Art. 15 access and Art. 17 erasure requests, pixel-free and link-tracking-free sending as a supported mode, and preference-centre granularity rather than all-or-nothing.
The CRM Manager
Double opt-in is free, configurable per form, stores a consent record with the source visible in the contact profile, and opt-in and opt-out dates travel with every export, deliberately separated from subscription status for GDPR and TCPA. But it is optional rather than default, it only works on Omnisend's own signup forms — subscribers collected at Shopify checkout or through third-party forms get no confirmation mail — and the pages state that Omnisend will not restrict sending based on consent alone; we found no public information on switching off open or click tracking, or on a preference centre. 7 8 10
The Deliverability Engineer
Double opt-in is configurable per form, stores a consent record with source, creates no contact profile until the confirmation link is clicked, and the record is inspectable per contact with opt-in and opt-out dates carried into exports — more than a checkbox. It stops short of the next level: opt-in is off by default, checkout-collected addresses get no GDPR consent record, the vendor itself states sending is not restricted on consent alone, and we found no public information on one-click unsubscribe, a preference centre, or open and click tracking that can be switched off. 7 8 10
The Data Protection Officer
Double opt-in exists at no cost, creates no contact profile until the confirmation link is clicked, and leaves a consent record with its source kept separate from subscription status — a fair start on proof. But it is optional rather than default, does not reach subscribers collected through Shopify checkout or third-party forms, sending is not restricted on consent alone, and I found no public information on an IP-captured consent history, a preference centre, or any way to switch open and click tracking off. 7 8 1
The Shop Owner
Double opt-in is optional, off by default, and limited to Omnisend's own forms — contacts from Shopify checkout or third-party forms get no confirmation email — though consent itself is logged per subscriber with source and opt-in and opt-out dates, visible in the contact profile and exportable, with GDPR and TCPA records kept separate. Sending is not restricted by consent, so I must build the exclusion segments myself, and I found no public information on one-click unsubscribe, a preference centre, or any way to switch open and click tracking off. 7 8 6
The Integrator
Double opt-in is documented in depth — optional per form, a 30-day confirmation expiry, no profile created until confirmation, and a consent record with named sources kept separate from subscription status and filterable by GDPR or TCPA type. It is opt-in rather than the default, the vendor states sending is not restricted on consent alone, and I found no public information on unsubscribe handling or the ability to switch open and click tracking off. 7 8
The Skeptic
Double opt-in is optional per form, and the consent record — source, opt-in and opt-out dates, kept separate from subscription status — is genuinely documented in the contact profile and in the export; the help centre also states plainly that sending is not restricted based on consent alone and that checkout-collected contacts receive no GDPR consent record. We found no public information on one-click unsubscribe handling, a preference centre, or any way to switch open and click tracking off. 7 8 10 6
List ownership, import & exit
Show reasoningHide reasoning
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 — The vendor states that the list cannot be exported; subscriber data stays inside the product.
3 — CSV import and export of subscribers with their fields; engagement history, unsubscribe state and deletion are basic or not described.
5 — Import with field mapping, subscriber export including custom fields and subscription or unsubscribe status, deletion of a subscriber on request, and an API to read and write the list.
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.
The CRM Manager
Import maps to default and custom properties with duplicate-handling options and automatic source tags, export covers consent dates, custom fields and spending data with stated durations and no sign of throttling, the API's Contacts scope includes deleting contacts, and the data processing agreement promises deletion or return of everything with certification when the contract ends. Free five-day migration of lists, flows and templates from Klaviyo, Mailchimp and others makes arrival cheap; we found no public information on exporting engagement history or campaigns and templates. 10 12 1 2 9
The Deliverability Engineer
Import maps default and custom fields with duplicate-handling options and a good/bad-email report, export runs to CSV by status, segment or tag with consent dates and custom properties included, an API reads and writes contacts, and a free vendor-run migration moves lists, flows and templates; the processing agreement promises deletion or return with a certificate at end of service. We found no public information on exporting engagement history or campaigns yourself, and scheduled exports are not supported. 9 10 12 2
The Data Protection Officer
File import with field mapping including opt-in and opt-out dates, a CSV export carrying consent status, opt-in and opt-out dates and custom properties, an API with contact read, write and delete rights, and end-of-service deletion with certification give me most of what I need. I found no public information on exporting engagement history, campaigns or templates, and the captured pages state scheduled or automated exports are not supported, so leaving is a manual and partial exercise. 9 10 12 2 9
The Shop Owner
Import is the best-documented part of the product: field mapping with up to 200 properties, four duplicate-handling choices, an import report, and CSV export filtered by status, segment or tag that carries consent dates, custom properties and total spent, plus an API contact scope that reads and writes the list. Free five-day migration of lists, flows and templates and deletion-or-return with certification at contract end go beyond the norm; I found no public information on exporting engagement history, campaigns or templates. 9 10 12 1 2
The Integrator
Import maps fields including opt-in and opt-out dates with four duplicate-handling modes, and CSV export carries consent dates, tags, segments and every custom property — the list is genuinely mine to take, with read and write plus deletion through the API's Contacts permission. Exit is weaker: no scheduled or automated exports exist, campaign and template export is not documented, and certified deletion is promised in the processing agreement at end of service rather than evidenced as a per-subscriber operation. 10 9 12 2
The Skeptic
Import has real field mapping, duplicate-handling options and ISO 8601 opt-in dates, contact export covers custom fields, consent dates and tags in CSV, the API can create, edit, download and delete contacts, and a free five-day migration of lists, flows and templates is offered on the way in. We found no public information on exporting engagement history, campaigns or templates, and the help centre states that scheduled or automated exports are not supported. 9 10 12 1
Integrations & API
Show reasoningHide reasoning
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 — A closed stand-alone tool: the vendor offers neither an API nor integrations, and the list is maintained by hand or CSV.
3 — A handful of named integrations or embeddable forms, or a basic API; webhooks and API documentation are basic or not described.
5 — Named integrations for common shop and CRM systems, a documented REST API with keys, and webhooks or connector-platform triggers for 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.
The CRM Manager
Eight native shop platforms including Shopify Plus, BigCommerce and WooCommerce, a claimed 335+ integrations, and API keys with per-scope permissions covering campaigns, contacts, orders, products, carts and custom events — enough to wire a lifecycle programme into the shop without middleware. We found no public information on event webhooks with retries, documented rate limits or a sandbox, which is what I would want before building anything load-bearing against it. 11 12 1 4
The Deliverability Engineer
Maintained native integrations with Shopify, Shopify Plus, BigCommerce, WooCommerce, Wix and others are listed alongside 335+ integrations, store sync runs continuously, and the API key system is unusually well documented — scoped keys, custom permission combinations, revocation and no key limit. We found no public information on webhook retries, documented rate limits or a sandbox, which keeps it out of the top band. 11 12 1 4
The Data Protection Officer
Native integrations with Shopify, BigCommerce, WooCommerce and the other named shop platforms, more than 335 integrations, a documented API-key system with per-scope permissions and unlimited revocable keys, and Zapier connectivity form a solid surface. I found no public information on event webhooks with retries, documented rate limits, or a sandbox, which keeps this below the maintained-bidirectional band. 11 12 1 4
The Shop Owner
Every shop platform I sell on is named — Shopify, Shopify Plus, BigCommerce, WooCommerce, Wix — with continuous store sync of orders, cart activity and account registrations, 335+ integrations, a developer centre, and API keys scoped to campaigns, contacts, orders, products, carts and events that I can mix per key. Webhooks with retries, documented rate limits and a sandbox are what would take it further, and I found no public information on those. 4 12 1 9 11
The Integrator
API keys are handled properly — multiple keys with custom permission combinations across Contacts, Orders, Products, Carts and Events, view-once with revocation — alongside native Shopify, BigCommerce and WooCommerce integrations, a developer centre and an API documentation collection. But the captured pages give me no webhooks, no retries, no documented rate limits, no sandbox and no deprecation policy, and Zapier is named as the route for anything outside the native library, which I read as outsourced connectivity. 12 1 4 11
The Skeptic
Native integrations cover Shopify, Shopify Plus, BigCommerce, WooCommerce and more, a catalogue of 335+ integrations is advertised, and scoped API keys reach campaigns, contacts, orders, products, carts and events, with no limit on key count and revocation supported. We found no public information on webhook retries, documented rate limits or a sandbox, so this stays at the documented-API level. 1 1 12 11
European sovereignty
panel opinion
Show reasoningHide reasoning
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. Dimensions not proven either way are unknown, not non-European.
0 — Vendor, contracting entity and hosting shown to be outside the EU, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist and one European element is proven (an EU contracting entity or representative, or EU hosting as an option); the rest of the chain is not stated.
5 — An EU contracting entity and EU hosting stated, with a data processing agreement; sending, tracking or support providers are not all shown to be European or are named without a stated safeguard.
8 — EU or DACH hosting on named infrastructure, EU contracting entity, the subprocessor list published with locations including the sending infrastructure, 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.
The CRM Manager
A Lithuanian entity, UAB Omnisend in Vilnius, is proven and the data processing agreement is published with Standard Contractual Clauses Module Two and the UK addendum incorporated. But that agreement names a group of three companies in Lithuania, England and the United States without saying which one contracts with the customer, and we found no public information on hosting location or where the named subprocessors process — for a category I weigh this heavily, and the proof stops at one European element. 2 2 2
The Deliverability Engineer
A published, self-serve processing agreement incorporating Standard Contractual Clauses Module Two and the UK addendum exists, with a Lithuanian entity, government-access notification duties and 10-day subprocessor change notice. But hosting location is not stated, the subprocessor names and locations are not captured, and the contracting group spans Lithuania, England and the United States without saying which company the customer signs with — decisive uncertainty for a buyer who weighs this heavily. 2 2 2
The Data Protection Officer
The published data processing agreement incorporates the 2021 Standard Contractual Clauses with a Lithuanian entity and gives data subjects third-party beneficiary rights, but the group also contains a UK and a US company and the agreement does not say which one contracts with the customer. Data residency, hosting and the locations of the subprocessors behind the send are unknown from the captured pages, so I cannot place the behavioural data in Europe — no Schrems II argument is offered here, and none can be built on this evidence. 2 2 2
The Shop Owner
There is a Lithuanian entity (UAB Omnisend in Vilnius) and a published data processing agreement incorporating the EU Standard Contractual Clauses, but that same agreement names a group of three companies in Lithuania, England and the United States without saying which one I would contract with. Hosting location, data residency and subprocessor locations are unknown from the captured pages, so I can only credit the one proven European element despite weighing this heavily. 2 2 2
The Integrator
The processing agreement is published and incorporates the EU Standard Contractual Clauses and the UK addendum, and a Lithuanian company in Vilnius heads the group — but the agreement names Lithuanian, English and American entities without saying which one contracts with the customer, and subprocessor locations are named only by purpose, not place. Hosting and data residency are unstated in everything I read, so the chain is unproven beyond that first-listed entity, and I weight that heavily. 2 2 2
The Skeptic
A published data processing agreement incorporating the EU Standard Contractual Clauses exists and a Lithuanian entity with a Vilnius address is named, but the same agreement lists a group of three companies in Lithuania, England and the United States without saying which one contracts with the customer. We found no public information on where hosting or the sending infrastructure sits, and the subprocessors are named by purpose only, with no locations shown — as this buyer weighs sovereignty, that silence is decisive. 2 2 2 4
Pricing transparency
Show reasoningHide reasoning
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 public "from" price, a free plan or one priced tier; how cost scales with contacts or sends is unclear.
5 — Prices per contact or send tier public for the main plans with the billing period stated and the main limits given; some add-ons (dedicated IP, extra domains, overage) may be unpriced.
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.
The CRM Manager
A free start with full access and no credit card required is public, as are zero-cost items like domain signing, double opt-in confirmation mail and the five-day migration. But we found no public information on per-contact or per-send prices for the paid plans — only a 'Pay up to 35%* less' comparison against Klaviyo's Marketing plan — so I cannot compute what my list size and send volume would actually invoice. 1 7 1
The Deliverability Engineer
A free start with full access and no credit card is public, and two items are stated as free — domain signing for all users and double opt-in confirmation mail that never counts toward the monthly email limit. Beyond that we found no public information on paid tier prices, contact-band or send-volume costs, overage rates or dedicated-IP pricing; the only pricing signal is a claim of paying up to 35% less than a named competitor. 1 5 7 1
The Data Protection Officer
A free start with full access and no credit card is public, and domain signing and double opt-in are stated to be free, with confirmation emails excluded from the monthly email limit. I found no public information on priced tiers with numbers, per-contact scaling, billing periods or overage rates — the comparison pages name a Standard plan but never give its price — so the real invoice is not computable from these pages. 1 3 5 7 1
The Shop Owner
The public pricing facts amount to a free full-access start with no credit card, a free domain signature, free double opt-in whose confirmation mails do not count toward the monthly limit, and a relative claim of paying up to 35 percent less than Klaviyo comparing the Standard plan to Klaviyo's Marketing plan. I found no public information on what any tier costs, how price scales with contacts or sends, or overage rates, so I cannot compute the invoice for my list. 1 1 3 5 7
The Integrator
What is public is a free start with no credit card, a free domain signature, free double opt-in whose confirmation emails do not consume the monthly email allowance, a free five-day migration, and a relative claim of paying up to 35% less than Klaviyo on the Standard plan. I found no absolute tier prices, contact-band scaling or overage rates on the captured pages, so a real invoice cannot be computed from them. 3 1 7
The Skeptic
The free start with full access and no credit card is the only price the captured pages contain; the Standard plan is named only inside a comparison claiming up to 35% less than Klaviyo, and a monthly email limit is implied by the note that double opt-in confirmation emails do not count toward it. We found no public information on any paid tier's price, contact tiers, overage rates or add-on costs, so the real invoice cannot be computed from what was captured. 3 1 7 1
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in LT
unverified
Why unverified?The DPA names a group of three companies in Lithuania, England and the United States without saying which one contracts with the customer, so LT reflects only the first-listed UAB Omnisend. |
2/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The full agreement text is published on the vendor's site, though the excerpt shows no online signature or acceptance flow for concluding it. |
1/1 pts | 2 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Omnisend
Is Omnisend European?
Not determined: the vendor’s pages as captured do not say where Omnisend is based. Its vendor, Omnisend, UAB, is incorporated in Lithuania, per the vendor’s page captured 2 Nov 2026.
Where does Omnisend store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Omnisend have a free plan?
Yes. Omnisend has a free plan, per the vendor’s page captured 26 Oct 2026.
What are the best alternatives to Omnisend?
As of 18 Nov 2026, the panel rates Brevo (3/5), Dotdigital (3/5) and Mailjet (3/5) highest among the other 35 Email Marketing & Newsletter products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Brevo (EU-Made, France). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Omnisend alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The full agreement text is published on the vendor's site, though the excerpt shows no online signature or acceptance flow for concluding it.
- Weak sourcing — Legal entity. The DPA names a group of three companies in Lithuania, England and the United States without saying which one contracts with the customer, so LT reflects only the first-listed UAB Omnisend.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 49 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.omnisend.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 22 Sep 2026 Details →
- 2 Data processing agreement (dpa) — found from the homepage www.omnisend.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 3 Campaigns & automation — found from sitemap www.omnisend.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 4 Campaigns & automation — found from sitemap www.omnisend.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 5 Deliverability infrastructure — found from sitemap support.omnisend.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 6 Deliverability infrastructure — found from sitemap support.omnisend.com Checked 16 Nov 2026 Details →
- 7 Consent, proof & tracking limits — found from sitemap support.omnisend.com Checked 16 Nov 2026 Details →
- 8 Consent, proof & tracking limits — found from sitemap support.omnisend.com Checked 16 Nov 2026 Details →
- 9 List ownership, import & exit — found from sitemap support.omnisend.com Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
- 10 List ownership, import & exit — found from sitemap support.omnisend.com Checked 16 Nov 2026 Details →
- 11 Integrations & API — found from sitemap support.omnisend.com Checked 16 Nov 2026 Details →
- 12 Integrations & API — found from sitemap support.omnisend.com Checked 16 Nov 2026 Details →