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 panel's verdict

E-goi's strongest documented ground is deliverability, scored 6-7 for a published stack of SPF, SenderID, DomainKeys and DKIM authentication, feedback loops with Gmail, Hotmail and Yahoo, dedicated-IP warm-up across hundreds of IP addresses, suppression lists and daily human monitoring. Campaign and automation, 5-6, and integrations, 5-6, cover the mid-level basket: a drag-and-drop editor, behaviour-triggered and abandoned-cart campaigns, lead scoring, A/B testing as a named module, and connectors for WordPress, Salesforce, Magento, Prestashop and WooCommerce plus Zapier with more than 1000 apps, webhooks and an API. The weak ground is compliance and ownership. Consent and proof sits at a flat 2, with no public information on double opt-in, a stored consent record, one-click unsubscribe or limits on open and click tracking. Sovereignty scores 1-2 with no sovereignty attributes on record. List data control scores 2-3: import is broad, export and deletion unevidenced. Spreads never exceed one point and the flagged splits came back with nothing notable. Entry terms: a free account with no credit card and a 14-day trial.

Report an error

Speaks for it

  • Deliverability scores 6-7 on a documented stack of SPF, SenderID, DomainKeys and DKIM, feedback loops with Gmail, Hotmail and Yahoo, and dedicated-IP warm-up across hundreds of IP addresses.
  • Campaign and automation scores of 5-6 rest on a drag-and-drop editor, behaviour-triggered and abandoned-cart campaigns, lead scoring and A/B testing as a named module.
  • Named integrations cover WordPress, Salesforce, Magento, Prestashop and WooCommerce, plus Zapier with more than 1000 apps, webhooks and an API, scoring 5-6.
  • Import is broad — API, integrations, Excel, copy and paste, and automatic pulls from CRM, online store or ERP — with custom fields and tags intact.
  • Entry terms are published — a free account with no credit card, a 14-day trial and a 30 day money-back guarantee in any paid plan.

Report an error

Held against it

  • Consent and proof scores sit at 2 with no public information on double opt-in, a stored consent record, one-click unsubscribe, or limits on open and click tracking.
  • Sovereignty scores 1-2 with no sovereignty attributes on record — nothing published on hosting location, contracting-entity jurisdiction or subprocessors.
  • The exit half of list ownership is unevidenced — no public information on exporting subscribers with unsubscribe state or on documented deletion; list data control scores 2-3.
  • Upper-band features are undocumented — a journey builder with branching, send-time optimisation, DMARC guidance and inbox-placement testing.

Report an error

Best for

  • You run an online store and need abandoned-cart and behaviour-triggered campaigns with named Magento, WooCommerce and Prestashop connectors.
  • You want the vendor to run deliverability on your behalf — authentication, feedback loops, dedicated-IP warm-up and daily human monitoring are all published.
  • You import contacts from a CRM, online store or ERP and want custom fields and tags preserved on arrival.
  • You want campaign and transactional sending (Slingshot) in one platform alongside email, SMS, push, voice and WhatsApp.

Report an error

Avoid if

  • You must show a regulator a stored consent record, double opt-in or one-click unsubscribe mechanics — consent and proof scored a flat 2.
  • You need documented hosting location, contracting-entity jurisdiction or a subprocessor list — ask the vendor: the public pages we read do not show it
  • You need to leave with your list intact — no public information covers exporting subscribers with unsubscribe state or deleting a subscriber across records.

Report an error

The scores

Campaigns & automation

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

A drag-and-drop editor, free templates, attribute and behaviour segmentation, and automation triggered by cart abandonment, URL visits and purchases give me a real journey engine rather than a broadcaster. What holds it down: the A/B testing evidence is a module name only with nothing on significance reporting, and we found no public information on a visual journey builder with branching, dynamic content per segment, or send-time optimisation. 2 5 6

Report an error

The Deliverability Engineer

A drag-and-drop editor, free templates, behaviour and attribute segmentation, lead scoring and multi-step "Autobots" triggered by cart abandonment and site behaviour are all documented, and A/B testing is listed among the optimisation modules. We found no public information on a visual journey builder with branching, send-time optimisation, dynamic content per segment, or tests that report significance rather than raw counts. 2 6

Report an error

The Data Protection Officer

Templates, behaviour-based segments and multi-step automation are all evidenced — abandoned-cart follow-ups, lead scoring, and a multichannel sequence that texts or pushes when a mail goes unopened. I found no public information on a branching journey builder, dynamic content per segment, send-time optimisation or A/B testing that reports significance, so I stop short of the upper band. 2 4 5

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

The Integrator

Drag-and-drop editing, free templates, behaviour-based segmentation and Autobots automation with abandoned-cart, lead-scoring and behaviour-triggered campaigns are all documented, alongside A/B testing. We found no public information on a journey builder with branching, dynamic content per segment, send-time optimisation or significance reporting. 2 6

Report an error

The Skeptic

The marketing pages show a drag-and-drop editor, free templates, behaviour-based segmentation with tags and custom fields, triggered campaigns for abandoned carts, reminders and sales follow-ups, lead scoring, and A/B testing as a named feature — that is the full mid-level basket. We found no public information on a visual journey builder with branching, dynamic content per segment, send-time optimisation, or test results reported with significance rather than raw counts. 2 4

Report an error

Deliverability infrastructure

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

SPF, DKIM, SenderID and DomainKeys are documented, invalid and bouncing addresses are automatically removed and kept out by suppression lists, feedback loops with Gmail, Hotmail and Yahoo are stated, and there is dedicated-IP warm-up plus daily human monitoring of antispam standards. However, we found no public information on DMARC guidance, a custom sending domain, seed or inbox-placement testing, or engagement-based sunsetting. 4 5

Report an error

The Deliverability Engineer

The infrastructure is unusually well documented where it counts: SPF and DKIM authentication, dedicated-IP warm-up across hundreds of addresses of stated reputation levels, feedback loops with Gmail, Hotmail and Yahoo that process bounces and complaints, automatic removal of invalid and bouncing addresses, suppression lists, and daily human monitoring of delivery against antispam standards. It stops short of the top: we found no public information on DMARC guidance, inbox-placement or seed testing, or engagement-based sunsetting of inactive subscribers, and the advertised reach claim I set aside as always. 4 5

Report an error

The Data Protection Officer

Authentication is documented for SPF and DKIM alongside SenderID and DomainKeys, feedback loops with Gmail, Hotmail and Yahoo are stated to process bounces and complaints automatically, and dedicated-IP warm-up with hundreds of addresses is documented. I found no public information on DMARC guidance, a custom sending domain, or seed and inbox-placement testing, which holds this below the top bands. 4 5

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

The Integrator

Authentication with SPF, DKIM (plus SenderID and DomainKeys), feedback loops with Gmail, Hotmail and Yahoo for bounces and complaints, automatic removal of invalid and bouncing addresses, suppression lists and a documented dedicated-IP warm-up are all published, with ISP rules, throttling and daily human monitoring handled by the vendor. We found no public information on DMARC guidance, custom sending domain setup, or seed and inbox-placement testing. 4 5

Report an error

The Skeptic

The deliverability page documents SPF, SenderID, DomainKeys and DKIM, feedback loops with Gmail, Hotmail and Yahoo that automatically process bounces and complaints, automatic removal of invalid and bouncing addresses, suppression lists, dedicated-IP warm-up across hundreds of IP addresses, and daily human analysis of delivery processes. We found no public information on DMARC, custom sending domains, or seed and inbox-placement testing, which caps this below the fuller stack. 4 5

Report an error

List ownership, import & exit

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

Import is well covered — API, integrations, Excel or copy-paste, with custom fields and tags arriving intact — and behavioural reporting exports with a single click. But the export story stops at reports: we found no public information on exporting subscribers with status, engagement history and unsubscribe state, or on documented deletion across records. 2 5

Report an error

The Deliverability Engineer

Import is documented broadly — API, integrations, spreadsheets, copy and paste, CRM, online store and ERP sync with custom fields and tags — and the vendor states imported data is accessible to the client only, with behavioural analytics exportable in one click. We found no public information on export of subscribers with subscription and unsubscribe state, engagement history, or on deletion of a subscriber across records, so the exit side of ownership rests on nothing published. 2 4 5

Report an error

The Data Protection Officer

Import is well served — spreadsheet, copy and paste, API, and automatic imports from CRM, online store, ERP or the website database, with freely definable fields and tags. Export is evidenced only as behavioural reporting exported with a single click; I found no public information on exporting subscribers with subscription and unsubscribe state, on documented deletion of a subscriber across all records, or on what leaving costs. 2 4 5

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

The Integrator

Import is well covered — Excel, copy and paste, API and automatic imports from CRM, store or ERP, with arbitrary custom fields — and behavioural reporting exports with one click. We found no public information on exporting subscriber records with subscription status and engagement history, on documented deletion, or on any exit path from the platform. 5 2

Report an error

The Skeptic

Import is genuinely well covered — API, integrations, Excel spreadsheet, copy and paste, custom fields, tags, and automatic imports from CRM, store or ERP — and behavioural reporting can be exported "with a single click". We found no public information on export of the subscriber list itself, engagement history or unsubscribe state, nor on documented deletion of a subscriber across records, so the exit half of the question rests on nothing published. 2 4 5

Report an error

Integrations & API

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

WordPress/WooCommerce, Magento, Salesforce and Prestashop are named, webhooks are described, Zapier and OmniConnect extend the surface by a thousand-plus apps, and data flows both directions — automatic imports from CRM or ERP and notifications back to sales at a funnel stage. We found no public information on rate limits, webhook retries, a sandbox, or API versioning. 2 6

Report an error

The Deliverability Engineer

Named integrations include WordPress and WooCommerce, Magento, Prestashop and Salesforce, webhooks are documented, the API supports custom integrations, and Zapier plus an integration centre extend the surface, with transactional sending available on the platform. We found no public information on documented rate limits, webhook retries, or a sandbox, which is what the higher end of this criterion would need. 2 6

Report an error

The Data Protection Officer

Named connections to WordPress, WooCommerce, Magento, Prestashop and Salesforce, a webhook mechanism, Zapier with more than a thousand apps and an API for building custom integrations — the surface a newsletter needs is present. I found no public information on documented rate limits, a sandbox, webhook retries or an API versioning policy. 2 6

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

The Integrator

Named integrations including WordPress/WooCommerce, Magento, Salesforce and Prestashop, an API for building custom ones, webhooks, and transactional sending via Slingshot are documented. The long tail runs through Zapier and OmniConnect rather than vendor-maintained connectors, and we found no public information on documented rate limits, a sandbox, webhook retries, or API versioning with a deprecation policy — the things I need before wiring this into an existing stack. 6 2

Report an error

The Skeptic

Named integrations include WordPress, Salesforce, Magento, Prestashop and WooCommerce, plus Zapier with "more than 1000 apps", webhooks, an API for building custom integrations, email parsers for shopping carts, and an official WhatsApp integration as a Meta Tech Provider. We found no public information on rate limits, webhook retries, a sandbox, or whether the named integrations are maintained and bidirectional. 2 6

Report an error

European sovereignty panel opinion

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

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

The sovereignty record is empty: the captured pages name no hosting jurisdiction, no contracting-entity location beyond the vendor's legal name, and no subprocessors, so I cannot verify where subscriber data and behavioural tracking are processed. Weighing this category heavily, the absence of published information is an absence of demonstrated protection. 1 4

Report an error

The Deliverability Engineer

Nothing is on record here: the captured pages give no hosting location, no contracting-entity jurisdiction and no subprocessor list, and I found no public information on any of it. For a buyer who weighs this heavily, unevidenced is unproven. 1

Report an error

The Data Protection Officer

The sovereignty record carries nothing: I found no public information on where subscriber and behavioural data are hosted, where the contracting entity sits, or a single named subprocessor, while the product pages describe omnichannel tracking with real-time geolocation following people into physical stores. Until the vendor states where that data lives and who touches the send, every send rests on an undocumented transfer I would have to defend. 1 2

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

The Integrator

The sovereignty record is empty: beyond the vendor's Portuguese-form company name and a claim that imported data is accessible only to the client, we found no public information on hosting location, the contracting entity's jurisdiction, certification, or any subprocessor list. For a category I weigh this heavily, an undocumented data chain is not one I can sign off on. 1 4

Report an error

The Skeptic

The independently sourced sovereignty attributes came back with nothing on record, and the captured pages are silent on hosting location, contracting entity, sending infrastructure and every subprocessor. For a buyer who weighs this heavily, the total absence of any documented EU option or named data-centre provider means this scores by what silence is worth, just above the confirmed-US floor. 1 4

Report an error

Pricing transparency not rated — the vendor publishes no price

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

Only commercial comfort is public — a 14-day trial without a credit card, a free account, a 30-day money-back guarantee on paid plans, and WhatsApp billed at Meta's direct cost. No tier prices, contact or send limits, overage rates or VAT treatment appear on any captured page, so a buyer cannot compute the invoice for their list size. 1 2

Report an error

The Deliverability Engineer

No price figure appears in any capture — only a free account without credit card, a 14-day trial, a 30-day money-back guarantee on paid plans, and WhatsApp charged at the direct cost to Meta with no commissions. We found no public information on contact-tier prices, send limits, overage rates or VAT treatment, so a real invoice cannot be computed from public pages. 1 2

Report an error

The Data Protection Officer

A free account, a 14-day trial without a credit card and a 30-day money-back guarantee on paid plans are stated, but no contact-tier price, send limit or overage rate appears anywhere; the only cost statement is that WhatsApp carries no commission beyond the direct cost to Meta. A sender cannot compute a real invoice from what is published. 1 2

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

The Integrator

Only entry terms are public: a 14-day free trial without a credit card, a free start, a 30-day money-back guarantee on paid plans, and WhatsApp at Meta's direct cost with no commission. We found no public information on any paid tier price, send limits, overage rates or VAT treatment, so no real invoice can be computed from these pages. 1 2

Report an error

The Skeptic

The only pricing facts published are a free account with no credit card, a 14-day trial, a "30 day money-back guarantee in any paid plan", and WhatsApp billed at "the direct cost to Meta" with no commissions. We found no public information on tier prices, send limits, overage rates or feature boundaries, so a buyer cannot compute even a rough invoice for their list size from these pages. 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 →