Journeys enables real-time messaging decisions
Colin Nederkoorn, CEO and founder of Customer.io, on AI's effect on marketing automation
This reveals that Customer.io is trying to own the decision point, not just the message send. When Journeys has the same live profile, event stream, and warehouse synced traits that power segmentation, marketers can trigger emails, SMS, and push without asking a data team to export fields or patch broken connectors. That makes the product faster in day to day use, and it makes the bundled platform harder to replace with a loose stack of warehouse, CDP, and messaging tools.
-
In practice, full context means a marketer can target a user based on app events, plan status, CRM fields, or warehouse data in one workflow. Customer.io built Data Pipelines to pull data in, transform it, and pass it both into Journeys and out to other tools, so the messaging logic is using the same customer record as the rest of the stack.
-
This is a response to a real market shift. Many companies moved customer data into warehouses and then rationed what downstream tools could see. Customer.io’s pitch is that warehouse sync plus CDP style routing restores enough context for real time messaging, while avoiding the extra latency, debugging, and cost of stitching together separate vendors like Segment plus a messaging tool.
-
It also explains why Customer.io reversed course from selling separate products to selling one platform. Earlier, Data Pipelines could stand alone and widen the funnel. Later, the company folded it back into Journeys because the main value was not CDP revenue by itself, it was making the core messaging product more useful, easier to sell, and better positioned against bundled suites like HubSpot and Klaviyo.
The direction from here is toward a tighter operating system for product led messaging. As AI assistants generate segments, workflows, and personalized content, the winner will be the platform with the richest shared context across profile data, business context, and action history. Customer.io is positioning Journeys to be that execution layer, with data movement built in rather than bolted on.