# Customer.io — Marketing Automation

Customer.io by Customer.io, Inc. holds a panel rating of 2.5/5 from 6 AI judges (category median 2.5/5), as of 2026-11-17. Provenance: provenance unknown; sovereignty: 3 of 6 dimensions proven.

- Vendor: Customer.io, Inc. (https://customer.io)
- Category: [Marketing Automation](https://whats-best.ai/software/marketing-automation.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/marketing-automation/customerio
- Alternatives: https://whats-best.ai/software/marketing-automation/customerio/alternatives ([markdown](https://whats-best.ai/software/marketing-automation/customerio/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-17 · oldest source captured 2026-09-29

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## 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 [S2]
- Free plan: Not stated on the vendor’s pages as of 16 Nov 2026

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

**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

**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

**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

**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

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v2). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Demand Gen Lead | The Sales Ops Manager | The Data Protection Officer | The Lifecycle Marketer | The Solution Architect | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Journeys & orchestration | 3/5 | 3/5 | 3.5/5 | 3.5/5 | 3/5 | 3/5 |
| Lead scoring, routing & lifecycle | 1.5/5 | 1.5/5 | 1.5/5 | 1.5/5 | 1.5/5 | 1.5/5 |
| Channels & personalisation | 3/5 | 3.5/5 | 3.5/5 | 3/5 | 3.5/5 | 3/5 |
| Consent, tracking & profiling | 2/5 | 2/5 | 3/5 | 2/5 | 2/5 | 2/5 |
| CRM integration & data model | 3.5/5 | 3.5/5 | 3.5/5 | 3/5 | 3.5/5 | 3.5/5 |
| European sovereignty | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2.5/5** | **2.5/5** | **2.5/5** | **3/5** | **3/5** | **2.5/5** |

### The judges

- **The Demand Gen Lead** (v1.0): Owns pipeline contribution and is measured on it. Wants journeys that branch on real behaviour, scoring that sales trusts, and attribution that survives a quarterly review. Unmoved by a builder that demos beautifully and cannot say which journey sent yesterday's email.
- **The Sales Ops Manager** (v1.0): Owns the CRM and inherits every duplicate the platform creates. Wants field-level ownership defined, conflict rules that are configurable rather than folklore, and a sync error log somebody can act on before the pipeline report is wrong.
- **The Data Protection Officer** (v1.0): Sees a profiling system, not a mailing tool. Wants consent reproducible per person, tracking that can be switched off for someone who never agreed to it, deletion that removes derived scores as well as raw events, and scoring documented well enough to assess under Art. 22.
- **The Lifecycle Marketer** (v1.0): Thinks in cohorts and retention rather than in campaigns. Wants frequency capping across every journey, holdout groups so the effect is measurable, and personalisation drawn from the behavioural record rather than assembled by hand.
- **The Solution Architect** (v1.0): Has implemented three of these and knows where they fail: identity resolution, custom objects, and the API limit nobody mentioned. Wants a data model extensible without vendor services and a documented path from anonymous visitor to known contact.
- **The Skeptic** (v1.0): Reads for the contact-tier staircase, the tier where journeys actually begin, and the mandatory onboarding fee that never appears on the pricing page. Has watched "unlimited emails" mean unlimited within a sending limit described elsewhere.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 3 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | EU region selectable | 1/1 | [S2] |
| Open source | Not determined | — | — |
| Data processing agreement | Published, self-serve | 1/1 | [S2] |
| Transfer impact assessment | Published | 1/1 | [S9] |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Breach notification: yes [S9]
- Breach notification: yes [S9]
- CCPA: CCPA and US data privacy laws compliance reviewed regularly [S2]
- CCPA: CCPA and US data privacy laws compliance stated [S2]
- Certifications: GDPR · CCPA · ISO 27001 · AICPA SOC · HIPAA [S1]
- Certifications: GDPR · CCPA · ISO 27001 · AICPA SOC · HIPAA [S1]
- Certifications: GDPR · CCPA · ISO 27001 · AICPA SOC · HIPAA [S1]
- Certifications: GDPR · CCPA · ISO 27001 · AICPA SOC · HIPAA [S1]
- Data sale: no [S2]
- DPA: legal page · yes [S2]
- DPA: yes [S2]
- DPA available: yes [S9]
- DPF membership: yes [S9]
- DPF membership: yes [S9]
- Encryption: Cloud KMS · HTTPS [S2]
- Encryption in transit: yes [S9]
- Encryption in transit: yes [S9]
- GDPR: data rectification · right to be forgotten · audit trail · yes [S2]
- GDPR: data rectification · right to be forgotten · comprehensive audit trail · EU data residency · yes [S2]
- GDPR commitment: yes [S10]
- HIPAA: yes [S2]
- HIPAA SOC 2: yes [S2]
- ISO 27001: yes [S2]
- ISO 27001: yes [S2]
- No data sale: no [S2]
- PCI stripe: Stripe · PCI Service Provider Level 1 · no [S2]
- Processing on instructions: yes [S9]
- Processor controller roles: yes [S9]
- SOC 2: SOC 2 Type II · yes [S2]
- Subprocessor list published: yes [S9]
- Transfer impact assessment: yes [S9]
- Transfer impact assessment: yes [S9]
- Trust center: yes [S1]

**Data**
- Subprocessor list: yes [S9]

**Hosting**
- EU data residency: yes [S9]
- EU residency: yes [S2]
- Legal entity: Peaberry Software, Inc. [S5]
- Regional API keys: yes [S2]
- Regions: US · EU · yes [S2]
- Regions: US · EU · yes [S2]
- Status page: yes [S1]

**Integrations**
- AI tools: MCP, CLI, API, webhooks [S1]
- API reference: yes [S5]
- Data warehouse: data activation · data warehouse [S5]
- Docs API: yes [S1]
- Eca migration deadline: Migration to ECA required before August 17, 2026 for pre-June 17, 2026 connections [S11]
- Regional API keys: yes [S2]
- Salesforce source complement: yes [S11]
- Surface: Connect your data, apps, and AI tools to a single platform [S1]
- Surface: data, apps, and AI tools integration [S1]
- Surface: Integrates with data, apps, and AI tools [S1]
- Twilio whatsapp: WhatsApp messages can be sent via Twilio; non-WhatsApp-approved Twilio senders will fail [S8]

**Legal**
- Address: 9450 SW Gemini Dr, 97008 Beaverton, US [S1]
- Address: 9450 SW Gemini Dr, 97008 Beaverton, US [S1]
- Address: 9450 SW Gemini Dr, 97008 Beaverton, US [S1]
- Copyright entity: Peaberry Software, Inc. [S5]
- Entity: Peaberry Software, Inc. [S1]
- Entity: Peaberry Software, Inc. [S9]
- Entity: Peaberry Software, Inc. [S1]
- Entity: Peaberry Software, Inc. [S1]
- Entity: Peaberry Software, Inc. [S1]
- Entity: Peaberry Software, Inc. [S2]
- Government request policy: notify_customer_and_challenge_requests [S9]
- Processor role: yes [S9]

**Pricing**
- Free trial: 14 · yes [S5]
- Trial: 14 · yes · no [S1]
- Trial: yes · 14 · no [S2]
- Trial: 14 · yes · no [S5]
- Trial: yes · 14 · no [S6]
- Trial: 14 · yes · no [S1]
- Trial: 14 · yes · no [S1]
- Trial: 14 · no · yes [S1]
- Trial: 14 · no · yes [S2]

**Product**
- Account protection: yes [S2]
- Account protection: yes · bank-grade · yes [S2]
- Action account: Create/update/upsert accounts [S11]
- Action case: Create/update/upsert cases [S11]
- Action contact: Create/update/upsert contacts [S11]
- Action custom object: Create/update/upsert records in any custom or standard object [S11]
- Action lead: Create/update/upsert leads [S11]
- Action opportunity: Create/update/upsert opportunities [S11]
- Action task for message delivery: Create Salesforce task per email delivery event, linking back to Customer.io [S11]
- Activation: Guide new users toward meaningful actions using behavioral triggers. [S1]
- Agent: yes [S1]
- Agent automation prompt: prompt to configured automation [S1]
- AI agent: AI Agent that builds automations from a prompt and analyzes campaign performance [S1]
- AI agent: AI Agent for building automations from prompts and analyzing campaign performance [S1]
- AI agent: AI Agent builds automations from a single prompt with triggers, content, timing, and logic [S1]
- AI integration: Works with any AI tool using MCP, CLI, API or webhooks [S1]
- AI integration: MCP, CLI, API or webhooks [S1]
- AI integration methods: MCP · CLI · API · webhooks [S1]
- Anonymous messages: yes [S5]
- Anonymous messages: yes [S1]
- Anonymous messages: yes [S1]
- Automatic suppression: yes [S9]
- Automatic suppression API: yes [S9]
- Automations: events · segment membership [S4]
- Automations capabilities: Automations and Broadcasts send email, SMS, push, and in-app messages; workflows can also send Slack messages, webhooks, and update attributes [S4]
- Automations support triggers: Automations can be triggered by event, object, relationship, date or form [S3]
- Automations triggers: Automations trigger on events or segment joins [S4]
- Brands count: 11000 [S1]
- Broadcasts: list of recipients · time you specify [S4]
- Broadcasts: Broadcasts send to a list of recipients at a specified time, manually or programmatically [S4]
- Case study metrics: 28 · 22 [S1]
- Case study metrics 2: 3.36 · 4.4 [S1]
- Channels: email · mobile · in-app · push · SMS · WhatsApp [S1]
- Channels: Email, Mobile, In-app Messages, Push Notifications, SMS, WhatsApp [S1]
- Channels: Email · SMS & MMS · In-app messages · WhatsApp · Mobile push · Mobile marketing [S1]
- Channels email: yes [S1]
- Channels mobile: mobile · in-app · push · sms · whatsapp [S1]
- Classic editors deprecated: deprecating classic editors in favor of Design Studio [S7]
- Classic editors types: drag-and-drop · rich text · code [S7]
- Code editor: syntax autocomplete · responsive previews · inspect element mode [S7]
- Code editor amp: yes [S7]
- Code editor amp: yes [S7]
- Code editor amp: yes [S7]
- Code editor features: yes [S7]
- Code editor features: syntax autocomplete · responsive previews · inspect element mode [S7]
- Code editor parcel: Parcel [S7]
- Code editor parcel: Parcel [S7]
- Cross sell: personalized cross-sell/upsell [S1]
- Cross sell upsell: Personalize cross-sell and upsell campaigns based on product usage. [S1]
- Custom objects: yes [S5]
- Custom objects: yes [S1]
- Custom objects: yes [S1]
- Customer brands: trusted by 9,000+ brands [S1]
- Customer brands: Trusted by 11,000+ brands [S1]
- Customer count: 11,000+ brands [S1]
- Data activation: yes [S1]
- Data activation: yes [S1]
- Data sources: data can be sent via preferred tools and sources [S4]
- Design studio: Design Studio is newest email editor; block-based with components and global styles [S7]
- Design studio access cutoff: accounts on/after cutoff get only Design Studio · Nov 5, 2026 [S7]
- Design studio AI: yes [S7]
- Design studio AI tools: yes [S7]
- Design studio capabilities: yes [S7]
- Design studio capabilities: unified brand, AI workflow, visual block-based editor with code editing option [S7]
- Design studio code access: yes [S7]
- Design studio code editing: yes [S7]
- Design studio collaboration: send test messages · request feedback [S7]
- Design studio collaboration: yes [S7]
- Design studio collaboration: yes [S7]
- Design studio components: yes [S7]
- Design studio components: yes [S7]
- Design studio components: yes [S7]
- Design studio creation contexts: Design Studio dashboard · automation · broadcast · transactional message [S7]
- Design studio global styles: email · in-app messages [S7]
- Design studio global styles: emails and in-app messages [S7]
- Design studio global styles: yes [S7]
- Design studio message types: Design Studio dashboard · automation · broadcast · transactional message [S7]
- Design studio review panel: yes [S7]
- Drag and drop editor: yes [S7]
- Drag and drop editor: build responsive emails without coding; blocks, columns, images, buttons, social links, global styles [S7]
- Dynamic segmentation: Dynamic segmentation groups customers based on data that updates continuously as users take actions or attributes change [S6]
- Ec authentication: Authenticate via Customer.io External Client App (ECA), installed once per Salesforce environment [S11]
- Editor switch content reset: no [S7]
- Editor switching: no [S7]
- Editor use contexts: automation · broadcast · transactional message [S7]
- Editors classic: Classic editors include drag-and-drop, rich text, and code editors [S7]
- Encryption: Cloud KMS · HTTPS [S2]
- End user data exports: Feature to export attributes for a group of users [S10]

**Subprocessors**
- Review process: yes [S9]
- Review process: yes [S9]
- SMS providers: yes · no [S9]
- Stripe: Stripe · credit card processing · PCI Service Provider Level 1 [S2]
- Twilio not subprocessor: no · yes [S9]

**Support**
- API docs: yes [S1]
- Appexchange listing: no [S11]
- Channels: email · chat · yes [S1]
- Channels: email · chat [S1]
- Channels: email · chat · yes [S1]
- Channels: email · chat · yes [S1]
- Docs: Documentation · API reference · Trust Center [S1]
- Legal contact: legal@customer.io [S2]
- Status operational: yes [S5]
- Status page: operational [S1]
- Status page: status page [S2]
- Status page: yes [S1]
- Status page: yes [S2]
- Trust center: yes [S5]
- Vulnerability reporting: Site Reliability team · email · no [S2]
- Vulnerability reporting: Site Reliability · email · yes [S2]

105 more facts on the canonical page: https://whats-best.ai/software/marketing-automation/customerio

## Questions

### 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](https://whats-best.ai/evidence/2199).

### 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)](https://whats-best.ai/software/marketing-automation/braze), [HubSpot Marketing Hub (3/5)](https://whats-best.ai/software/marketing-automation/hubspot-marketing-hub) and [ActiveCampaign (Automation) (3/5)](https://whats-best.ai/software/marketing-automation/activecampaign-automation) 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)](https://whats-best.ai/software/marketing-automation/brevo-automation) (EU-Made, France). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Customer.io alternatives](https://whats-best.ai/software/marketing-automation/customerio/alternatives).

## What this page leaves out

- 23 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.
- 5 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.
- 2 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.
- 1 compliance 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.
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown.
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure.

## Sources

- [S1] Vendor page: https://customer.io (checked 2026-11-16)
- [S2] Security / trust page — found from the homepage: https://customer.io/security (checked 2026-11-16)
- [S3] Journeys & orchestration — found from sitemap: https://docs.customer.io/messaging/send/automations/journeys/ (checked 2026-11-16)
- [S4] Journeys & orchestration — found from sitemap: https://docs.customer.io/messaging/journeys-overview/ (checked 2026-11-16)
- [S5] Lead scoring, routing & lifecycle — found from sitemap: https://customer.io/learn/lifecycle-marketing (checked 2026-11-16)
- [S6] Lead scoring, routing & lifecycle — found from sitemap: https://customer.io/learn/lifecycle-marketing/segmentation-for-saas (checked 2026-11-16)
- [S7] Channels & personalisation — found from sitemap: https://docs.customer.io/messaging/channels/email/editors/choose/ (checked 2026-11-16)
- [S8] Channels & personalisation — found from sitemap: https://docs.customer.io/messaging/channels/whatsapp/send-whatsapp/ (checked 2026-11-16)
- [S9] Consent, tracking & profiling — found from sitemap: https://customer.io/legal/gdpr (checked 2026-11-16)
- [S10] Consent, tracking & profiling — found from sitemap: https://docs.customer.io/accounts/security/gdpr-faq/ (checked 2026-11-16)
- [S11] CRM integration & data model — found from sitemap: https://docs.customer.io/integrations/data-out/connections/salesforce/salesforce-intro/ (checked 2026-11-16)
- [S12] CRM integration & data model — found from sitemap: https://docs.customer.io/integrations/data-in/connections/salesforce/mapping-to-customerio/ (checked 2026-11-16)

---

Cite as: whats-best.ai, "Customer.io — Marketing Automation", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/marketing-automation/customerio

Corrections: https://whats-best.ai/correct/479?target=page
