Email Marketing & Newsletter

Klaviyo

Rest of world 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.

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

Compare with Inxmail → Compare with Mailchimp → 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 Deliverability Engineer

Weighted verdict

Cares about one number nobody publishes honestly: what reaches the inbox. Reads for authentication, IP and domain reputation, bounce discipline and sunsetting. Ignores every advertised delivery rate on principle — the infrastructure either is documented or it is not.

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

Scored by The Deliverability Engineer

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 Deliverability Engineer

Templates, a drag-and-drop editor, more than 60 prebuilt flows across email, SMS and push, and segmentation that is genuinely deep — real-time updates, unlimited conditions, behavioural and custom-property dimensions, ML-driven grouping — are all documented. We found no public information on A/B testing, branching journeys, dynamic content per segment or send-time optimisation, so I cannot credit the top of the range. 6 11 2

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 Deliverability Engineer

A public deliverability guide documents bounce types as seen in the product, spam traps, blacklists and list hygiene, dedicated IP warm-up is documented at 30 days, and the guidance that 1 complaint per 1,000 messages is where mailbox providers consider the complaint level elevated is honest, useful material. We found no public information on SPF, DKIM or DMARC setup documentation, inbox-placement or seed testing, or an engagement-based sunsetting policy, so the authentication spine is a topic heading rather than shown setup documentation. 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 Deliverability Engineer

Every form submission is automatically timestamped and version-labelled to form a consent log, consent forms can be geo-targeted to EU and UK visitors only, profiles without valid consent can be suppressed, and built-in tools export or delete a person's data with a deleted-profile list kept as proof of compliance. We found no public information on tracking that can be limited or switched off, on double opt-in as the documented default, or on unsubscribe handling honoured across lists. 8 4 7

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 Deliverability Engineer

Individual records can be found, exported and deleted on demand, the contract commits Klaviyo to deleting all further copies within 90 days of termination, and a deletion log evidences that deletion requests were honoured. We found no public information on bulk export of subscribers with engagement history, campaigns or templates in open formats, or on import with attributes intact — the exit story is contract language, not a documented feature. 8 5 4 1

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 Deliverability Engineer

More than 350 maintained integrations, a native Shopify partnership, and APIs, webhooks, SDKs and warehouse syncs are documented, which covers a real build surface. But rate limits are stated only as set and enforced at Klaviyo's sole discretion, we found no public information on webhook retries or a sandbox, and the terms reserve termination of API access at any time for any reason — that is a surface a sender builds on at the vendor's pleasure. 11 1 10

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 Deliverability Engineer

The contracting entity is Klaviyo, Inc. of Boston, the data processing agreement permits storing and processing customer data wherever Klaviyo or its subprocessors maintain facilities, and transfers rest on the EU-US Data Privacy Framework and standard contractual clauses — a Schrems II argument every EU buyer must make, with the agreement even contemplating FISA 702 and Executive Order 12333 requests. We found no public information on an EU hosting option, and data residency and ownership are unconfirmed on the vendor's own captured pages; a subprocessor list is published at a Klaviyo URL. 10 5 3 1 4

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 Deliverability Engineer

The free tier is fully quantified publicly — up to 250 active profiles, 500 emails per month, mobile messaging worth 5 $ per month and Composer usage worth 5 € per month — and paid tiers are stated to carry no send or profile limits after upgrading. But the captured pricing page states no paid prices at all: paid subscriptions are described only as scaling by contact count and channels with enterprise on custom quote, and we found no public information on overage rates, VAT treatment, or what a given list size would actually pay. 2 1 1 2

Report an error

European sovereignty — proven facts

0 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	Not determined ⚠ unverified	—	uncited Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	Not determined ⚠ unverified	—	uncited Report an error
Subprocessors	Not determined	—	uncited Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 30 Aug 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, Data residency. 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.

45 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
19 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
13 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
4 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
3 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 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 legal 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 hosting 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 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us

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

Sources (11)

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

1 Vendor homepage www.klaviyo.com Checked 5 Oct 2026 +3 earlier captures: 16 Sep 2026, 11 Sep 2026, 30 Aug 2026 Details →
2 Pricing www.klaviyo.com Checked 5 Oct 2026 +4 earlier captures: 28 Sep 2026, 16 Sep 2026, 11 Sep 2026, 30 Aug 2026 Details →
3 Privacy policy www.klaviyo.com Checked 5 Oct 2026 +1 earlier capture: 28 Sep 2026 Details →
4 Security / trust page www.klaviyo.com Checked 5 Oct 2026 Details →
5 Legal notice www.klaviyo.com Checked 5 Oct 2026 Details →
6 Campaigns & automation — found from sitemap www.klaviyo.com Checked 5 Oct 2026 Details →
7 Deliverability infrastructure — found from sitemap www.klaviyo.com Checked 5 Oct 2026 Details →
8 Consent, proof & tracking limits — found from sitemap www.klaviyo.com Checked 5 Oct 2026 Details →
9 Consent, proof & tracking limits — found from sitemap www.klaviyo.com Checked 5 Oct 2026 Details →
10 Integrations & API — found from sitemap www.klaviyo.com Checked 5 Oct 2026 Details →
11 Integrations & API — found from sitemap www.klaviyo.com Checked 5 Oct 2026 Details →