Data portability reduces Customer.io lock-in

Third party data pipes turn Customer.io from a system of record into a system of execution. When event data lives first in Segment or Hull, a company can keep the same user profiles, events, and audience logic while swapping out the messaging layer. That matters most for teams using Customer.io mainly for email automations, because the hard part, getting product data into usable shape, has already been solved outside the product.

• A former Customer.io customer described the switch to ActiveCampaign as relatively easy because all event data already flowed through Segment, and the new vendor rebuilt automations, forms, and segments for a few hundred dollars a month. That is the practical meaning of lower switching costs.
  1 sacra
• Customer.io historically benefited from deeper product integrations that required developer work. That custom setup raises lock in when teams wire directly into Customer.io. But the 2021 research also notes that using Segment or Hull removes some of that friction by making the data model portable across vendors.
  3 sacra
• This is one reason Customer.io expanded into Data Pipelines. The company explicitly positioned its CDP to lower the cost and complexity of integration, bundle it with Journeys, and compete with pricier standalone CDPs like Segment, while still letting customers send data to tools like Braze or Iterable.
  2 sacra 4 sacra 5 sacra

The next phase of competition moves upstream from message builders to the customer data layer. If Customer.io can own both data movement and orchestration, it can keep the benefits of openness while recapturing some of the stickiness that standalone CDPs took away. That would make churn less about moving data and more about which product turns that data into the best campaigns.