Customer.io

Customer.io is event-driven messaging with the customer data pipeline that feeds it in one product: email, push, in-app, SMS and WhatsApp for product-led teams.

Customer.io is one platform sold in two parts: Journeys, the messaging side, and Data Pipelines, the data layer that feeds it. It is built for product-led software and subscription businesses that already emit events and want to act on them across every channel from the same tool that collects the data. It is made by Peaberry Software, Inc., trading as Customer.io, a remote-first company founded in 2012. Journeys sends email, push, in-app, SMS and WhatsApp itself rather than through a bolted-on provider, with a transactional messaging API for the one-off messages. A person enters an automation when an event fires, a segment matches, a date arrives, a form is submitted or a webhook hits, then moves through a visual workflow builder of true or false and multi-split branches, wait until and time window delays, random cohort experiment paths, holdout tests, webhook send and receive actions and a Run LLM step that writes attributes back onto the profile. Goals carry a revenue impact, message frequency limits and a recommended send time protect the audience, the AI Agent drafts campaigns and builds segments from a sentence, and ad audience sync pushes segments to Google and Meta. Data Pipelines collects identify, track, page and screen calls through a JavaScript library, native iOS and Android SDKs and a server-side Pipelines API, takes Salesforce, HubSpot, Segment, Rudderstack and mParticle as sources, and forwards events in real time to analytics, CRM, support and ad destinations. Identity merge with alias calls builds unified profiles with activity history, a no-code audience builder with an AI describe mode segments them, and reverse ETL, warehouse export to Redshift, BigQuery and Snowflake, historical data replay and a profile lookup API move the data both ways. Custom roles, SAML SSO and US and EU data hosting sit underneath. Customer.io suits product-led SaaS teams with event data, lifecycle marketers running onboarding and retention flows, mobile apps that need push and in-app together, teams with engineers to wire up SDKs and webhooks, and data teams feeding messaging from a warehouse. It is sold by profile count, with Essentials billed monthly, Premium billed yearly and Enterprise on request, a trial with no card on file and a startup programme for early-stage companies. Data Pipelines is included in the same plans. For a subscription business, Customer.io runs the onboarding and activation sequence, the churn-risk and re-engagement messaging, the cross-sell based on product usage and the trial expiry reminder, sends transactional email and push from one API, syncs segments to ad audiences and feeds Salesforce and the support desk from one event stream. The warehouse, the CRM and the product itself remain the systems of record; Customer.io reads their events and does the messaging.