Klaviyo (Automation)
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Klaviyo, Inc. · www.klaviyo.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Klaviyo (Automation) at a glance
- Vendor
- Klaviyo, Inc.
- Headquarters
- Incorporated in the United States source, captured 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 16 Sep 2026
- Panel verdict
- The AI panel rates Klaviyo (Automation) 2.5/5, the mean of 6 judges. Klaviyo's automation platform is a strong e-commerce lifecycle tool with one severe weakness. how scores are made
- As of
- Vendor pages captured 2 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Klaviyo's automation platform is a strong e-commerce lifecycle tool with one severe weakness. Channel coverage is the high point — the only criterion scored 7 by all six judges — with email, SMS, RCS, mobile push, WhatsApp and in-app messaging on a single customer profile, consent tracked per channel and behaviour-driven personalisation; we found no public information on ad-audience sync or cross-channel frequency capping. Journey orchestration scores run 6 to 7 on a documented visual flow builder, but nothing public covers frequency capping, priority when a contact qualifies for several flows, or versioning of a live journey. Lead management sits at 3 to 4: predictive churn, next-order and lifetime-value scores sit on profiles, but nothing public covers configurable scoring, routing or handover to sales. Sovereignty is uniformly 1 — Klaviyo, Inc. of Boston is the contracting entity, the processing agreement permits processing wherever Klaviyo or its subprocessors maintain facilities, and the privacy notice names the United States and United Kingdom as storage locations. Pricing transparency runs 5 to 6, and no flagged splits were flagged — no criterion spans more than a point.
Speaks for it
- Email, SMS, RCS, mobile push, WhatsApp and in-app messaging run from one customer profile with consent tracked per channel.
- Visual flow builder with real-time behaviour triggers, conditional splits, custom waits and A/B testing of flow logic.
- Webhook steps post to any API endpoint with automatic retry, delivery analytics and a testable request.
- Form submissions are timestamped and version-stamped into a consent log, with built-in export and deletion tools and a kept deletion list as proof.
- A free tier of up to 250 active profiles and 500 emails per month and a marketing plan at 25 USD per month are public, with automation reachable from the free account.
Held against it
- The contracting entity is Klaviyo, Inc. of Boston, the data processing agreement permits storage and processing wherever Klaviyo or its subprocessors maintain facilities, and the privacy notice names the United States and the United Kingdom as storage locations.
- EEA transfers rest on the EU-US Data Privacy Framework and standard contractual clauses, transfer-impact-assessment support is chargeable, and we found no public information on EU hosting or residency.
- We found no public information on configurable lead scoring, routing to sales owners or score history, and nothing public documents how the predictive scores are derived.
- We found no public information on frequency capping, priority when a contact qualifies for several journeys, or safe editing and versioning of a live journey.
- We found no public information on overage rates, onboarding fees, minimum term or VAT treatment, and above 150,000 active profiles the price is a sales conversation.
Best for
- You run an e-commerce brand and want welcome, abandonment, replenishment and win-back flows on one unified customer profile.
- You want a low-cost start: the free tier covers up to 250 active profiles and 500 emails per month and includes automation workflows.
- You need documented consent handling — timestamped, version-stamped consent logs, per-channel consent states and built-in export and deletion tools.
- Your personalisation runs on behaviour: product recommendations from purchase history, predicted send times and AI-chosen channel and message.
Avoid if
- You must keep EU-resident personal data within the EU — the documented chain runs through a US contracting entity with transfers on the EU-US Data Privacy Framework and standard contractual clauses.
- You need sales lead management — configurable scoring, routing to owners and handover with follow-up SLAs — rather than B2C lifecycle segmentation.
- You need to compute your annual invoice from public pages — we found no public information on overage rates, onboarding fees, minimum term or VAT treatment.
The scores
| Criterion | Panel median |
|---|---|
| Journeys & orchestration | 3 of 5 |
| Lead scoring, routing & lifecycle | 2 of 5 |
| Channels & personalisation | 3.5 of 5 |
| Consent, tracking & profiling | 3.5 of 5 |
| CRM integration & data model | 3 of 5 |
| European sovereignty | 0.5 of 5 |
| Pricing transparency | 3 of 5 |
Journeys & orchestration
Show reasoningHide reasoning
How this is scored
Multi-step automation: triggers, branching, waits, goals — and what happens when a contact qualifies for several journeys at once.
0 — No automation; the product sends one-off campaigns only.
3 — Autoresponders or linear sequences started by a trigger such as a sign-up or a tag, with waits between steps.
5 — A visual workflow builder with triggers on behaviour and attributes, if/else branching and waits, and goals or exit conditions that take a contact out of the flow.
8 — Event-driven entry from external systems through an API, frequency capping and suppression across journeys, priority when a contact qualifies for several, per-contact journey state and reporting per step, versioning or safe editing of a live journey, and testing against real records.
10 — Orchestration is coherent across the whole programme: one decision layer deciding what a person receives next regardless of which journey wants to send it, holdout groups for measurement, and journeys documented and readable months later.
The Demand Gen Lead
A visual drag-and-drop flow builder with behaviour-based triggers, conditional splits and custom waits is documented, and it goes past the basics: A/B testing of flow logic, revenue tracked per flow, AI choosing channel or message inside a multi-channel flow, and test requests against webhook steps. We found no public information on frequency capping across flows, priority when one contact qualifies for several at once, or versioning of a live journey — the controls that keep a programme honest at scale. 10 11 12 14
The Sales Ops Manager
The captured pages document a visual flow builder with event-based and real-time triggers, conditional splits and waits, webhook steps posting to any API with a testable request, per-flow revenue reporting, and AI choosing channel or message inside a flow — a serious workflow engine. We found no public information on what happens when one person qualifies for several flows at once, or on frequency capping and safe editing of a live journey, which is the conflict handling I would ask about first. 10 11 14 13
The Data Protection Officer
A visual flow builder with real-time behavioural triggers, conditional splits, custom waits and a template library is documented, and webhooks give event-driven entry outward to any API endpoint with automatic retry and a testable request. We found no public information on frequency capping across journeys, priority when a contact qualifies for several flows, or versioning of a live journey. 10 11 12 14
The Lifecycle Marketer
A visual flow builder with real-time behaviour triggers, conditional splits, custom waits and A/B testing of flow logic is documented, with event-driven entry and webhooks that can post out mid-journey — that clears the multi-step bar comfortably. What I could not find is anything on frequency capping across journeys, priority when one person qualifies for several, holdout groups for measurement, or versioning of a live journey, which is exactly the discipline a lifecycle programme runs on. 10 11 13 14 12
The Solution Architect
A visual drag-and-drop builder with real-time behaviour triggers, conditional splits, custom waits and A/B testing of flow logic is documented, and email, SMS, push, WhatsApp and in-app coordinate inside one flow, with webhooks as flow steps that retry on exponential backoff and log delivery. What I could not find is any governance across flows: we found no public information on frequency capping, suppression across journeys, priority when one contact qualifies for several, or safe editing and versioning of a live flow — the parts that bite at scale. 10 11 14
The Skeptic
The captured pages document a visual drag-and-drop flow builder with real-time behaviour triggers, conditional splits and custom waits, webhook steps that POST to any API endpoint with a testable request, and A/B testing of flow logic with revenue tracked per flow. The question that decides real programmes — what happens when one contact qualifies for several flows at once — goes unanswered: I found no public information on frequency capping, suppression across flows, per-step reporting or safe editing of a live flow. 10 11 14 12
Lead scoring, routing & lifecycle
Show reasoningHide reasoning
How this is scored
Scoring, qualification and handover to sales — including whether the customer can explain to a lead why the system decided what it decided.
0 — No scoring, lifecycle or lead handling at all; the product is a sending tool for lists.
3 — A rule-based lead score from attributes or engagement, or lifecycle stages set by tags or fields.
5 — Configurable lead scoring on attributes and behaviour, lifecycle or pipeline stages, and qualified leads assigned or notified to sales.
8 — Multiple scoring models per product or region, negative scoring and score decay, account-level scoring alongside contact-level, routing rules to owners or teams with follow-up SLAs, and score history visible per contact.
10 — Scoring is explainable and accountable: the contribution of each signal visible per record, model changes versioned with their effect on the funnel, routing rules auditable, and predictive scoring — where offered — documented well enough for a DPO to assess it as automated decision-making.
The Demand Gen Lead
Segments of first-time buyers, repeat customers and VIPs sort themselves from live purchase and browsing behaviour, and each profile carries predictive churn risk, lifetime value and a predicted next order date — a behavioural layer sales can actually read. We found no public information on configurable scoring models, routing rules to owners or teams with follow-up SLAs, or score history per contact. 12 11 8
The Sales Ops Manager
Predictive churn risk, next order date and lifetime value sit on each profile, and value segments update themselves from live purchase and engagement data — but that is model scoring for marketing, not lead handling. We found no public information on configurable lead scoring, routing rules to sales owners or teams, follow-up SLAs, or score history per contact. The positioning as an autonomous B2C CRM does not by itself evidence a sales handover. 8 11 12
The Data Protection Officer
Predictive churn risk, next order date and lifetime value sit on individual named profiles and auto-updating segments sort first-time, repeat and VIP customers, but we found no public information on configurable lead scoring, lifecycle stages or handover to sales. Nothing public documents how the predictive scores are derived, which is what I would need before assessing automated scoring of individuals. 8 12 11
The Lifecycle Marketer
Lifecycle thinking is present as auto-updating behavioural cohorts — first-time buyers, repeat customers and VIPs sort themselves — plus predictive churn risk, next order date and lifetime value on each profile, and win-back flows keyed to them. We found no public information on a configurable lead score, qualification rules, or handover and routing to sales owners, so this reads as lifecycle segmentation rather than lead management. 12 8 11
The Solution Architect
Lifecycle exists as auto-updating segments of first-time, repeat and VIP buyers plus templated welcome, abandonment, replenishment and win-back flows, with predictive churn risk, next order date and lifetime value computed per profile. But we found no public information on configurable lead scoring, qualification handover to sales, routing rules or per-record score history — and the per-signal explainability a DPO would ask about for the predictive scores is not documented either. 8 12 11
The Skeptic
This is lifecycle marketing for e-commerce, not a sales handover machine: segments auto-sort first-time buyers, repeat customers and VIPs, and predictive churn risk, next order date and lifetime value are computed onto each profile. I found no public information on configurable scoring models, negative scoring, decay, routing to owners or score history, and I found no public information on how each signal contributes to the predictive values. 12 8 11
Channels & personalisation
Show reasoningHide reasoning
How this is scored
What the platform can send and personalise — email, SMS, push, on-site content, ad audiences — judged on what shares one profile and one suppression list.
0 — Not a sending platform; the product cannot deliver messages on any channel.
3 — Email with merge-field personalisation, plus sign-up forms or landing pages.
5 — Email plus at least one further channel (SMS, push, or ad-audience sync) driven from the same contact profile, and dynamic content blocks based on contact data.
8 — Email, SMS and push from one profile with shared unsubscribe handling, on-site personalisation, ad-audience sync to the major networks, cross-channel frequency capping, and content personalised on behaviour rather than only on stored fields.
10 — Channel is a delivery detail: one profile and one consent state across every channel, next-best-channel selection, and personalisation that draws on the full behavioural record without the marketer assembling it by hand.
The Demand Gen Lead
Email, SMS, RCS, mobile push, WhatsApp and web events are documented on one customer profile, consent is tracked per channel, and personalisation runs on behaviour — SMS early access only to email clickers, AI selecting which channel and message per person, per-subscriber optimal send time. We found no public information on cross-channel frequency capping or ad-audience sync, so the top of this scale stays out of reach. 1 11 13 8 3
The Sales Ops Manager
Email, SMS, RCS, mobile push, WhatsApp and in-app messages all run from one customer profile, with consent tracked separately per channel and an SMS STOP keyword, and personalisation draws on purchase history and live web behaviour rather than stored fields alone. AI even decides within a flow which channel and message a person receives. We found no public information on ad-audience sync to the major networks or cross-channel frequency capping. 1 8 11 13 3
The Data Protection Officer
Email, SMS, RCS, mobile push, WhatsApp and web events run in one customer profile with per-channel consent status visible per profile, and personalisation is behavioural — product recommendations from purchase history, predicted send times and AI choosing the channel within a flow. We found no public information on ad-audience sync or cross-channel frequency capping. 1 8 11 13 8
The Lifecycle Marketer
Email, SMS, RCS, mobile push, WhatsApp and in-app are documented as running from one profile with one per-channel consent state, and personalisation — recommended products, predicted send time, even which channel carries the next message inside a flow — draws on the behavioural record rather than hand-assembled merge fields. We found no public information on ad-audience sync to the major networks or cross-channel frequency capping, which keeps it short of the top band. 11 13 1 8 3
The Solution Architect
Email, SMS, RCS, push, WhatsApp and in-app all run from one customer profile with consent status tracked per channel, and personalisation runs on behaviour: product recommendations per profile, SMS early access sent only to email clickers, and AI choosing which channel and message each person receives. The gaps are ad-audience sync and cross-channel frequency capping — we found no public information on either. 1 11 13 8
The Skeptic
Email, SMS, RCS, push, WhatsApp and in-app are all stated to run on one customer profile, with consent tracked per channel inside that profile and personalisation driven by behaviour — per-profile product recommendations, AI-chosen send times, and AI picking channel and message within a multi-channel flow. I found no public information on ad-audience sync to the major networks, on-site personalisation or cross-channel frequency capping. 13 1 11 8
Consent, tracking & profiling
Show reasoningHide reasoning
How this is scored
The platform builds behavioural profiles of named people. Consent capture and proof, tracking that can be limited, retention, and whether automated decisions about individuals are documented and contestable.
0 — The vendor states a practice that defeats consent, such as importing purchased lists or tracking named contacts with no opt-in mechanism at all.
3 — Double opt-in available and unsubscribe handled per contact.
5 — Double opt-in with the consent timestamp and source stored per contact, consent or subscription status per channel, and a documented way to answer access and erasure requests.
8 — Consent reproducible as evidence with the wording versioned, tracking switchable per contact or a cookieless or first-party tracking mode, profiling suppressible per person, retention for inactive records stated and executed per data category, and erasure covering derived scores.
10 — Built for the accountability principle: a per-contact history of what was tracked, scored and decided, automated decision-making documented well enough to support an Art. 22 DSGVO assessment, profiling off by default for anyone who has not consented to it, and deletion that removes derived scores as well as raw events.
The Demand Gen Lead
Every form submission is automatically timestamped and version-stamped as a consent record, consent status is visible per channel in each profile, contacts without valid consent can be suppressed, and built-in tools export a person's data and delete profiles with a kept list of deletions as proof. We found no public information on switching tracking off per contact, suppressing profiling per person, or erasure that covers derived scores such as churn risk. 7 8 8 5
The Sales Ops Manager
Every form submission is timestamped and version-stamped into a consent log, consent is tracked per channel, profiles without valid consent can be suppressed, and built-in tools handle export and deletion with a kept list of deleted profiles as proof. Server-side tracking keeps activity up to a year, and anonymous browsing is captured and backfilled onto the profile at signup. We found no public information on erasure covering the derived predictive scores, on a per-contact switch for tracking, or on suppressing profiling per person. 7 8 8 3 7
The Data Protection Officer
Form submissions are timestamped and version-stamped so consent is reproducible per person, profiles without valid consent can be suppressed, built-in tools export and delete a profile with a deletion list kept as proof, and server-side tracking retention is stated at up to a year. We found no public information on a per-contact tracking switch, suppression of profiling per person, or erasure covering derived scores; anonymous activity is captured before identification and backfilled at sign-up, which reads as tracking on by default. 7 8 8 7 4
The Lifecycle Marketer
Every form submission is timestamped and version-stamped into a consent log, consent is tracked per channel in each profile, profiles without valid consent can be suppressed, and built-in export and deletion tools leave a list of deleted profiles as proof. On the other side of the ledger, tracking runs by default — anonymous journeys are captured and backfilled at sign-up, with server-side activity kept up to a year — and we found no public information on a per-contact tracking switch, a cookieless mode, or erasure covering derived scores such as churn risk. 7 8 8 7 3
The Solution Architect
Every form submission is timestamped and version-stamped into a consent log, consent sits per channel on the profile, profiles without valid consent can be suppressed, and built-in tools export and delete a person's data with a deleted-profile list kept as proof. Server-side tracking retention is stated at up to one year, but we found no public information on profiling being suppressible per person, on double opt-in, or on whether deletion covers the derived churn and lifetime-value scores. 7 8 8 4
The Skeptic
Consent is the best-documented area here: every form submission is timestamped and versioned into a consent log, consent status sits per channel on the profile, profiles without valid consent can be suppressed, and built-in tools export a person's data and delete the profile with a deletion list kept as proof. Server-side tracking retention is stated at up to twelve months and the data processing agreement fixes deletion within ninety days of contract end. I found no public information on switching tracking off per contact, suppressing profiling per person, or whether erasure reaches the derived scores. 7 8 8 5
CRM integration & data model
Show reasoningHide reasoning
How this is scored
The join that decides the implementation: how the platform and the CRM stay in agreement about who a person is, and what happens when they disagree.
0 — No way to get contact data in or out beyond typing it in.
3 — CSV import and export, and a sync or connector to a named CRM.
5 — Two-way sync with at least one major CRM (or a built-in CRM) with field mapping, duplicate handling, and a documented API.
8 — Configurable conflict resolution per field, account and contact objects both modelled, custom objects supported, near-real-time sync with retry and an error log, and API rate limits documented.
10 — One record, two systems, no ambiguity: identity resolution across anonymous and known states, field-level ownership defined per system, replay of failed syncs, and a data model the customer can extend without vendor services.
The Demand Gen Lead
A built-in B2C CRM unifies purchase, web and consent data into one live profile, merges cross-device duplicates automatically and backfills anonymous browsing once someone signs up, with native e-commerce syncs that include a full historical load and webhooks posting to any API endpoint with exponential-backoff retry and delivery analytics. We found no public information on field-level conflict resolution between systems, custom objects, or documented API rate limits. 13 8 9 14 1
The Sales Ops Manager
Klaviyo positions itself as the B2C CRM, merges duplicate profiles automatically across devices and backfills anonymous activity onto the known record — which addresses my duplicate problem, though we found no public information on the conflict rules behind that merge. Outbound webhooks post to any API, retry on exponential backoff and show delivery analytics for every request, and the Magento integration offers a full historical sync. We found no public information on field-level ownership between systems, configurable per-field conflict resolution, account objects, or documented API rate limits. 12 13 8 9 14 1
The Data Protection Officer
Identity resolution across anonymous and known states with automatic cross-device profile merging is documented, alongside a built-in B2C CRM, 400-plus integrations, APIs, webhooks, SDKs and warehouse syncs with configurable payloads, retry and delivery analytics. We found no public information on field-level conflict resolution with external CRMs, custom objects, or documented API rate limits. 8 14 1 12
The Lifecycle Marketer
Klaviyo presents itself as the CRM here: duplicate profiles merge automatically across devices, anonymous activity resolves into the known record, and updates land in real time, with webhooks that retry on failure with exponential backoff, report delivery success and can be test-fired against the connected system. We found no public information on configurable conflict resolution per field, field-level ownership between systems, account-level objects alongside contacts, or documented API rate limits, which is where the harder implementations get decided. 1 14 8 9 13
The Solution Architect
The anonymous-to-known path is documented and it is the good one: activity is captured before identification and the full history attaches on signup, duplicate profiles merge automatically even across devices, the Magento integration does a full historical sync, and webhooks post to any API endpoint with retries, delivery analytics and a test request. But the data model I would have to live in shows custom properties on profiles only — we found no public information on custom objects, account-level objects, configurable conflict resolution per field, or documented API rate limits. 8 9 14 1
The Skeptic
Klaviyo calls itself a B2C CRM, unifies purchase, web, consent and engagement data into one real-time profile, and documents identity resolution across anonymous and known states with automatic cross-device merges. Webhook deliveries retry with exponential backoff and expose delivery analytics, and payloads draw on custom fields; I found no public information on field mapping, per-field conflict resolution, account-level objects or documented API rate limits. 12 8 14 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where behavioural profiles of named EU residents are processed, who the contracting entity is, and which subprocessors see them. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which given the profiling is heavily. Dimensions the sources do not establish are unknown, not non-EU.
0 — Proven non-EU: a non-EU vendor and contracting entity with hosting and tracking stated outside the EU.
3 — One European element proven — an EU contracting entity or EU data residency stated — with the rest of the chain undocumented.
5 — An EU contracting entity and EU hosting both stated, and a data processing agreement offered.
8 — EU hosting on named infrastructure, EU contracting entity, a subprocessor list published with locations, and any non-EU processing (tracking, AI scoring, support access) named with its legal basis.
10 — Sovereign end to end and evidenced: every profile, event and derived score processed in the EU by European subprocessors, certification published, and no transfer requiring a Schrems II argument to survive.
The Demand Gen Lead
The contracting entity is Klaviyo, Inc. of Boston, the processing agreement permits storage wherever Klaviyo or its subprocessors maintain facilities, and the privacy notice names the United States and the United Kingdom as transfer and storage locations; for EU-origin data the documented safeguards are the Data Privacy Framework, standard contractual clauses, a published subprocessor list and transfer-impact support on request. We found no public information on a European contracting entity or EU hosting — for behavioural profiles of named EU residents that defence sits with the buyer. 5 3 3 7
The Sales Ops Manager
The contracting entity is Klaviyo, Inc. of Boston, and its data processing agreement permits storage and processing wherever Klaviyo or its subprocessors maintain facilities, with no regional restriction; the privacy notice names the United States and the United Kingdom as storage locations. Transfers out of the EEA rest on the Data Privacy Framework and standard contractual clauses, and AI content is sent to OpenAI, Anthropic and Google. For behavioural profiles of named EU residents, that is a chain I would have to defend with transfer mechanisms rather than locality. 5 3 3 1
The Data Protection Officer
The contracting entity is Klaviyo, Inc. of Boston, the data processing agreement permits processing wherever Klaviyo or its subprocessors maintain facilities, and EEA-origin data is transferred on the EU-US Data Privacy Framework or standard contractual clauses, with the privacy notice naming the United States and United Kingdom as storage locations. Transfer impact assessment support is chargeable and audits run at the customer's cost including reimbursement of Klaviyo's time; no European element in the chain is proven on the captured pages. 5 3 7 3
The Lifecycle Marketer
The contracting entity is Klaviyo, Inc. in Boston, the processing agreement permits storage and processing wherever Klaviyo or its subprocessors maintain facilities, and the privacy notice names the United States and the United Kingdom as storage locations. Transfers out of the EEA rest on the EU-US Data Privacy Framework and standard contractual clauses with a published subprocessor list that includes US AI providers; for a platform profiling named EU residents at this scale, I found nothing establishing EU residency anywhere in the chain. 5 3 7 3 3
The Solution Architect
The contracting entity is Klaviyo, Inc. of Boston, the processing agreement permits storage and processing wherever Klaviyo or its subprocessors have facilities, and the privacy notice names the United States and the United Kingdom as storage locations, with content also going to AI providers OpenAI, Anthropic and Google. For profiles of EU residents this is a transfer case resting on the Data Privacy Framework and standard contractual clauses; the published subprocessor list and chargeable transfer-impact support document the transfer rather than replace it. 5 3 3 7
The Skeptic
The contracting entity is Klaviyo, Inc. of Boston, and the data processing agreement permits storage and processing wherever Klaviyo or its subprocessors maintain facilities, with transfers from the EEA carried on the EU-US Data Privacy Framework and standard contractual clauses. The privacy notice states personal information may be transferred to and stored in the United States and the United Kingdom; no captured page claims EU hosting or residency. A subprocessor list is published and transfer-impact-assessment support exists at a charge, but for a platform profiling named EU residents this is a non-EU chain as documented, carried on Schrems II machinery rather than avoiding it. 5 3 3 7
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their contact base and send volume — including the tier where automation actually begins, overage, and mandatory onboarding — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or a single tier with its contact limit.
5 — Prices per tier public with the billing period and contact limits stated, and which tier includes automation visible.
8 — Every tier priced publicly with contact and volume limits, feature boundaries, overage rates, onboarding costs, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given contact count, send volume and feature set, including overage, additional users and any implementation fee stated outright.
The Demand Gen Lead
Public pages show the free tier at 250 profiles and 500 emails a month, a 25 USD per-month marketing plan with its profile and email limits, automation available from the free account, and fixed add-on prices — 5 USD a month for Composer or mobile messaging and 15 USD for 1,000 US mobile messages. We found no public information on tier prices across the range up to 150,000 profiles, email overage, onboarding costs, minimum term or VAT treatment, so the annual invoice cannot be computed; the captured pages also give different figures for the free subscription and its currency. 2 2 6 10 1
The Sales Ops Manager
The captured pricing pages give different pictures of disclosure — some show only an unanswered question about cost, while a later capture shows a free tier of 250 profiles and 500 emails per month, a 25 USD per month marketing plan, add-ons at 5 $ per month for Composer and for mobile messaging, and US SMS at 15 USD per 1,000 messages. Automation is visible from the free tier, and beyond 150,000 active profiles everything is a sales conversation. We found no public information on overage rates, onboarding costs, minimum term or VAT treatment, so the annual invoice for a given contact base is not computable from these pages. 2 2 6 1 1
The Data Protection Officer
The pricing page shows a free tier at up to 250 active profiles and 500 emails per month, paid tiers with their profile and email limits, automation reachable from the free account, SMS at 15 USD per 1,000 messages for the United States and add-ons at 5 $ pro Monat. We found no public information on overage rates, onboarding fees, minimum term or VAT treatment, and the public tiers end at 5,000 active profiles with a custom sales conversation only above 150,000. 2 2 2
The Lifecycle Marketer
The free tier's limits (up to 250 active profiles and 500 emails per month) and a marketing plan at 25 USD per month with 500 active profiles and 5,000 emails are public, automation is visible from the free subscription, and US mobile messaging is priced at 15 USD per 1,000 messages a month. Above 150,000 active profiles the tier becomes a sales conversation, and we found no public information on overage rates, onboarding fees, minimum term or VAT treatment; the captured pages also give different figures for the free-subscription question, some showing the limits and some raising the question without an answer. 2 2 6 2
The Solution Architect
Tiers are public with limits — 250 profiles and 500 emails free, an email tier at 500 profiles and 5,000 emails, a marketing tier at 25 USD per month, add-ons at 5 USD, US messaging at 15 USD per 1,000 messages, and a custom tier above 150,000 profiles — and automation is visible from the free tier. The captured pages give different figures on whether paid tiers carry send and profile limits, and for a mid-size contact base the profile-tiered price, overage, onboarding, minimum term and VAT treatment cannot be derived from public pages. 2 2 6 11
The Skeptic
The public pricing pages give a free tier at 250 profiles and 500 emails a month, a marketing plan at 25 USD a month, an email tier at 500 profiles and 5,000 emails a month, add-ons at 5 USD a month, and US messaging at 15 USD per 1,000 messages — and automation workflows are reachable from the free account, so the automation staircase starts at zero. Above 150,000 active profiles the price becomes a conversation with the sales team, and I found no public information on overage rates, onboarding costs, minimum term or VAT treatment. The captured pages also give different figures for what limits apply after upgrading to a paid plan. 2 2 6 10
European sovereignty — proven facts
2 of 6 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 |
Incorporated in US
unverified
Why unverified?The page states only where Klaviyo, Inc. is located, not its place of incorporation or a commercial register. |
0/2 pts | 3 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The AVV text is posted in full but takes effect together with the master agreement rather than being concluded in a separate online flow. |
1/1 pts | 5 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Klaviyo (Automation)
Is Klaviyo (Automation) European?
No. whats-best.ai classifies Klaviyo (Automation) as Rest of world. Its vendor, Klaviyo, Inc., is incorporated in the United States, per the vendor’s page captured 16 Nov 2026.
Where does Klaviyo (Automation) store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Klaviyo (Automation) have a free plan?
Yes. Klaviyo (Automation) has a free plan, per the vendor’s page captured 16 Sep 2026.
What are the best alternatives to Klaviyo (Automation)?
As of 18 Nov 2026, the panel rates Braze (3/5), HubSpot Marketing Hub (3/5) and ActiveCampaign (Automation) (3/5) highest among the other 20 Marketing Automation products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Brevo (Automation) (EU-Made, France). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Klaviyo (Automation) alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 2 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 — Data processing agreement. The AVV text is posted in full but takes effect together with the master agreement rather than being concluded in a separate online flow.
- Weak sourcing — Legal entity. The page states only where Klaviyo, Inc. is located, not its place of incorporation or a commercial register.
- Weak sourcing — Hosting location. 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.
- 62 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
- 22 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
- 14 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
- 8 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
- 6 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
- 4 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 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
- 1 data 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.klaviyo.com Checked 16 Nov 2026 +7 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 19 Oct 2026, 16 Sep 2026, 11 Sep 2026, 2 Sep 2026 Details →
- 2 Pricing www.klaviyo.com Checked 16 Nov 2026 +4 earlier captures: 2 Nov 2026, 16 Sep 2026, 11 Sep 2026, 2 Sep 2026 Details →
- 3 Privacy policy www.klaviyo.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 16 Sep 2026 Details →
- 4 Security / trust page www.klaviyo.com Checked 16 Nov 2026 Details →
- 5 Legal notice www.klaviyo.com Checked 16 Nov 2026 Details →
- 6 Channels & personalisation — found from sitemap www.klaviyo.com Checked 16 Nov 2026 Details →
- 7 Consent, tracking & profiling — found from sitemap www.klaviyo.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 8 Consent, tracking & profiling — found from sitemap www.klaviyo.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 9 CRM integration & data model — found from sitemap www.klaviyo.com Checked 16 Nov 2026 Details →
- 10 Journeys & orchestration — found from sitemap www.klaviyo.com Checked 16 Nov 2026 +1 earlier capture: 8 Nov 2026 Details →
- 11 Journeys & orchestration — found from sitemap www.klaviyo.com Checked 16 Nov 2026 +1 earlier capture: 8 Nov 2026 Details →
- 12 Lead scoring, routing & lifecycle — found from sitemap www.klaviyo.com Checked 16 Nov 2026 +1 earlier capture: 8 Nov 2026 Details →
- 13 Channels & personalisation — found from sitemap www.klaviyo.com Checked 16 Nov 2026 +1 earlier capture: 8 Nov 2026 Details →
- 14 CRM integration & data model — found from sitemap www.klaviyo.com Checked 16 Nov 2026 +1 earlier capture: 8 Nov 2026 Details →