Email Marketing & Newsletter

AWeber

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 4 dimensions proven

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

by AWeber Communications · www.aweber.com

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The CRM Manager v1.0 · The Deliverability Engineer v1.0 · The Data Protection Officer v1.0 · The Shop Owner v1.0 · The Integrator v1.0 · The Skeptic v1.0 · rubric v1 · evaluated 30 Sep 2026

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 Integrator

Weighted verdict

Has to wire this into a stack that already exists. Wants a documented API with rate limits, webhooks that retry, a sandbox and a deprecation policy. Treats a partner-form integration page as a missing API, and reads "Zapier supported" as an outsourced one.

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

Scored by The Integrator

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 Integrator

Split testing of subject lines and content is documented with segment targeting and preset distributions, and automations run on page-hit, engagement and RSS triggers with tagging from website visits — a solid mid-market feature set. I found no public information on a branching journey builder, dynamic content per segment, send-time optimisation, or tests that report significance, so I cannot credit the higher levels. 1 4 5

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 Integrator

DKIM and DMARC setup is documented unusually well — automatic for 40+ domain providers, simultaneous setup, a status view per domain, a default DMARC reporting address, and sender authentication re-verified on every broadcast. I found no public information on SPF, bounce handling, complaint-loop handling, dedicated IP options or warm-up, so only the authentication half of the picture is evidenced. 3 6 7

Report an error

Consent, proof & tracking limits

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 — Single opt-in with no consent record; tracking is always on and cannot be disabled.

3 — Double opt-in available but not the default, and the consent record is a timestamp without the source, IP or the wording consented to.

5 — Double opt-in as the documented default with a stored consent record including source and timestamp, one-click unsubscribe, and tracking that can be turned off per campaign.

8 — Consent is reproducible as evidence: the confirmation mail and form wording versioned and retrievable per subscriber, unsubscribe honoured across lists, 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.

Report an error

The Integrator

Confirmed opt-in is documented and the import flow lets you switch the confirmation message on or off, which makes double opt-in optional rather than a default; imports do require stating how subscribers signed up, but I found no public information on a stored consent record per subscriber, one-click unsubscribe mechanics, or any way to limit or switch off open and click tracking. Erasure on request and a 30-day response window are documented, which keeps this above the floor. 2 8 9 10

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 Integrator

Import takes CSV, spreadsheet and text files with custom fields, tags and update options behind a documented review process, and export of lists or selected fields is available at any time while the account is active, with filters that expose subscription status. I found no public information on exporting engagement history, campaigns or templates, or on full-account export; deletion is met with a 30-business-day response window rather than evidenced erasure. 3 9 10

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 Integrator

The API is real and documented: OAuth 2 with scopes and PKCE, an API key, a rate-limiting FAQ, and free webhooks for the core subscriber events with HMAC-SHA256 verification and a deduplication header. But webhook delivery is explicitly not guaranteed and I found no public information on retries, a sandbox, a versioned API with a deprecation policy, or vendor-maintained bidirectional shop integrations — the directory is largely integrations developers have already created. 12 13

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 Integrator

The contracting entity is AWeber Systems, Inc. in Pennsylvania, hosting sits with Amazon AWS, the named subprocessors include US names such as Anthropic, OpenAI, Google and Stripe, and I found no public information on EU hosting or an EU entity. The published subprocessor list and a stated transfer basis — the Data Privacy Framework and standard contractual clauses — lift this just above the floor, but the whole arrangement rests on the transfer argument I would rather not have to defend. 2 3 9

Report an error

Pricing transparency

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 Integrator

The only price visible anywhere is a limited-time done-for-you launch offer quoted as "$599 $79", plus the existence of a Free plan that gates split testing behind an upgrade you are told to discuss with the Customer Solutions team. I found no public information on subscription tier prices, contact or send limits, overage rates, or VAT treatment, so a real invoice cannot be computed from these pages. 1 5

Report an error

European sovereignty — proven facts

2 of 4 dimensions proven

Built 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 US ⚠ unverified	0/3 pts	3 Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	Not determined ⚠ unverified	—	uncited Report an error
Subprocessors	US CLOUD Act reach ⚠ unverified	0/2 pts	3 Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 29 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 — Legal entity. Jurisdiction rests on postal addresses naming "USA" and the US-style "Inc."; no state of incorporation or commercial register is stated.
Weak sourcing — Data residency. Not confirmed on the vendor’s own pages as captured.
Weak sourcing — Subprocessors. The excerpted sub-processor table is truncated by "[…]" and no provider's headquarters are stated; the US attribution rests on the names Amazon AWS and Anthropic, and the customer-data nature of some rows (Calendly, Discourse) is not spelled out.
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.

7 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
6 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
4 data 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
3 subprocessors 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 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
1 support 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 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us

Do you know more about AWeber? Tell us Report an error on this page

Sources (13)

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

1 Vendor page www.aweber.com Checked 29 Sep 2026 Details →
2 Privacy policy — found from the homepage www.aweber.com Checked 30 Sep 2026 Details →
3 Data processing agreement (dpa) — found from the homepage www.aweber.com Checked 30 Sep 2026 Details →
4 Campaigns & automation — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
5 Campaigns & automation — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
6 Deliverability infrastructure — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
7 Deliverability infrastructure — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
8 Consent, proof & tracking limits — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
9 Consent, proof & tracking limits — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
10 List ownership, import & exit — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
11 List ownership, import & exit — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
12 Integrations & API — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
13 Integrations & API — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →