Marketing Automation
Klaviyo (Automation)
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
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, positioned as "the autonomous B2C CRM," is strongest on channels & personalisation: email, SMS, RCS, mobile push, WhatsApp and web events are stated to unite in a single customer profile, with native WhatsApp and SMS in the free tier. Its floors are lead scoring, routing & lifecycle — no scoring, lifecycle stage, decay or routing appears anywhere in the evidence — and sovereignty, a flat 1: the contracting entity is Klaviyo, Inc., hosting sits with an unnamed cloud hosting provider, processing runs through the United States and the United Kingdom, subprocessors are unnamed, and transfers rest on the EU-US Data Privacy Framework and SCCs. Journey orchestration rests on "Flows" named only as objects the AI Composer analyses. The judges' clearest split is consent, tracking & profiling: those crediting the DPA and self-service privacy-centre tooling scored high, those weighing the confirmed AI processing of personal data against absent consent records and per-contact suppression scored low. The free tier is concretely priced (up to 500 emails/month, $5 mobile messaging, 10,000 Composer credits); no paid figures exist. Persona-weighted totals span 1.7-3.4.
Speaks for it
- Email, SMS, RCS, mobile push, WhatsApp and web events stated to unite in a single customer profile (channels & personalisation 5-6)
- Native WhatsApp messaging built into the platform without third-party integrations
- 350+ prebuilt integrations including CRM connectors, plus APIs, webhooks, SDKs and warehouse syncs (CRM integration & data model 3-4)
- Free tier fully quantified: up to 500 emails/month, $5 mobile messaging, 10,000 Composer credits, 60 days of email support
- Self-service data-subject-request tools and a DPA with EU-US Data Privacy Framework and SCC transfer mechanisms stated
Held against it
- No lead scoring, lifecycle stages, decay or routing documented anywhere in the evidence (lead scoring, routing & lifecycle 0-1)
- 'Flows' evidenced only as objects the AI Composer analyses; branching, waits, entry/exit conditions and collision handling absent (journeys & orchestration 2-3)
- Contracting entity Klaviyo, Inc. with an unnamed cloud hosting provider, processing in the US and UK, and no subprocessor list captured (sovereignty 1)
- AI processing of personal data is confirmed with no consent-record mechanics, per-channel consent states or per-contact suppression evidenced (consent, tracking & profiling 2-4)
- No paid-tier figures: plans scale by contacts and channels and enterprise is custom-quoted
Best for
- You run B2C e-commerce and want email, SMS, RCS, push, WhatsApp and web events unified on one customer profile
- You want a concretely specified free start: up to 500 emails/month, $5 of mobile messaging and 10,000 Composer credits
- Your stack is built on e-commerce platforms like Shopify and you rely on 350+ prebuilt integrations and warehouse syncs
- You can accept a US contracting entity and US/UK processing under the stated EU-US Data Privacy Framework and SCCs
Avoid if
- You need lead scoring, lifecycle stages, decay or routing to a sales owner — ask the vendor: the public pages we read do not show it
- Your procurement requires confirmed EU data residency or a published subprocessor list — the evidence lists both as unknown, with processing in the US and UK (sovereignty 1)
- You must budget a paid tier in advance — ask the vendor: the public pages we read do not show it
- You depend on branching journeys with waits, entry/exit conditions and collision handling — ask the vendor: the public pages we read do not show it
The scores
Journeys & orchestration
Show reasoningHide reasoning
How this is scored
Multi-step automation: triggers, branching, waits, and — the part that decides whether it survives contact with reality — what happens when journeys collide.
0 — Autoresponders on a single trigger; no branching, no waits, no conditions.
3 — Linear sequences with simple conditions, one entry trigger per journey, and no visibility into where a contact currently sits.
5 — A visual builder with branching on attributes and behaviour, waits and goals, entry and exit conditions, and per-contact journey state visible.
8 — Event-driven entry from external systems, frequency capping and suppression across journeys, priority when a contact qualifies for several, versioning 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 a journey a colleague can read months later without a diagram.
The Demand Gen Lead
The evidence names 'Flows' only as something the AI agent analyses, and the closest hard evidence of automation is 'automatische Antworten in Social Media' on the free tier — autoresponder territory. Nothing on branching, waits, entry conditions, per-contact journey state, or what happens when two flows fight over one person; for a platform whose pitch is automation, that silence is information. 1 2
The Sales Ops Manager
The evidence names 'Flows' only in passing as something the AI Composer analyses, and otherwise talks about launching omnichannel campaigns — no triggers, branching, waits, entry/exit conditions, or per-contact journey state are evidenced anywhere. When journeys collide is exactly what I'd need documented before letting this near my pipeline, and the evidence is silent, so it sits at linear-sequence level at best. 1
The Data Protection Officer
"Flows" exist as an object the AI agent analyses and the free tier offers autoresponders and automatic social replies, but nothing evidences branching, waits, entry/exit conditions, per-contact journey state, or suppression when journeys collide. That sits between rubric level 0 and a linear rubric level 3. 1 2
The Lifecycle Marketer
Flows exist as objects the AI agent can analyse and omnichannel campaigns launch across email, SMS, push, WhatsApp and web, but the evidence says nothing about branching, waits, frequency capping across journeys, priority on collision, versioning or holdouts — the parts that decide whether automation survives contact with reality. Even linear-sequence structure is inferred from the word 'Flows' rather than evidenced, so this sits at the bottom of the linear band. 1 2
The Solution Architect
The evidence names 'Flows' and an AI agent that analyses them, but gives me nothing on triggers, branching, waits, entry/exit conditions, per-contact journey state, or — the part that decides survival — what happens when two flows want the same contact. That's the linear-sequence anchor at best, and even that is inferred from the word 'Flows' rather than evidenced. 1
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 or lifecycle model; every contact is treated alike.
3 — A single additive score with fixed rules, no decay, no lifecycle stages and no routing.
5 — Configurable scoring on attributes and behaviour with decay, lifecycle stages, and routing to owners or teams with notification.
8 — Multiple scoring models per product or region, negative scoring, account-level scoring alongside contact-level, SLA on follow-up, 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
Zero evidence of scoring, lifecycle stages, decay, or routing to an owner — the words do not appear anywhere in the registry. Best on offer is 'grundlegende Kundensegmentierung' on the free tier, which is targeting, not qualification, so sales would be trusting a number this sheet cannot show exists. 1 2
The Sales Ops Manager
Nothing here evidences scoring, decay, lifecycle stages, routing, or any handover to sales — the closest facts are basic segmentation, revenue attribution, and a vague line that data is 'processed using Artificial Intelligence'. For a product positioning itself as 'the autonomous B2C CRM', the absence of any lifecycle or scoring model in the evidence is the information. 1 2
The Data Protection Officer
No scoring model, lifecycle stage, decay, routing rule or SLA appears anywhere in the module list or the free-tier feature set. The positioning is an "autonomous B2C CRM" with no lead qualification or handover story at all — a clean rubric level 0. 1 2
The Lifecycle Marketer
Nothing in the evidence evidences scoring, decay, lifecycle stages or handover to sales — segments and a unified profile exist, but segmentation is not scoring, and 'basic segmentation' in the free tier is the only lifecycle-adjacent fact. For a product calling itself 'the autonomous B2C CRM', total silence on how a lead qualifies is itself information: as far as this evidence goes, every contact is treated alike. 1 2
The Solution Architect
Complete silence: no scoring, no decay, no lifecycle stages, no routing, no handover, nothing explainable per record anywhere in the evidence — segmentation and revenue attribution are not lead management. Silence on the entire criterion means I score near the floor. 1 2
Channels & personalisation
Show reasoningHide reasoning
How this is scored
What the platform can actually send and personalise: email, SMS, push, on-site content, ads audiences — judged on what shares one profile and one suppression list.
0 — Email only.
3 — Email plus one further channel, managed separately with its own list and no shared suppression.
5 — Email, SMS or push and web forms driven from one contact profile, with dynamic content blocks and shared unsubscribe handling.
8 — The above plus 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
This is the one place the evidence delivers: email, SMS, WhatsApp (native, no third-party), RCS, mobile push and web events all stated 'in einem einzigen Kundenprofil'. But no dynamic content blocks, no ad-audience sync, no cross-channel frequency capping, and no behavioural personalisation claim I can verify — breadth past rubric level 5, none of the discipline that earns 8. 1
The Sales Ops Manager
This is the one area the evidence actually documents: email, SMS, RCS, mobile push, native WhatsApp and web events 'in einem einzigen Kundenprofil', which exceeds the five-anchor channel list. But dynamic content blocks, shared unsubscribe handling, ad-audience sync, cross-channel frequency capping and on-site personalisation are all unevidenced, so it clears rubric level 5 on channel breadth and unity without reaching 8. 1
The Data Protection Officer
Email, SMS, RCS, push, WhatsApp and web events are claimed to unite in a single customer profile, with native WhatsApp and omnichannel launch — breadth past rubric level 5. But the evidence is silent on shared unsubscribe handling, one consent state, dynamic content blocks and cross-channel frequency capping, so I stop below rubric level 8. 1
The Lifecycle Marketer
Email, SMS, RCS, push, WhatsApp, web events, reviews and social all hang off one customer profile with native WhatsApp and no third-party bridge — that clears the one-profile bar comfortably. But there is no evidence of cross-channel frequency capping, shared suppression or ad-audience sync, which is precisely what I need before letting six-plus channels loose on one cohort, so it stalls short of the next anchor. 1 2
The Solution Architect
Six channels — email, SMS, RCS, push, WhatsApp, web events — unified in one customer profile, with native WhatsApp built in and SMS even in the free tier, which beats the one-profile anchor on breadth. But the evidence never evidences shared suppression or unsubscribe handling across channels, dynamic content, ad-audience sync, or cross-channel frequency capping, so I stop just above that anchor. 1 2
The Skeptic
Email, SMS, RCS, mobile push, WhatsApp and web events are genuinely united in one customer profile with native WhatsApp messaging — a solid anchor-5. Dynamic content blocks, shared unsubscribe handling, frequency capping and ad-audience sync are unevidenced, so no higher. 1
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 — Tracking always on and undocumented, single opt-in, no consent record, no retention rule, no way to exclude a person from profiling.
3 — Double opt-in available with a timestamp, cookie tracking that cannot be disabled per contact, and retention described as the customer's problem.
5 — Double opt-in as documented default with a stored consent record including source, per-channel consent states, tracking switchable per contact, and stated retention for inactive records.
8 — Consent reproducible as evidence with the wording versioned, profiling suppressible per person, retention executed per data category, documented handling of access and erasure requests including derived scores, and a cookieless or first-party tracking mode.
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 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
There's a compliance apparatus — cookie notice, privacy centre with past-requests and DSAR tooling, verification methods, DPA with SCCs and the Data Privacy Framework — but the evidence is silent on stored consent records with source, per-channel consent states, per-contact tracking switches, and retention for inactive profiles. AI processing of personal data is confirmed outright with zero documentation of what it decides, which given the profiling is exactly what I cannot wave through. 3 1
The Sales Ops Manager
There is a real privacy posture: a separate cookie notice, a privacy centre with self-service DSR tools including 'view past requests', a DPA, and named transfer mechanisms. But no double opt-in, no consent record with source, no per-channel consent states, no per-contact tracking switch, no retention for inactive records, no profiling suppression — and AI processing of personal data is disclosed with zero documentation of how automated decisions are made or contested. 3 1
The Data Protection Officer
There is a separate cookie notice, a tracking-technologies disclosure, a do-not-sell link, and self-service data-subject-request tools with a stated verification method, plus a DPA and transfer mechanisms. But for a platform processing named people's behavioural data with generative AI, nothing evidences a stored consent record with source, per-contact tracking suppression, per-channel consent states, retention beyond card digits, or deletion of derived scores — below rubric level 3, which at least expects double opt-in with a timestamp. 3 1
The Lifecycle Marketer
There is a separate cookie notice, a privacy centre with request history and self-service subject-rights tooling under a DPA, but no double opt-in, no consent-record mechanics, no per-channel consent states, no per-contact tracking switch and no retention rule for behavioural profiles. Since the platform explicitly processes personal data with AI including machine learning, the silence on profiling suppression is worse than a neutral gap. 3 1
The Solution Architect
Real machinery exists: a DPA with SCCs and Data Privacy Framework, a privacy centre with DSR tooling and past-request history, a cookie notice, CCPA opt-out, and disclosed AI processing of personal data. But no double opt-in, no stored consent record with source, no per-channel consent states, no per-contact tracking switch, and retention is entirely unaddressed — that caps it below the mid anchor. 3 1
The Skeptic
Real apparatus exists: privacy centre with tracking-technology controls and past-request history, self-service data subject request tools, DPA and DPF/SCC mechanisms. But double opt-in as default, consent records with source, per-channel consent states and retention beyond card digits are silent, while AI profiling is confirmed with no per-person suppression documented. 3 1
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 — CSV import and export; no CRM integration and no identity resolution.
3 — One-way sync into a named CRM on a schedule, with duplicates resolved by hand and no conflict rules.
5 — Bidirectional sync with at least one major CRM, field mapping, deduplication rules, and a sync error log somebody can act on.
8 — Configurable conflict resolution per field, account and contact objects both modelled, custom objects supported, near-real-time sync with retry, and a documented API with rate limits.
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
Strong plumbing signals: 350+ integrations, CRM connectors, APIs, webhooks, SDKs, warehouse syncs, and a data platform 'vereint Kundendaten in Echtzeit' into unified profiles. But the evidence cannot confirm bidirectional CRM sync, field mapping, deduplication rules or any conflict resolution — and for me the entire implementation is decided by what happens when the two systems disagree about who a person is. 1
The Sales Ops Manager
350+ prebuilt integrations, 'connectors for CRMs', APIs/webhooks/warehouse-syncs, and a real-time data platform that unifies customer data — but not one word on bidirectional sync, field mapping, deduplication rules, conflict resolution, or a sync error log somebody can act on. I inherit every duplicate a platform creates, and 'unified customer profile' inside Klaviyo tells me nothing about what happens when it disagrees with my CRM, so this tops out at one-way-connector territory. 1
The Data Protection Officer
CRM connectors are listed among 350+ integrations, with APIs, webhooks, SDKs, warehouse syncs and a real-time data platform of profiles and segments. But there is no evidence of sync direction, field mapping, conflict resolution, deduplication rules, or identity resolution across anonymous and known states — a native data model, not a governed two-system join. 1
The Lifecycle Marketer
Klaviyo positions itself as the CRM, with a real-time unified customer profile, 350+ integrations and a full API/webhook/SDK/warehouse surface — the breadth is real. But the evidence is silent on sync direction, field mapping, conflict resolution, deduplication and sync error handling, which is the join that decides implementations, so it lands between 'one-way sync' and the bidirectional anchor without evidencing either. 1
The Solution Architect
350+ integrations including CRM connectors, APIs, webhooks, SDKs and warehouse syncs, and a real-time data platform unifying profiles — a decent inbound story. But the evidence is silent on sync direction, conflict resolution, dedup rules, custom objects, documented rate limits, and above all the anonymous-visitor-to-known-contact path; 'autonomous B2C CRM' positioning tells me nothing about how two systems agree on who a person is when they disagree. 1
The Skeptic
Strong foundation on paper — real-time unified profiles, 350+ integrations with "CRMs" as a connector category, APIs, webhooks, warehouse syncs — but no named CRM sync, field mapping, dedup rules, conflict resolution or sync error log is evidenced; the join mechanics are all silent. 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.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed, behavioural data leaving the EU with no stated basis.
3 — EU data residency for storage while tracking, sending or support access remain non-EU, or the contracting entity sits outside the EU.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — tracking scripts, AI scoring, analytics — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, complete subprocessor list published, and any non-EU processing 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
US contracting entity (Klaviyo, Inc.), storage with an unnamed 'cloud hosting provider' in the US and UK, subprocessors unnamed, and EU transfers resting on the Data Privacy Framework and SCCs — which is precisely the Schrems II argument rubric level 10 says a buyer shouldn't have to make. Named transfer mechanisms are the only thing keeping this off zero. 3 1
The Sales Ops Manager
Klaviyo, Inc. is a US contracting entity, personal information is stored by an unnamed cloud host and processed 'in the United States', and subprocessors are unnamed — behavioural profiles of EU residents leave the EU on EU-US Data Privacy Framework and SCCs, which is a stated basis but a Schrems II argument the customer has to survive. That stated basis and a DPA keep it off a pure zero, nothing more. 3 1
The Data Protection Officer
Klaviyo, Inc. is a US contracting entity and data is processed "in the United States, where Klaviyo, Inc. is located", hosting is an unnamed "cloud hosting provider", and no subprocessor list is captured; DPF and SCCs are mentioned, which is the only thing lifting this above rubric level 0. Behavioural profiles of EU residents leave the EU with no residency or safeguard detail, and given the profiling I weigh that heavily. 3 1
The Lifecycle Marketer
Klaviyo, Inc. of Boston is the contracting entity, hosting is an unnamed 'cloud hosting provider', storage and processing run through the US and UK, and the subprocessor list is unpublished — transfers rest on the EU-US Data Privacy Framework and SCCs, which is exactly the Schrems II argument a behavioural profiling programme should not have to make. For named EU shoppers' profiles, this is a hair above the floor. 3 1
The Solution Architect
The contracting entity is Klaviyo, Inc. (US), hosting is 'our cloud hosting provider on secure servers' with transfers to the US and UK, subprocessors are unnamed, and the stated basis is SCCs plus the EU-US Data Privacy Framework — exactly the Schrems II argument the top anchor says shouldn't be needed. For a platform building behavioural profiles of named EU residents, I weigh that heavily; the named transfer mechanism alone keeps it off the floor. 3 1
The Skeptic
US legal entity, storage with an unnamed "cloud hosting provider", processing in the US and UK, subprocessors unpublished. The single point above zero: the transfer basis (EU-US Data Privacy Framework, SCCs) is at least stated — which is exactly the Schrems II argument this profile-heavy use would have to survive. 3 1
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, and onboarding fees are never mentioned.
3 — A contact-tier headline exists, but the tier where journeys, scoring or CRM sync begin is unstated, as is any mandatory implementation fee.
5 — Contact-tier prices public with billing period and send limits stated, but at least one commonly needed capability sits in an unpriced enterprise tier.
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
The free tier is documented to the cent — 500 emails, $5 of SMS, 10,000 Composer credits — but the captured pricing pages yielded no paid-tier figures at all: paid plans 'scale by contacts and channels', enterprise is 'individuelle Preise', and overage, onboarding fees, minimum term and VAT are unmentioned. I cannot compute an annual invoice for a 200k-contact base from this, so it sits between nothing-for-sale and a headline price. 1 2
The Sales Ops Manager
The free tier is concretely priced (500 emails/month, $5 mobile messaging, 10,000 Composer credits, 60 days of email support), but beyond that there are no contact-tier prices at all — just 'paid plans scale by contacts and channels' — and enterprise is 'individuelle Preisangebote'. No feature-to-tier boundaries (where do Flows or CRM connectors begin?), no overage rates, no onboarding fee, so the real annual invoice is not computable from these pages. 2 1
The Data Protection Officer
The free tier is unusually concrete — 500 emails/month, $5 mobile messaging, 10,000 Composer credits, 60-day email support — but paid plans are described only as scaling by contacts and channels with no figures, the tier where flows or CRM sync begin is unstated, and enterprise is quote-only. No overage, onboarding or VAT treatment anywhere; just below rubric level 3. 1 2
The Lifecycle Marketer
The free tier is fully specified — 500 emails/month, $5 of mobile messaging, 10,000 Composer credits, 60 days of email support — but no paid price figure exists anywhere in the evidence, only a 'contacts plus channels' basis and custom enterprise quotes. I cannot compute the invoice for the tier where flows, WhatsApp or the data platform actually begin, and onboarding fees, overage and VAT treatment are never mentioned. 1 2
The Solution Architect
The free tier is fully computable — 500 emails/month, $5 of mobile messaging, 10,000 Composer credits, 60 days of email support — and the paid basis is stated as contacts plus channels. But no actual tier prices, no overage rates, no onboarding or implementation fee, and enterprise is 'individuelle Preisangebote', so I cannot compute a real annual invoice for any contact base from these pages. 1 2
The Skeptic
The free tier is honestly quantified — 500 emails, $5 messaging, 10,000 Composer credits, 60 days of support — but paid plans "skalieren nach Kontakten/Kanälen" with no figures and enterprise is custom-quoted. The tier where flows begin, overage rates, and any mandatory onboarding fee never appear in the capture. 1 2
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 ⚠ unverified | — | uncited Report an error |
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 — Legal entity, Data residency, Subprocessors. 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.
- 50 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
- 45 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
- 20 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
- 12 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
- 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 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
- 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
- 2 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 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 (9)
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, 2 Sep 2026 Details →
- 2 Pricing www.klaviyo.com Checked 5 Oct 2026 +3 earlier captures: 16 Sep 2026, 11 Sep 2026, 2 Sep 2026 Details →
- 3 Privacy policy www.klaviyo.com Checked 5 Oct 2026 +1 earlier capture: 16 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 Channels & personalisation — found from sitemap www.klaviyo.com Checked 5 Oct 2026 Details →
- 7 Consent, tracking & profiling — found from sitemap www.klaviyo.com Checked 5 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 8 Consent, tracking & profiling — found from sitemap www.klaviyo.com Checked 5 Oct 2026 Details →
- 9 CRM integration & data model — found from sitemap www.klaviyo.com Checked 5 Oct 2026 Details →