Email Marketing & Newsletter
eSputnik
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by eSputnik LLC · esputnik.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.
eSputnik at a glance
- Vendor
- eSputnik LLC
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Default not stated; pages mention Ireland source, captured 3 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 3 Nov 2026
- Panel verdict
- The AI panel rates eSputnik 2/5, the mean of 6 judges. eSputnik is strongest on campaign and automation (5 to 7) and integrations (4 to 6): the pages document predictive segments that update themselves, more than twenty pre-built trigger scenarios from abandoned cart to back-in-stock, dynamic content across channels, a free Shopify plugin and connectors for WooCommerce, OpenCart, Wix and Horoshop. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 3 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
eSputnik is strongest on campaign and automation (5 to 7) and integrations (4 to 6): the pages document predictive segments that update themselves, more than twenty pre-built trigger scenarios from abandoned cart to back-in-stock, dynamic content across channels, a free Shopify plugin and connectors for WooCommerce, OpenCart, Wix and Horoshop. Deliverability is the weakest surface (0 to 2): we found no public information on SPF, DKIM or DMARC set-up, bounce suppression, dedicated IPs or reputation reporting, and the agreement's 99.95% figure is infrastructure uptime. Consent and proof (2 to 3) documents GDPR rights, but we found no public information on double opt-in, unsubscribe handling or turning tracking off. List data control (3 to 4) rests on contractual return-or-delete rather than documented export formats. The judges split on sovereignty (5 to 8): they credit the Warsaw contracting entity, Amazon Web Services hosting in Dublin and the published subprocessor list, but weigh the US subprocessors Amplitude, Anthropic, Google, Intercom and OpenAI differently, with transfers resting on standard clauses and written consent. We found no public plan prices on any captured page.
Speaks for it
- More than twenty pre-built trigger scenarios — abandoned cart, browse abandonment, wishlist reminders, back-in-stock — fed by a one-click web tracker recording product views, cart changes and purchases.
- Predictive segments that update automatically as customers browse and buy, with purchase-probability scoring usable in the interface without SQL or data scientists.
- A free Shopify plugin promising a first campaign minutes after connecting the store, plus named connectors for WooCommerce, OpenCart, Wix and Horoshop and a documented API with keys.
- A European contracting base: RETENTION YES SP. Z.O.O in Warsaw, services stated to run on Amazon Web Services in Dublin, with Hetzner in Germany and a subprocessor list published with locations.
- A data processing agreement folded into the terms of use, ISO/IEC 27001:2022 stated, and return or deletion of personal data promised on termination or the controller's request.
Held against it
- Deliverability scores range from 0 to 2, and we found no public information on SPF, DKIM or DMARC set-up, bounce or complaint handling, dedicated IPs or reputation reporting.
- We found no public information on double opt-in, per-subscriber consent records, unsubscribe handling, or any switch to turn off open, click or web tracking.
- The list exit path is contractual rather than product-documented: we found no public information on field-mapped import or subscriber export with custom fields and statuses.
- The published subprocessor list names Amplitude, Anthropic, Google, Intercom and OpenAI in the USA, with transfers resting on standard clauses and a written-consent requirement rather than a per-provider legal basis.
- We found no public information on webhooks, documented rate limits, a sandbox, or a named CRM integration — Pipedrive appears in the subprocessor list, not as an integration.
Best for
- You run a store on Shopify, WooCommerce, OpenCart, Wix or Horoshop and want abandoned-cart and back-in-stock triggers running quickly.
- You want AI purchase-probability segmentation your marketers can use without SQL or data scientists.
- You need a Warsaw contracting entity with hosting stated in Dublin, and standard clauses plus written consent for the disclosed US subprocessors are acceptable to your legal review.
- You want campaign results exported to Google BigQuery for analysis in your own warehouse.
Avoid if
- You need documented sender authentication, dedicated IPs and reputation reporting before committing your list.
- You must evidence per-subscriber consent records, double opt-in or unsubscribe handling to a regulator.
- You need documented subscriber export with custom fields and statuses, or field-mapped import, for a clean migration.
- A processing chain free of US subprocessors is a hard requirement for your data protection review.
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 3 of 5 |
| Deliverability infrastructure | 1 of 5 |
| Consent, proof & tracking limits | 1.5 of 5 |
| List ownership, import & exit | 2 of 5 |
| Integrations & API | 2.5 of 5 |
| European sovereignty | 3.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
Segmentation here is the real thing: purchase-probability scoring that updates segments automatically as customers browse and buy, dynamic content per segment across ten channels, and a library of more than twenty trigger scenarios from abandoned cart to back-in-stock. What I cannot see is the journey canvas — nothing on branching builders, send-time optimisation, or A/B testing beyond a bare mention — and even ready-made templates are flagged as coming soon, so it sits between a solid campaign engine and a true lifecycle tool. 3 5
The Deliverability Engineer
Documented automation runs deep: a library of more than twenty pre-built trigger scenarios driven by shop behaviour such as abandoned carts and back-in-stock, predictive segments that refresh themselves as customers browse and buy, dynamic content per segment across ten channels, and A/B testing. What holds it back is the composition and journey layer — we found no public information on a visual journey builder with branching or send-time optimisation, and the vendor's own page marks ready-made templates as coming soon. 3 5
The Data Protection Officer
The captured product pages show behaviour-based segments that update themselves as people browse and buy, predictive purchase-probability scoring, A/B testing, dynamic content across a dozen channels, and a library of more than twenty trigger scenarios including abandoned cart fed by a one-click web tracker — well past a plain broadcast tool. A visual journey builder with branching, send-time optimisation and significance-reported testing are not described on the captured pages, and ready-made templates are marked as coming soon. 3 5
The Shop Owner
The machinery a shop wants is documented: a library of more than twenty trigger scenarios — abandoned cart, browse abandonment, wishlist reminders, back-in-stock — fed by a one-click tracker that records product views, cart changes and purchases, plus auto-updating predictive segments, dynamic content across channels, A/B testing and analytics that include campaign revenue. The composing side is thinner: ready-made templates are marked as coming soon, and we found no public information on a visual journey builder, send-time optimisation or significance reporting. 3 5
The Integrator
The journey side is strongly documented: predictive segments that auto-update on behaviour and purchases, dynamic content per segment across ten channels, and a library of more than twenty trigger scenarios fed by shop events like abandoned carts, browse abandonment and back-in-stock. But the captured pages never describe a campaign editor, ready-made templates are marked as coming soon, and A/B testing appears as a bare label with no detail on what is tested or how results are reported. 3 5
The Skeptic
Predictive segmentation on behaviour and purchase history that updates itself, a library of more than twenty trigger scenarios (abandoned cart, browse abandonment, wishlist reminders, back-in-stock), A/B testing and dynamic content across channels are all documented. What holds it back: the captured pages give no visual journey builder or branching, ready-made templates are marked as coming soon, and we found no public information on send-time optimisation or significance reporting. 3 5
Deliverability infrastructure
n/r
n/r
n/r
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
The platform plainly sends email, SMS and push from its own infrastructure and its terms carry an anti-spam policy, but we found no public information on SPF, DKIM or DMARC set-up, bounce or complaint handling, or sending reputation. Sending without documented authentication guidance is exactly the gap that decides whether my lifecycle programme lands in the inbox. 4 5
The Deliverability Engineer
The pages describe an omnichannel sender across email, SMS, push and Viber, but document almost nothing about how the mail arrives: we found no public information on SPF, DKIM or DMARC set-up, custom sending domains, bounce suppression, dedicated IPs or reputation reporting. The only hygiene-adjacent material is that the Terms of Use carry an anti-spam policy, mailing moderation and import rules — governance of senders, not documented sending infrastructure. 4 5
The Data Protection Officer not rated — no public information
We found no public information on sending infrastructure, SPF, DKIM or DMARC set-up, bounce handling, complaint feedback or reputation management on the pages captured for this review — the homepage, the product pages and the Shopify integration page. 1 3 5
The Shop Owner not rated — no public information
We found no public information on deliverability — the captured pages cover predictive segmentation, GDPR, the data processing agreement and the Shopify plugin, and none describes domain authentication, bounce or complaint handling, dedicated IPs, warm-up or inbox-placement testing. The agreement's 99.95 percent uptime and encryption clauses speak to infrastructure security, not to whether the mail arrives. 1 2 3 4 5 6
The Integrator not rated — no public information
We found no public information on sender authentication such as SPF, DKIM or DMARC, bounce or complaint handling, dedicated IPs or reputation monitoring in any of the captured pages — the homepage, the data processing agreement, the predictive segmentation page, the GDPR page and the integration pages. 1 3 4 5
The Skeptic
Mail goes out through the vendor's own platform and the terms of use carry an anti-spam policy, moderation rules for mailings and import rules, which is policy-level hygiene. Beyond that we found no public information on SPF, DKIM or DMARC set-up, bounce or complaint suppression, dedicated IPs or reputation reporting; the 99.95% figure in the agreement is infrastructure uptime, not delivery. 4 5 2
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
Subscription forms exist among the eight widget types, the GDPR page lists data-subject rights to a copy, to edit and to be forgotten, and the data processing agreement promises help answering access and erasure requests. But we found no public information on double opt-in, the unsubscribe link, a per-subscriber consent record, or any way to switch off the web tracker's product-view and purchase tracking. 2 4 5
The Deliverability Engineer
Subscription forms are among the documented widget types, and the GDPR pages commit to access, correction and erasure rights with a named DPO contact and contractual assistance on data-subject requests. We found no public information on double opt-in, a per-subscriber consent record, unsubscribe handling, or any way to limit or switch off tracking — behaviour tracking is documented as present, with a one-click tracker for product views, cart changes and purchases. 2 4 5
The Data Protection Officer
Subscription-form widgets are documented, the GDPR page lists access, edit and erasure rights, and the processing agreement promises assistance with data-subject requests. But double opt-in, a per-subscriber consent record with timestamp and source, unsubscribe handling and any switch to turn open, click or web tracking off are not described on the captured pages — and the web tracker is presented as a one-click install with no documented off switch, which is exactly the gap I cannot sign off on. 2 4 5
The Shop Owner
Sign-up forms are among the eight widget types, and the GDPR pages show real machinery — a data protection officer contact, data-subject rights to a copy, edits and erasure, agreement assistance with access and deletion requests, and an antispam policy inside the Terms of Use. We found no public information on double opt-in, per-subscriber consent records, unsubscribe handling, or any switch for open and click tracking, so the proof side stays undocumented. 4 5 2
The Integrator
The captured pages show subscription forms among the eight widget types, and the data processing agreement obliges the vendor to assist with data-subject access, erasure and portability requests. We found no public information on double opt-in, unsubscribe handling, a stored consent record, or any way to switch off open and click tracking — while the web tracker is advertised as a one-click install. 5 2 4
The Skeptic
Subscription forms are among the widget types, the GDPR pages document data-subject rights (a copy of the data, edits, the right to be forgotten) and the processing agreement promises assistance with access and erasure requests. But we found no public information on double opt-in, a per-subscriber consent record, unsubscribe handling, or limiting email-level tracking; the web tracker recording product views, cart changes and purchases is presented as a one-click install. 4 5 2
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
The terms include import rules, a documented API with keys exists, campaign results export to Google BigQuery, and the agreement promises data return and deletion on termination or on the controller's request. What no captured page shows is field-mapped import, export of subscribers with their engagement history, or deletion executed across all records — the mechanics of a clean exit. 2 3 4 5
The Deliverability Engineer
Import is acknowledged through the Terms of Use import rules, a documented API with keys exists, communication results can be exported to Google BigQuery, and the data processing agreement commits to deleting personal data on the controller's request and to return or deletion at termination. Subscriber export with fields intact, field mapping, and evidenced deletion of an individual subscriber across all records are not described on the captured pages. 2 3 4 5
The Data Protection Officer
The pages document import from CRM, shop and analytics sources, an API with keys, a right to be forgotten, and return-or-delete on termination, which gives partial control over the list. A documented full subscriber export with custom fields and engagement history is not described on the captured pages, and the one analytics export named sends communication results to Google BigQuery. 2 3 4 5
The Shop Owner
Import rules, a documented API with keys, and a Google BigQuery export of communication results are stated, the GDPR page names the right to be forgotten and to a copy of one's data, and the agreement promises return or deletion of personal data at termination. What is not described is field mapping on import, export of unsubscribe state or engagement history in open formats, or anything about export throttling — the exit path is documented at the level of rights and clauses rather than formats. 4 3 5 2
The Integrator
The data processing agreement promises return or deletion of personal data on termination and removal on the controller's request, campaign results can be exported to Google BigQuery, and the terms of use carry explicit import rules — a real exit path for engagement data. We found no public information on field-mapped import, on exporting subscribers with their custom fields and subscription status, or on whether exports are throttled, so exit is asserted contractually rather than documented as a product feature. 2 5 4
The Skeptic
A documented API with keys, an export of communication results to Google BigQuery, deletion of a subscriber on request, and return-or-delete on termination are documented, with import rules set in the terms. We found no public information on subscriber export with custom fields and statuses, field mapping on import, export throttling or migration tooling. 4 3 5 2
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
Named shop integrations for Shopify, WooCommerce, OpenCart, Wix and Horoshop — with a free Shopify plugin that connects a store and launches a first campaign in minutes — plus a documented API with keys and a one-click web tracker feeding product views, cart changes and purchases. Webhooks with retries, documented rate limits and a sandbox are not described, which keeps this short of developer-grade. 3 5
The Deliverability Engineer
Named connectors for Shopify, WooCommerce, OpenCart, Wix and Horoshop, a free Shopify plugin promising a first campaign within minutes, and a documented API with keys and a user guide give a working connection surface for shops. We found no public information on webhooks, rate limits, a sandbox, or maintained bidirectional CRM integrations. 3 5
The Data Protection Officer
Named shop integrations for Shopify, WooCommerce, OpenCart, Wix and Horoshop, a documented API with keys, a Viber channel and a BigQuery export cover the surface of a mid-level tool, with a free Shopify plugin promising a first campaign in minutes. Webhooks, documented rate limits and a sandbox are not described on the captured pages. 3 5
The Shop Owner
This is the strongest surface for a shop: a free Shopify plugin promising a first campaign minutes after connecting the store, integrations for WooCommerce, OpenCart, Wix and Horoshop, a documented API with keys, and the one-click tracker that makes abandoned-cart and back-in-stock triggers possible. We found no public information on webhooks with retries, documented rate limits or a sandbox, so the depth of the API beyond keys is unproven. 5 3 6
The Integrator
There is a genuine build surface: a documented API with a user guide and API keys, named shop plugins including a free Shopify connector plus WooCommerce, OpenCart, Wix and Horoshop, and a one-click tracker for product views, cart changes and purchases. What I need to wire this in confidently we found no public information on — webhooks with retries, documented rate limits, a sandbox, or an API versioning and deprecation policy — and no CRM integration is shown either. 3 5 6
The Skeptic
Named e-commerce integrations for Shopify (a free plugin), WooCommerce, OpenCart, Wix and Horoshop, plus API documentation and keys. We found no public information on webhooks, documented rate limits, a sandbox, or a named CRM integration — Pipedrive appears in the subprocessor list, not as an integration. 5 3
European sovereignty
panel opinion
panel disagrees
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
The contracting entity is RETENTION YES SP. Z.O.O in Warsaw, hosting is stated as AWS in Dublin with Hetzner in Germany, ISO/IEC 27001:2022 is claimed, and the data processing agreement publishes a subprocessor list with locations. Non-EU processing is disclosed rather than hidden — Amplitude, Google, Intercom, OpenAI and Anthropic, all in the USA — with a clause barring third-country transfers without the customer's written consent, though the legal basis per transfer beyond the general clause language is not spelled out. 2 4
The Deliverability Engineer
The contracting party in the data processing agreement is a Polish company, services are stated to run on Amazon Web Services in Dublin, and the subprocessor list is published with locations, showing sending infrastructure in Ireland alongside Hetzner in Germany and Pipedrive in Estonia, with an ISO/IEC 27001:2022 certificate published. Four named processors sit in the United States — Amplitude for behavioural analytics, Google, OpenAI and Anthropic for AI services, Intercom for support chat — and transfers rest on standard clauses plus a written-consent requirement rather than a stated legal basis per processor. 2 4
The Data Protection Officer
The processing agreement names a Polish contracting entity in Warsaw, the GDPR page places hosting in Dublin on AWS, and the subprocessor list is published with locations — a European core, with encryption, breach notification and audit rights in the agreement. But that same list puts Amplitude, Google, Intercom, OpenAI and Anthropic in California, and Amplitude's stated job is product analytics and event tracking, so the answer to where behavioural data lives still runs through standard clauses and a written-consent rule rather than staying in Europe. 2 4
The Shop Owner
The contracting side is European — a Warsaw company, services hosted in Dublin on AWS with Hetzner in Germany, a data processing agreement folded into the Terms of Use, and a published subprocessor list with locations. Five of those subprocessors sit in the USA, including product analytics, AI services and live chat; the agreement requires written consent for third-country transfers and names standard-clauses governing law, but we found no public information on a transfer-impact assessment for that chain. 2 4
The Integrator
The chain is proven where I need it: contracting entity RETENTION YES SP. Z.O.O in Warsaw, services hosted in Dublin on named Amazon Web Services infrastructure, a subprocessor list published with locations including the sending and hosting providers, standard contractual clauses governed by the exporter's Member State law, a bar on third-country transfer without written consent, and an ISO/IEC 27001:2022 certificate stated. Not sovereign end to end, though: Amplitude, Anthropic, Google, Intercom and OpenAI are all listed in San Francisco, so behavioural analytics, AI text processing and support chat run through US processors under contractual clauses rather than staying in Europe. 2 4
The Skeptic
The contracting entity is in Warsaw and the platform states its services run in Dublin on Amazon Web Services, with a data processing agreement folded into the terms and a subprocessor list published in its appendix. But that list names Amplitude, Anthropic, Google, Intercom and OpenAI in the USA — analytics, AI and support all in the chain — and the safeguard offered is a written-consent clause and a governing-law provision for the standard clauses rather than a per-provider legal basis; the published ISO/IEC 27001:2022 certificate covers security management, not a European-only chain. 2 4
Pricing transparency
not rated — the vendor publishes no price
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 not rated — no public information
We found no public information on pricing transparency — no plan tiers, per-contact prices, send limits or a calculator on any page we read, including the homepage, the predictive-segmentation page and the Shopify page. I cannot judge a number I was never shown. 1 3 5
The Deliverability Engineer not rated — no public information
We found no public information on plan prices, billing periods, contact or send tiers, overage rates or feature boundaries on the captured pages. The only price statement anywhere is that the Shopify plugin itself is free. 1 3 5
The Data Protection Officer not rated — no public information
We found no public plan prices, contact tiers or billing periods on any page captured for this review — the homepage and the product pages show none. The only cost statement anywhere is a free Shopify plugin, which does not let a sender compute an invoice. 1 3 5
The Shop Owner not rated — no public information
We found no public information on pricing transparency: no tiers, no per-contact or per-send figures, no overage or VAT treatment anywhere in the pages we reviewed — only a free Shopify plugin, which prices the connector, not the sending. Before I can weigh price against what a campaign contributes, this starts as a sales conversation. 1 3 5 6
The Integrator
None of the captured pages shows a plan, a tier or a price per contact or send, so I cannot compute any invoice from public information. The only pricing statements found are a free Shopify plugin and custom development on request, which points to a sales conversation rather than a public rate card. 1 3 4 5
The Skeptic not rated — no public information
We found no public information on plan prices, contact or send limits, overage rates or VAT treatment on any page captured. The only price-adjacent statements are a claim of cutting costs in expensive channels by up to 50% and a free Shopify plugin, neither of which prices the product for a given list size or send volume. 1 3 5
European sovereignty — proven facts
0 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 | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about eSputnik
Is eSputnik European?
Not determined: the vendor’s pages as captured do not say where eSputnik is based.
Where does eSputnik store data?
The default storage location for customer data is not stated on the vendor’s pages as of 3 Nov 2026. The vendor’s pages mention Ireland as hosting location, per the vendor’s page captured 3 Nov 2026.
Does eSputnik have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to eSputnik?
As of 3 Nov 2026, the panel rates Brevo (3.5/5), CleverReach (3/5) and Dotdigital (3/5) highest among the other 31 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). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: eSputnik alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 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, Legal entity, Hosting location. Not confirmed on the vendor’s own pages as captured.
- 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.
- We found no public information on pricing on the pages we read (esputnik.com, esputnik.com/uk/data-processing-agreement, esputnik.com/predictive-segmentation, esputnik.com/gdpr, esputnik.com/shopify, esputnik.com/woocommerce). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 20 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
- 9 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
- 2 compliance 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
- 2 support 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 data 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 legal 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
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (6)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page esputnik.com Checked 3 Nov 2026 Details →
- 2 Data processing agreement (dpa) — found from the homepage esputnik.com Checked 3 Nov 2026 Details →
- 3 Campaigns & automation — found from sitemap esputnik.com Checked 3 Nov 2026 Details →
- 4 Consent, proof & tracking limits — found from sitemap esputnik.com Checked 3 Nov 2026 Details →
- 5 Integrations & API — found from sitemap esputnik.com Checked 3 Nov 2026 Details →
- 6 Integrations & API — found from sitemap esputnik.com Checked 3 Nov 2026 Details →