Twilio Engage turned Segment competitive

Launching Engage meant Twilio stopped being just the pipe and started becoming the app at the end of the pipe. Segment had won by being the neutral event router that let a merchant send the same customer data to Klaviyo, Braze, Intercom, or anyone else with one snippet. Engage turned that router into Twilio’s own marketing layer, with audience building and journey orchestration sitting directly on top of Segment data and Twilio messaging channels.

• Segment’s original power came from analytics.js, one universal snippet that collected customer events once and forwarded them to many downstream tools. That made destination apps easier to swap, because the data model lived in Segment instead of inside any single ESP or CRM.
  1 sacra
• Twilio launched Engage in October 2021 as a growth automation product built natively on Segment. At that point, Twilio was no longer only helping marketers move data into Klaviyo or Braze. It was packaging data, audiences, journeys, and delivery into one stack that could replace parts of those tools.
  2 twilio 3 businesswire 4 twilio
• That shift is why apps like Klaviyo and Customer.io moved to build their own CDP layers. Once the system that stores the canonical customer profile also owns activation, it can bundle the data plumbing cheaply, reduce handoff latency, and make the messaging product harder to rip out.
  1 sacra 5 sacra 6 sacra

The market keeps moving toward bundles where the data layer and engagement layer are sold together. The winners will be the products that own the customer profile, make activation easy for marketers without engineers, and still offer enough openness that partners keep feeding them data instead of treating them as a threat.