Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

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

by Customer.io, Inc. · customer.io

Report an error on this page Is this your product? →

Link to this page

Customer.io: AI-assisted analysis on whats-best.ai Customer.io: AI-assisted analysis on whats-best.ai (dark)

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.

Customer.io at a glance

Vendor
Customer.io, Inc.
Headquarters
Not stated on the vendor’s pages as of 16 Nov 2026
Data hosting
Default not stated; pages mention the US and the EU source, captured 9 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates Customer.io 2.5/5, the mean of 6 judges. Customer.io, a marketing automation platform, is judged strongest on CRM and data, where scores cluster at 6-7 with five of six judges at 7 for a Salesforce integration documented end to end — sync templates for contacts, leads, accounts and relationships, record matchers with a stated refusal on multiple matches, and lead-to-contact graduation handled through stored identifiers. how scores are made
As of
Vendor pages captured 29 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

Customer.io alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Customer.io, a marketing automation platform, is judged strongest on CRM and data, where scores cluster at 6-7 with five of six judges at 7 for a Salesforce integration documented end to end — sync templates for contacts, leads, accounts and relationships, record matchers with a stated refusal on multiple matches, and lead-to-contact graduation handled through stored identifiers. It is weakest on lead management, which scores 3: lifecycle runs on dynamic segments and preconfigured groups, and we found no public information on lead scoring, routing to owners or follow-up expectations. Sovereignty scores hold at 4 — EU hosting is selectable at signup with regional API keys, but the contracting entity on the captured pages is Peaberry Software, Inc. in Beaverton, Oregon, and the published transfer impact assessment discusses FISA 702 and EO 12333 because customer data may be transferred outside the EU/EEA. The split is consent and profiling: the data protection judge scored 6 for the documented erasure machinery, while five of six scored 4, finding no public information on double opt-in, consent timestamps or per-channel subscription states.

Report an error

Speaks for it

  • Salesforce integration documented in both directions — sync templates for contacts, leads, accounts and account-contact relationships, record matchers with AND/OR logic, and a stated refusal when several records match
  • Journeys trigger on events, objects, relationships, dates and forms, with filter retries up to 30 minutes, waits up to 24 hours, per-automation rate limiting and a per-person Journeys tab showing deliveries, conversions and entry/exit
  • Email, SMS and MMS, mobile push, in-app messages and WhatsApp all send from one person profile, with Liquid personalisation driven by product usage
  • Deletion and portability are documented as working machinery — a delete API and UI, suppression that redacts activity and blocks re-adding the same email or ID, an endpoint for objection and restriction requests, and a standardized profile export
  • EU hosting selectable at signup with US and EU data centers and regional API keys, alongside a downloadable data processing agreement and a published subprocessor list naming services and locations

Report an error

Held against it

  • Lead lifecycle runs on dynamic segments, and we found no public information on lead scoring, score history or routing rules with follow-up expectations
  • We found no public information on cross-channel frequency capping, on priority when a person qualifies for several journeys at once, or on safe editing of a live journey
  • We found no public information on double opt-in, stored consent timestamps and sources, per-channel subscription states or retention periods
  • Contracting entity on the captured pages is Peaberry Software, Inc. in Beaverton, Oregon, with a published transfer impact assessment that exists because customer data may be transferred outside the EU/EEA
  • Beyond a 14-day free trial with no card required and cancel-anytime terms, we found no public information on tier prices, contact or volume limits

Report an error

Best for

  • You run lifecycle messaging on real product events and need journeys triggered by events, object-relationship changes and dates, with a per-person view of deliveries and conversions
  • You sync with Salesforce in both directions and need lead-to-contact graduation handled through stored lead and contact identifiers
  • Your team sends email, SMS and MMS, push, in-app and WhatsApp from one people model and personalises on product usage rather than stored fields alone
  • You must answer deletion, objection and portability requests with documented machinery — a delete API and UI, suppression that redacts activity, and a standardized profile export

Report an error

Avoid if

  • You need lead scoring, score history and routing to sales owners inside the platform — the bench found lifecycle handled through dynamic segments, with qualification happening in Salesforce
  • Your programme depends on cross-channel frequency capping or arbitration when one person qualifies for several journeys at once — rate limiting is documented only within a single automation
  • Your procurement requires a European contracting entity — the captured pages name Peaberry Software, Inc. in Beaverton, Oregon, and the published transfer impact assessment exists because customer data may be transferred outside the EU/EEA

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Journeys & orchestration 3 of 5
Lead scoring, routing & lifecycle 1.5 of 5
Channels & personalisation 3.5 of 5
Consent, tracking & profiling 2 of 5
CRM integration & data model 3.5 of 5
European sovereignty 2 of 5

Journeys & orchestration

Show 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.

Report an error

The Demand Gen Lead

Triggers fire on events, segment joins and object-relationship changes, with filter conditions and retry windows, waits up to 24 hours, and a per-person Journeys tab showing every delivery, conversion, entry and exit — that per-person view is the attribution backbone I want. What holds it mid-scale: we found no public information on if/else branching, cross-journey frequency capping, priority when someone qualifies for several journeys at once, or safe editing of a live journey. 3 4 5 4

Report an error

The Sales Ops Manager

The journeys documentation is genuinely operational: triggers on events, objects, relationships, dates and forms, filter conditions retried for up to 30 minutes, a 24-hour wait setting, rate limiting, manual journey exits, and a per-person Journeys tab showing deliveries, conversions and entry/exit. That is more than a visual builder with waits, but we found no public information on what happens when one person qualifies for several journeys at once, cross-journey frequency capping, or safe editing of a live journey, so I stop short of the top band. 3 4 4 1

Report an error

The Data Protection Officer

Automations trigger on events, segment joins, objects, relationships, dates and forms, with filter conditions retried for up to 30 minutes, waits up to 24 hours, rate limiting, manual early exit, and a per-person Journeys tab recording deliveries, conversions and entry and exit — real per-contact journey state, fed by real-time product data through the API — and holding back a percentage of a segment for comparison is described. We found no public information on priority when a person qualifies for several automations at once, or on versioning and safe editing of a live journey. 3 4 6 4

Report an error

The Lifecycle Marketer

The visual workflow builder triggers on events, objects, relationships, dates, forms and segment joins, with filter conditions retried for up to thirty minutes and a wait setting that holds a person up to twenty-four hours; the journeys view shows each person's deliveries, conversions and entry and exit, and journeys can be ended manually. The vendor also documents holding out a percentage of a segment to compare activation rates, but rate limiting is documented only within a single automation, and we found no public information on frequency capping or priority across journeys, or on safe editing of a live journey. 3 4 6 4

Report an error

The Solution Architect

The journey documentation is the real thing: entry on event, object, relationship, date or form with a 30-minute filter retry, waits up to 24 hours, per-automation rate limiting, manual exit, and a per-person Journeys tab showing deliveries, conversions and entry/exit — the per-contact state record most tools get wrong. What I found no public information on is priority when one person qualifies for several journeys, cross-journey suppression, versioning of a live journey, or a single decision layer across the programme. 3 4 5 4 1

Report an error

The Skeptic

The docs describe automations triggered by events, segment joins, objects, relationships, dates and forms, with waits of up to 24 hours, filter retries, rate limiting, manual exit, and a per-person Journeys tab recording deliveries, conversions and entries/exits. We found no public information on if/else branching, priority when a person qualifies for several journeys, suppression across journeys, or versioning of a live journey, so this sits just past the visual-builder level rather than at full programme orchestration. 3 4 4 1

Report an error

Lead scoring, routing & lifecycle

Show 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.

Report an error

The Demand Gen Lead

Lifecycle is real but segment-shaped: people move automatically through dynamic segments as they act, preconfigured segments like paying customers and lapsed logins exist, and the Salesforce integration models lead-to-contact graduation with stored identifiers for reverse sync. We found no public information on lead scoring, score history per contact, routing rules to owners or follow-up service levels — so I cannot hand sales something they would trust or audit. 6 12 4

Report an error

The Sales Ops Manager

The captured pages show rule-based dynamic segmentation doing lifecycle duty — pre-built segments like "Paying Customers" and "Have not logged in recently" — plus a carefully modelled Salesforce lead graduation into Contact, Account and Opportunity with reverse sync. We found no public information on lead scoring, routing to owners or follow-up SLAs, so this sits at lifecycle stages set by rules with a real path into the sales system. 6 4 12

Report an error

The Data Protection Officer

Lifecycle handling is documented as dynamic segmentation — pre-configured segments such as “Paying Customers” and “Have not logged in recently” re-evaluating as people act and their attributes change — applied across onboarding, activation, retention and expansion. We found no public information on scoring models, negative scoring or score decay, per-contact score history, or routing rules with follow-up commitments to sales, and no scoring exists whose contribution per signal could be explained to a lead. 6 4

Report an error

The Lifecycle Marketer

Lifecycle is handled through dynamic segments that move people as they complete onboarding and adoption steps, and the Salesforce integration detects lead graduation by storing lead and contact identifiers. Qualification itself happens in Salesforce, and we found no public information on any lead scoring feature, score history, or routing rules with follow-up expectations. 5 6 11 12

Report an error

The Solution Architect

Lifecycle staging is documented only as marketer-built dynamic segments: onboarding steps move people into new segments that trigger the next relevant message. I found no public information on lead scoring, score decay or negative scoring, qualification rules, or routing and handover to sales. 5 6

Report an error

The Skeptic

Lifecycle stages are expressed as dynamic segments that update as people act or attributes change, with ready-made segments like Paying Customers and Have not logged in recently. We found no public information on lead scoring, score decay, routing to sales owners with follow-up expectations, or score history per contact. 5 6 4

Report an error

Channels & personalisation

Show 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.

Report an error

The Demand Gen Lead

Email, SMS and MMS, mobile push, in-app messages and WhatsApp all send from one person profile inside the same automations and broadcasts, with Liquid personalisation and campaigns personalised on product usage rather than stored fields alone. We found no public information on ad-audience sync, on-site web personalisation or cross-channel frequency capping, which is what the top of this scale is about. 1 4 1 8

Report an error

The Sales Ops Manager

Email, SMS and MMS, push, in-app and WhatsApp all send from one person profile of attributes, events and object relationships, with Liquid personalisation and cross-sell content driven by product usage rather than stored fields alone. We found no public information on ad-audience sync or cross-channel frequency capping — only per-automation rate limiting — which keeps it below the top band. 4 1 8 1

Report an error

The Data Protection Officer

Email, SMS, push, in-app messages and WhatsApp all send from one person record of attributes, events and relationships inside the same automations and broadcasts, with Liquid personalisation and campaigns personalised on product usage rather than stored fields alone. We found no public information on ad-audience sync, cross-channel frequency capping, or how a single unsubscribe state is shared across every channel. 1 4 1 8

Report an error

The Lifecycle Marketer

Email, SMS and MMS, push, in-app and WhatsApp all send from the same person profile inside automations and broadcasts, and personalisation runs on product-usage behaviour with Liquid variables rather than only stored fields. We found no public information on ad-audience sync to the major networks, on-site personalisation beyond in-app messages, or cross-channel frequency capping. 1 4 4 1 8

Report an error

The Solution Architect

Email, SMS and MMS, push, in-app and WhatsApp all send from the one person profile holding attributes, events and object relationships, and personalisation runs on Liquid plus product-usage behaviour rather than only stored fields. Rate limiting is documented per automation, and I found no public information on ad-audience sync or frequency capping across channels. 1 3 4 1 8

Report an error

The Skeptic

Email, SMS and MMS, mobile push, in-app messages and WhatsApp are all documented, driven from one people model of attributes, events and object relationships, with Liquid personalisation and cross-sell content personalised on product usage rather than stored fields alone. We found no public information on ad-audience sync, on-site personalisation, cross-channel frequency capping, or shared unsubscribe handling across channels. 1 4 1 8

Report an error

CRM integration & data model

Show 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.

Report an error

The Demand Gen Lead

Two-way Salesforce integration is documented end to end: data-in and data-out, sync templates for contacts, leads, accounts and relationships, field mapping with renames, timestamp conversion, record matchers on external IDs and custom fields with AND/OR operators, and a clean refusal with an error status when multiple records match rather than a silent overwrite. Lead graduation is handled by storing lead and contact identifiers with a coalesce function. We found no public information on per-field conflict resolution, sync retry with an error log, or documented API rate limits. 11 12 11

Report an error

The Sales Ops Manager

This is the deepest part of the documentation: Salesforce syncs both directions with templates for contacts, leads, accounts and account-contact relationships, create/upsert/update/delete with configurable record matchers on external IDs and custom fields, custom and standard objects, sandbox support, and an honest treatment of the identity join — leads and contacts identified by email, with the pages spelling out that email is unique by default in Customer.io but not required to be unique in Salesforce. What keeps me below the top band: the multi-match rule simply refuses the operation rather than letting me configure resolution per field, syncs are scheduled rather than near-real-time, and we found no public information on a sync error log, retry behaviour or API rate limits. 11 12 11 5

Report an error

The Data Protection Officer

The Salesforce integration is documented end to end: data-in and data-out with create, upsert, update and delete; record matchers on external IDs, record IDs, standard and custom fields with AND/OR logic; sync templates for contacts, leads, accounts and account-contact relationships; scheduled syncs plus a full resync with documented rename and backfill semantics; sandbox support; and identity by email with lead and contact IDs coalesced for the return trip. Duplicate behaviour is explicit — a multi-match under OR refuses the operation rather than guessing. We found no public information on near-real-time sync with retry and an error log, or on documented API rate limits. 11 12 11

Report an error

The Lifecycle Marketer

The Salesforce integration is genuinely two-way, with sync templates for contacts, leads, accounts and account-contact relationships, field mapping that can rename to existing attributes, record matchers with documented behaviour when several records match, and custom objects supported in both directions. Identity rests on the email address and the vendor documents that emails are unique by default in their system but not required to be in Salesforce; field-level conflict ownership, retry and error logging, and API rate limits are not documented on the captured pages. 5 11 12 11

Report an error

The Solution Architect

The Salesforce integration is documented to a depth I rarely see: sync templates for contacts, leads, accounts and relationships, record matchers with AND/OR including a stated failure on multi-match, custom and standard objects in both directions, and — the part implementations live or die on — the email uniqueness mismatch between the two systems, lead-to-contact graduation handled through stored lead and contact identifiers, and a documented coalesce. I found no public information on field-level conflict resolution, sync retry with an error log, replay of failed syncs, or API rate limits. 4 5 11 12 11

Report an error

The Skeptic

Salesforce is documented in both directions with sync templates for contacts, leads, accounts and relationships, field mapping and renaming, record matchers on external IDs, record IDs and custom fields, create/update/upsert/delete, custom and standard objects, scheduled syncs with resync semantics, and sandbox support. We found no public information on per-field conflict resolution, documented API rate limits, or an error log for failed syncs; the docs also note emails are unique in this platform but not in Salesforce by default, which is the identity seam a buyer should probe. 11 12 11

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The Demand Gen Lead

EU data residency is stated as selectable at signup with regional API keys, a data processing agreement is offered for download, and a subprocessor list is published with services and locations. But the contracting entity on the captured pages is Peaberry Software, Inc. at a Beaverton, Oregon address, and the published transfer impact assessment plus Data Privacy Framework membership point to processing outside the EU — we found no public information naming the EU infrastructure or an EU contracting entity. 9 9 1 2

Report an error

The Sales Ops Manager

EU residency is a signup-time choice between a United States and a Europe region, with regional API keys to match, alongside a self-serve data processing agreement and a published subprocessor list naming services and locations. The captured pages establish no EU contracting entity — the copyright entity and postal address point to Peaberry Software, Inc. in Beaverton, Oregon — and the published transfer impact assessment exists precisely because customer data may be transferred outside the EU/EEA. 2 2 9 1 9

Report an error

The Data Protection Officer

EU residency is selectable at signup, with US and EU data centres, regional API keys, and ingest, processing and storage in the chosen region, supported by a published subprocessor list with services and locations, a downloadable data processing agreement and a transfer impact statement. But the contracting entity evidenced on the captured pages is Peaberry Software, Inc. at an Oregon address, and the transfer impact statement discusses FISA 702 and EO 12333 because customer data may be transferred outside the EU/EEA, so behavioural profiles of EU residents are not shown to sit under a European entity. We found no public information on the named infrastructure behind the EU region or on certification. 2 9 9 1 2

Report an error

The Lifecycle Marketer

EU hosting is selectable at signup, a data processing agreement is downloadable, and a subprocessor list is published with services and locations, alongside a transfer impact assessment statement and a policy of challenging government requests. The contracting entity appears as Peaberry Software, Inc. at a Beaverton, Oregon address, and the transfer impact assessment together with active Data Privacy Framework membership points to processing outside the EU, so behavioural profiles of EU residents sit in an EU region of a US-entity chain at best. 2 9 9 1 2

Report an error

The Solution Architect

EU hosting is selectable at signup with regional API keys directing the data, a data processing agreement is downloadable, the subprocessor list names each processor with its services and location, and a transfer impact assessment is published — but the contracting entity is Peaberry Software, Inc. in Beaverton, Oregon, and the assessment's discussion of FISA 702 alongside active Data Privacy Framework membership confirms processing outside the EEA. I found no public information naming the infrastructure behind the EU region. 2 9 9 1 2

Report an error

The Skeptic

The vendor states you choose United States or Europe hosting at signup and offers a self-serve DPA, a subprocessor list with services and locations, and a published transfer impact assessment whose existence speaks to transfers outside the EU. The contracting entity is Peaberry Software, Inc. at a Beaverton, Oregon address and no page names the EU infrastructure or a European entity, so what is proven is a European hosting option on an American legal chain. 2 9 9 1 2

Report an error

Pricing transparency not rated — the vendor publishes no price

Show 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.

Report an error

The Demand Gen Lead

The only pricing information on the captured pages is a free 14-day trial with no card required and cancel-anytime terms. We found no public information on tier prices, contact or send-volume limits, which tier automation begins on, overage rates, onboarding fees or term lengths — nothing a demand gen team could use to budget a quarter. 6 5

Report an error

The Sales Ops Manager

The only commercial terms on the captured pages are a 14-day free trial with no card required and cancel-anytime. We found no public information on tier prices, contact or volume limits, overage rates, or the tier where automation begins, so I cannot begin to compute an annual invoice. 6 5

Report an error

The Data Protection Officer

The only price information we found is a free 14-day trial, no credit card required, cancel anytime. We found no public information on tier prices, billing periods, contact or volume limits, the tier where automation begins, overage rates, onboarding costs or VAT treatment, so a real annual invoice cannot be derived from what we read. 6 5

Report an error

The Lifecycle Marketer

The only pricing facts on the captured pages are a free fourteen-day trial with no credit card required and cancel-anytime terms. We found no public information on tier prices, contact limits, where automation features begin, overage rates or onboarding costs, so an annual invoice cannot be computed from these pages. 6 5

Report an error

The Solution Architect

The only public pricing information on the captured pages is a "14-day free trial", "No card required", "Cancel anytime". I found no public information on tier prices, contact or volume limits, the tier where automation begins, overage rates, or onboarding costs. 6 5

Report an error

The Skeptic

The only pricing information on the captured pages is a free trial described as 14-day free trial, No card required, Cancel anytime. We found no public information on tier prices, contact limits, the tier where automation begins, overage rates, or onboarding costs, so no annual invoice can be computed from what was captured. 6 5

Report an error

European sovereignty — proven facts

3 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Hosting options EU region selectable unverified
Why unverified?

The selectable regions include the United States as well as Europe, and no page states that self-hosting or on-premises deployment is unavailable.

1/1 pts 2 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

The excerpt only points to the DPA hosted on the legal page; the agreement text itself is not reproduced in the excerpts.

1/1 pts 2 Report an error
Transfer impact assessment Published unverified
Why unverified?

The page is a summary statement (discussing FISA 702, EO 12333 and subprocessor onward transfers) rather than a detailed assessment document, and its existence implies customer data may be transferred outside the EU/EEA.

1/1 pts 9 Report an error

Questions about Customer.io

Is Customer.io European?

Not determined: the vendor’s pages as captured do not say where Customer.io is based.

Where does Customer.io store data?

The default storage location for customer data is not stated on the vendor’s pages as of 16 Nov 2026. The vendor’s pages mention the US and the EU as hosting locations, per the vendor’s page captured 9 Nov 2026.

Does Customer.io have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to Customer.io?

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: Customer.io alternatives.

Where this could be wrong

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.

Sources (12)

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

  1. 1 Vendor page customer.io Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 29 Sep 2026 Details →
  2. 2 Security / trust page — found from the homepage customer.io Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
  3. 3 Journeys & orchestration — found from sitemap docs.customer.io Checked 16 Nov 2026 Details →
  4. 4 Journeys & orchestration — found from sitemap docs.customer.io Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
  5. 5 Lead scoring, routing & lifecycle — found from sitemap customer.io Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
  6. 6 Lead scoring, routing & lifecycle — found from sitemap customer.io Checked 16 Nov 2026 Details →
  7. 7 Channels & personalisation — found from sitemap docs.customer.io Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 26 Oct 2026 Details →
  8. 8 Channels & personalisation — found from sitemap docs.customer.io Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
  9. 9 Consent, tracking & profiling — found from sitemap customer.io Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  10. 10 Consent, tracking & profiling — found from sitemap docs.customer.io Checked 16 Nov 2026 Details →
  11. 11 CRM integration & data model — found from sitemap docs.customer.io Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  12. 12 CRM integration & data model — found from sitemap docs.customer.io Checked 16 Nov 2026 Details →