whats-best.ai

Email Marketing & Newsletter

E-goi

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by E-goi Marketing Technology S.A. · www.e-goi.com

Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Shop Owner

Weighted verdict

Runs a shop where the newsletter is a revenue channel. Wants the shop connected properly — orders, carts, products flowing in, abandoned-cart and post-purchase flows out — and revenue attributed per campaign. Judges price against contribution, not against a competitor's tier.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Shop Owner

Campaigns & automation

How this is scored

Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.

0 — One-off broadcasts from a fixed template; no segmentation and no automation of any kind.

3 — A drag-and-drop editor and simple list segmentation, but automation is a single welcome mail and there is no testing.

5 — Reusable templates, attribute and behaviour segmentation, multi-step automations on common triggers, and subject-line A/B testing.

8 — A visual journey builder with branching on behaviour and data, dynamic content per segment, send-time optimisation, 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.

Report an error

The Shop Owner

The abandoned-cart and behaviour-triggered flows my shop needs are documented — contacts tracked to the shopping cart, actions automated on a purchase or URL visit, automatic segments — alongside a drag-and-drop editor, free templates and A/B testing. We found no public information on a visual journey builder with branching, send-time optimisation, or test results reported with significance. 2 6

Report an error

Deliverability infrastructure

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 — No documentation of authentication or bounce handling; deliverability appears only as a marketing number.

3 — SPF and DKIM setup documented, but no DMARC guidance, no stated bounce policy and shared sending only.

5 — SPF, DKIM and DMARC documented with a custom sending domain, automatic hard-bounce suppression, and complaint-loop handling stated.

8 — The above plus dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, and published guidance on list hygiene.

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.

Report an error

The Shop Owner

Bounces and complaints are handled automatically through feedback loops with Gmail, Hotmail and Yahoo, invalid addresses are removed on their own, and dedicated-IP warm-up plus daily human monitoring and vendor-handled ISP throttling read like a deliverability operation run on my behalf. We found no public information on DMARC guidance, inbox-placement testing or engagement-based sunsetting. 4 5

Report an error

List ownership, import & exit

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 — Export is addresses only; engagement history, segments and automations cannot leave.

3 — CSV import and export of subscriber fields, but engagement history and unsubscribe state are not exportable.

5 — Full subscriber export including custom attributes, subscription status and unsubscribe state, plus API access sufficient to sync elsewhere.

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.

Report an error

The Shop Owner

Getting my data in is well documented — by API, integrations, spreadsheet, or automatic pulls from the online store, CRM and ERP, keeping custom fields like store and preferred products — and behavioural reporting exports with one click. We found no public information on exporting subscribers with their unsubscribe state, or on deletion executing across all records. 2 5

Report an error

Integrations & API

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 — No API and no named integrations; the list is maintained by CSV upload.

3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.

5 — Named integrations for common shop and CRM systems, a documented REST API with keys, and webhooks for the core 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.

Report an error

The Shop Owner

The connectors I judge a newsletter on are named: Magento, WooCommerce, Prestashop, Salesforce, Zapier with more than 1000 apps, webhooks, an API for custom builds, parsers for shopping carts, and transactional email and SMS in the same product. We found no public information on documented rate limits, webhook retries or a sandbox, which is what I would want before wiring order and cart events in. 2 6

Report an error

European sovereignty

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.

0 — US vendor and contracting entity, US hosting, subprocessors unnamed; subscriber behaviour leaves the EU with no stated basis.

3 — EU hosting offered as an option or for storage only, while sending, tracking or support access remains non-EU, or the subprocessor list is absent.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — sending infrastructure, analytics, support tooling — are non-EU without an explained safeguard.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, complete subprocessor list published, 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.

Report an error

The Shop Owner

We found no public information on where subscriber data and behavioural tracking are hosted, on the contracting entity's jurisdiction, or on any subprocessor touching the send. The only related statement — imported data accessible to the client alone with no third-party access — speaks to who can read my list, not to where my customers' behaviour lives. 4

Report an error

Pricing transparency not rated — the vendor publishes no price

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 headline price per contact tier exists, but send limits, overage rates or the tier where automation begins are not stated.

5 — Contact-tier prices public with the billing period stated and send limits given, but at least one commonly needed capability sits in an unpriced tier or add-on.

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.

Report an error

The Shop Owner

Beyond a free account, a 14-day trial without a credit card, a 30-day refund on paid plans, and the WhatsApp basis of paying only Meta's direct cost, we found no public information on contact-tier prices, send limits or overage rates. For a channel that has to earn its keep per campaign, I cannot compute the invoice for my list size from what is published. 1 2

Report an error

Where this could be wrong

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.

Sources (6)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page www.e-goi.com Checked 29 Sep 2026 Details →
  2. 2 Campaigns & automation — found from sitemap www.e-goi.com Checked 30 Sep 2026 Details →
  3. 3 Campaigns & automation — found from sitemap www.e-goi.com Checked 30 Sep 2026 Details →
  4. 4 Deliverability infrastructure — found from sitemap www.e-goi.com Checked 30 Sep 2026 Details →
  5. 5 List ownership, import & exit — found from sitemap www.e-goi.com Checked 30 Sep 2026 Details →
  6. 6 Integrations & API — found from sitemap www.e-goi.com Checked 30 Sep 2026 Details →