Email Marketing & Newsletter
Klaviyo
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Klaviyo, Inc. · www.klaviyo.com
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 panel's verdict
Klaviyo scored strongest on campaign automation and integrations: real-time segmentation with unlimited conditions, no lookback limits and predictive values such as churn risk and lifetime value, more than 60 prebuilt flows, more than 150 email templates, and more than 350 prebuilt integrations with a native Shopify relationship. The weakest scores are pricing transparency, range 2 to 2 — the captured pages state no paid prices, only scaling by contact count and channels with a custom enterprise quote — and sovereignty: Klaviyo, Inc. of Boston is the contracting entity, the processing agreement permits storage wherever Klaviyo or its subprocessors maintain facilities, and transfers rest on the EU-US Data Privacy Framework and standard contractual clauses. The splits are genuine: deliverability divides over how far the published guide and 30-day dedicated-IP warm-up carry the case when no public information exists on SPF, DKIM or DMARC setup, and consent and proof divides over the weight of the timestamped, version-labelled consent log against no public information on double opt-in defaults, unsubscribe handling or switching off open and click tracking.
Speaks for it
- Real-time segmentation with unlimited conditions, no lookback limits and predictive values such as churn risk, lifetime value and next order date
- More than 350 prebuilt integrations with a native Shopify relationship, plus APIs, webhooks, SDKs and warehouse syncs
- A kept list of deleted profiles as proof of deletion, alongside a contractual commitment to delete remaining copies within 90 days of termination with return on request
- A free tier precisely quantified at up to 250 active profiles, 500 emails per month, mobile messaging worth 5 $ per month and 10,000 Composer credits
Held against it
- Captured pricing pages state no figures for paid tiers, which are described only as scaling on contact count and channels with a custom enterprise quote
- Klaviyo, Inc. of Boston is the contracting entity and the processing agreement permits storage and processing wherever Klaviyo or its subprocessors maintain facilities, with no public information on EU hosting
- Lawful transfers rest on the EU-US Data Privacy Framework and standard contractual clauses, and the agreement contemplates requests under FISA Section 702 and Executive Order 12333
- API terms set rate limits in Klaviyo's sole discretion and reserve the right to modify or terminate API access at any time without notice
- No public information on SPF, DKIM or DMARC setup, on A/B testing or send-time optimisation, or on switching open and click tracking off
Best for
- You run a Shopify or e-commerce store and want lifecycle marketing across email, SMS and push driven by purchase history and predictive segments
- You need consent you can prove: timestamped, version-labelled form submissions, suppression by consent status and a log of deleted profiles
- You want to start free at up to 250 active profiles and 500 emails per month before any spend
Avoid if
- You must compute a paid invoice from public prices before committing — the captured pages state no paid prices, overage rates or VAT treatment
- Your procurement requires EU hosting or an EU contracting entity — the captured pages give no public information on either, and transfers rest on the EU-US Data Privacy Framework and standard contractual clauses
- Your core operations build on the APIs and cannot accept rate limits set at Klaviyo's sole discretion or termination of access at any time without notice
The scores
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 — 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.
The CRM Manager
Behavioural segmentation is the strongest thing on these pages: real-time segments on purchase history, browsing, predictive churn risk, CLV and next order date, unlimited conditions, no lookback limits, plus 60+ prebuilt flows and 150+ templates across email, SMS and push. What I found no public information on is A/B testing of any kind, journey branching, or holdout groups for measurement — the parts a lifecycle programme is actually judged on. 6 11 2
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
The Data Protection Officer
Segmentation is the documented strength: real-time segments on demographics, browsing behaviour, purchase history and custom properties with unlimited conditions, plus predictive and AI-generated segments, alongside 60+ prebuilt flows and 150+ email templates on a drag-and-drop editor. We found no public information on A/B testing with significance reporting, journey branching on behaviour and data, or send-time optimisation, so this sits above basic list-and-welcome tooling but well short of a fully evidenced journey platform. 6 11 2
The Shop Owner
The segmentation is genuinely built for a shop — purchase history, browsing behaviour, RFM groupings and predictive values like churn risk and next order date, with real-time updates and unlimited conditions — plus 'über 60 vorkonfigurierte Flows', more than 150 email templates and a drag-and-drop editor. We found no public information on a visual journey builder with branching, send-time optimisation or A/B testing of any kind, which is a real gap when the newsletter is a revenue channel. 6 11 2
The Integrator
Segmentation runs deep — unlimited conditions across behaviour, purchase history and predictive scores such as churn risk and lifetime value, real-time segment updates, and more than 60 prebuilt flows across email, SMS and push on top of more than 150 email templates. What holds it back is the testing half of the story: we found no public information on A/B testing, send-time optimisation or holdout groups. 6 11
The Skeptic
150+ email templates and 60+ prebuilt flows across email, SMS and push, with segmentation on attributes, behaviour and predictive values that updates in real time and unlimited lookback, is genuinely above the midpoint — but we found no public information on subject-line A/B testing, send-time optimisation or journey branching, so the top half of the ladder stays out of reach. 6 11 2
Deliverability infrastructure
panel disagrees
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 — 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.
The CRM Manager
The published guide covers bounce types, spam traps and blacklists, sending infrastructure, the complaint rate mailbox providers treat as elevated (1 in 1,000), and a 30-day dedicated-IP warm-up — more documented hygiene than most vendors show. But I found no public information on SPF, DKIM or DMARC setup, custom sending domains, or automatic hard-bounce suppression, so the authentication layer of the story rests on nothing quotable. 7
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
The Data Protection Officer
There is a real public deliverability guide covering bounce types and where they are found in the product, spam traps and blacklists, sending infrastructure and the pros and cons of double opt-in, plus guidance that one complaint per 1,000 messages is where mailbox providers consider a sender elevated and a documented 30-day dedicated-IP warm-up. We found no public information on SPF, DKIM or DMARC setup documentation, automatic hard-bounce suppression, or complaint-loop handling, which is what would raise this further. 7
The Shop Owner
There is a real deliverability guide covering bounce types in the product, spam traps, blacklists and sending infrastructure, a documented dedicated-IP warm-up of '30 days', and the guidance that 1 complaint per 1,000 messages already marks complaint levels as elevated. We found no public information on SPF, DKIM or DMARC setup, custom sending domains or automatic hard-bounce suppression, so the documented picture sits between the basics and proper infrastructure. 7
The Integrator
There is a published deliverability guide covering bounce types, spam traps and blacklists, and it documents a 30-day dedicated-IP warm-up plus the complaint-level maths mailbox providers apply. We found no public information on SPF, DKIM or DMARC setup, custom sending domains, automatic bounce suppression or complaint-loop handling, which is the documented baseline this buyer expects before anything else counts. 7
The Skeptic
There is real documentation here, not just a marketing number: a deliverability guide covering bounce types, spam traps, blacklists and sending infrastructure, a 30-day dedicated-IP warm-up, and the 1-complaint-per-1,000-messages threshold — but the captured pages show no SPF, DKIM or DMARC setup guidance, no custom sending domain and no stated hard-bounce suppression policy, so it sits at the lower rung with dedicated-IP documentation as the one bright spot. 7
Consent, proof & tracking limits
panel disagrees
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 — 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.
The CRM Manager
Consent is treated seriously: signup forms geo-targeted to EU and UK visitors, every form submission automatically timestamped and version-labelled into a consent log, segmentation by consent status, suppression of profiles without valid consent, and per-person export and deletion tools. I found no public information on double opt-in as a product default, one-click unsubscribe across lists, or turning open and click tracking off — pixel-free sending is likewise not something the captured pages describe. 4 8 7
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
The Data Protection Officer
But we found no public information on double opt-in being offered as a documented default (the deliverability guide only weighs its pros and cons), on open and click tracking being limitable or switchable off, on pixel-free sending, or on preference-centre granularity and retention rules for inactive subscribers. 4 8 7
The Shop Owner
We found no public information on double opt-in as the documented default, one-click unsubscribe for my subscribers, or any way to limit or switch off open and click tracking, so the proof side is stronger than the arrival and tracking side. 8 4
The Integrator
Every form submission is automatically timestamped and version-labelled into a consent log, contacts can be segmented and suppressed by consent status, and built-in tools export or delete a person's data with a list of deleted profiles kept as proof. We found no public information on double opt-in being the documented default, on product-level unsubscribe handling, or on any way to switch open and click tracking off. 4 8 7
The Skeptic
Form submissions are automatically timestamped and version-labelled into a consent log, contacts can be segmented and suppressed by consent status with EU/UK geo-targeted forms, and per-person export and deletion tools exist — that is a serious consent record — but we found no public information on double opt-in as a documented default, on unsubscribe handling, or on any way to switch off open and click tracking, while analytics data is stated to be processed with generative AI and machine learning. 4 8 3
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 — 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.
The CRM Manager
Individual records in the unified profiles can be found, exported and deleted, a list of deleted profiles is kept as proof of deletion, and the data processing agreement commits to deleting remaining copies within 90 days of contract end with return on request. What I found no public information on is bulk export of engagement history, campaigns and templates in open formats, or migration tooling — so exit looks per-person rather than per-account. 4 5 8
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
The Data Protection Officer
Exit hygiene is contractually documented: all customer personal data is deleted within 90 days of termination with return on request, individual profiles can be found, exported or deleted from the unified profile store, and the deletion log doubles as evidence of compliance. We found no public information on bulk export of the full list with custom attributes, engagement history or unsubscribe state, on campaigns and templates leaving in open formats, or on migration tooling in either direction — the parts that keep the list portable while the sender is still a customer. 5 4 8
The Shop Owner
Per-person export and per-profile deletion are built in, deletion is evidenced by a kept list of deleted profiles, and the data-processing agreement commits to deleting all copies 'innerhalb von 90 Tagen' after the contract ends with return on request. We found no public information on bulk or full-account export, whether engagement history and unsubscribe state travel with the subscribers, or on import and any export throttling, so I cannot confirm the list and its history remain fully mine on the way out. 4 5 8
The Integrator
Exit is half-documented: profiles can be exported and deleted individually, the processing agreement commits to deleting customer data within 90 days of termination with return on request, and APIs, webhooks and warehouse syncs are offered for syncing elsewhere. We found no public information on bulk import, full-fidelity export including engagement history, or any statement on export throttling. 4 5 1
The Skeptic
Individual profiles can be exported and deleted, a list of deleted profiles is kept as proof, and the data processing agreement commits to deleting remaining copies within 90 days of termination with return on request — but we found no public information on bulk export of engagement history, campaigns or templates, or on whether export is throttled, and the only documented return right is the contractual one. 4 5 8
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 — 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.
The CRM Manager
The connection surface is real: more than 350 prebuilt integrations, a native Shopify integration used by 117,000+ Shopify customers, and developer tools spanning APIs, webhooks, SDKs and warehouse syncs. But the API terms set rate limits at Klaviyo's sole discretion, reserve the right to modify the APIs or cease support without notice, and allow termination at any time for any reason — I found no public information on documented rate limits, a sandbox, or a deprecation policy, and building a programme on those terms is a risk I would have to price in. 11 1 10
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
The Data Protection Officer
The surface is broad: more than 350 prebuilt integrations, a native and maintained Shopify partnership claimed across 117,000+ shared customers, and developer tooling spanning APIs, webhooks, SDKs and warehouse syncs. It falls short of the top tier because rate limits are set and enforced at the vendor's sole discretion rather than documented, we found no public information on a sandbox or webhook retries, and the API terms reserve the right to modify or stop supporting the APIs at any time without notice. 11 1 1 10
The Shop Owner
This is where a shop gets connected: a native Shopify integration with Klaviyo as 'der bevorzugte E-Mail-Plattform-Partner von Shopify' used by 'über 117.000 Shopify-Kunden', more than 350 prebuilt integrations, and developer tools spanning APIs, webhooks, SDKs and warehouse syncs. It stops short of the top because rate limits are 'set and enforce... in our sole discretion' rather than documented, we found no public information on webhook retries or a sandbox, and the API terms reserve the right to modify or terminate API access at any time without notice. 11 1 10
The Integrator
The connection surface is broad — a native Shopify integration, more than 350 prebuilt integrations, APIs, webhooks, SDKs and warehouse syncs — but I cannot build on it with confidence: the API terms set rate limits "in our sole discretion", allow the APIs to be modified or unsupported "at any time without notice", and permit suspension of API access without notice. We found no public information on a sandbox, webhook retries or a deprecation policy. 1 10 11
The Skeptic
350+ prebuilt integrations, a native Shopify relationship claimed as the preferred email platform partner, and a developer surface of APIs, webhooks, SDKs and warehouse syncs clear the middle anchor — but the API terms reserve the right to modify or terminate API access without notice and set rate limits in Klaviyo's sole discretion, and we found no public information on documented rate limits, a sandbox, or webhook retries. 1 11 1 10
European sovereignty
panel opinion
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.
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.
The CRM Manager
Klaviyo, Inc. of Boston is the contracting entity, the agreement permits storing and processing customer data wherever Klaviyo or its subprocessors maintain facilities, and lawful transfers rest on the EU-US Data Privacy Framework and standard contractual clauses. A subprocessor list is published and transfer-impact-assessment support is offered, but I found no public information on EU hosting, an EU contracting entity, or where subscriber data and behavioural tracking actually reside — weighed heavily as this buyer weighs it, that sits near the bottom. 5 3 4 8
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
The Data Protection Officer
The contracting entity is Klaviyo, Inc. of Boston under Massachusetts law, and the data processing agreement authorises storage and processing wherever Klaviyo or its subprocessors maintain facilities — worldwide, with no regional lock — so behavioural data on EU subscribers is processed in the United States. Transfers rest on the Data Privacy Framework certification and standard contractual clauses with Irish governing law, transfer impact assessment support, a stated willingness to challenge FISA 702 and Executive Order 12333 requests, and a referenced published subprocessor list; that is the complete US-vendor transfer package, and it still requires a Schrems II argument to survive — we found no public information on any EU hosting or residency option. 3 5 10 1 4
The Shop Owner
The contracting entity is Klaviyo, Inc. of Boston, the API terms run under Massachusetts law, and the data-processing agreement permits storing and processing customer data wherever Klaviyo or its subprocessors maintain facilities, with transfers carried on the EU-U.S. Data Privacy Framework and standard contractual clauses. A published subprocessor list with 15 days' notice and transfer-impact-assessment support lift this above the bottom, but we found no public information on any EU hosting option or EU contracting entity, and as a buyer who weighs this heavily that decides it. 3 5 10
The Integrator
The contracting entity is Klaviyo, Inc. of Boston and the processing agreement permits storing customer data wherever Klaviyo or its subprocessors maintain facilities; we found no public information on EU hosting for any part of the chain, and the agreement even contemplates requests under FISA Section 702. Transfers rest on the EU-US Data Privacy Framework and standard contractual clauses under Irish law, which is precisely the Schrems II argument, and while a subprocessor list URL is referenced, we found no public information naming the subprocessors. 3 5 4
The Skeptic
The contracting entity is Klaviyo, Inc. of Boston, and the data processing agreement permits storage and processing anywhere Klaviyo or its subprocessors maintain facilities with no region lock, resting transfers on the EU-U.S. Data Privacy Framework and standard contractual clauses — every send is a Schrems II argument, with FISA 702 and Executive Order 12333 requests expressly contemplated; a published subprocessor list address and a stated transfer basis are the only things lifting this off the floor. 3 5 4
Pricing transparency
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 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.
The CRM Manager
The free tier is precisely quantified — up to 250 active profiles, 500 emails per month, mobile messaging worth 5 $ per month, Composer usage worth 5 € per month — but the captured pricing pages state no prices at all for paid tiers, only that they scale by contact count and channels with a custom enterprise quote. I cannot compute a real invoice for any list above 250: no contact-tier prices, no overage rates, no VAT treatment, and the promised absence of send or profile limits after upgrading is the only limit statement there is. 2 1 1 2
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
The Data Protection Officer
The free tier is fully computable — up to 250 active profiles, 500 emails per month, mobile messaging worth 5 $ per month and 10,000 Composer credits — but the paid tiers are described only as scaling on contact count and channels used, with enterprise on custom quote. We found no public information on any paid price figure, overage rate, feature boundary or VAT treatment, so a buyer cannot compute an invoice for a real list size from the captured pages. 2 2 1 1
The Shop Owner
The free tier is fully quantified — 'Bis zu 250 aktive Profile', '500 E-Mails pro Monat', 'Mobiles Messaging im Wert von 5 $/Monat' — and the paid model is described as scaling on contact count and channels, with AI-agent add-ons at '− 30 %'. But we found no public information on paid-tier prices, overage rates or VAT treatment, so I cannot compute the real invoice for my list size and send volume from public pages alone. 2 2 1 1
The Integrator
The free tier is precisely public — "Bis zu 250 Profile", "500 E-Mails pro Monat", mobile messaging worth "5 $/Monat" — but the captured pricing pages state no figures for paid tiers, which are described only as scaling on contacts and channels with a custom enterprise quote. We found no public information on paid-tier prices, overage rates or VAT treatment; the only calculator offered is for ROI. 2 2 1 1
The Skeptic
The free tier is exact and public — up to 250 active profiles, 500 emails per month, mobile messaging worth 5 $/Monat and 10,000 Composer credits — but the captured pricing pages state no paid prices at all, only that subscriptions scale with the number of contacts and channels used, enterprise is a custom quote, and there are no overage rates and no statement of VAT treatment; a buyer cannot compute a paid invoice from these pages. 2 2 1 1
European sovereignty — proven facts
0 of 4 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 |
|---|---|---|---|
| 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
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 →