CDPs Competing With Partners

This move showed that the CDP was no longer trying to stay a neutral pipe, it was moving up the stack to own the workflow where budgets and switching costs are highest. Once Segment added Engage, it was not just routing event data into Braze, Iterable, or Customer.io. It was also helping marketers build audiences, trigger messages, and run journeys inside Twilio’s own product. mParticle made a similar step by folding in Indicative, so the data layer could also answer product questions without handing analysis off to another vendor.

• The practical conflict was simple. CDPs had built large partner catalogs by promising to send clean customer data into downstream tools. When they launched their own destinations, they started selling against some of those same partners for the highest value use cases, audience building, campaign orchestration, and product analytics.
  1 twilio 2 twilio 3 mparticle 4 sacra
• This was a retention play as much as an expansion play. If a company only uses a CDP as plumbing, it can swap out downstream apps more easily. If the CDP also holds the audience logic, journey rules, and analysis layer, ripping it out means rebuilding much more of the operating system for growth teams.
  2 twilio 4 sacra 5 sacra
• The pattern spread quickly in reverse. Application vendors like Amplitude and Klaviyo then added CDP capabilities of their own, because owning data collection removes onboarding friction and makes the analytics or messaging product harder to replace. The market started converging on bundled systems instead of cleanly separated data routers and apps.
  3 mparticle 4 sacra 5 sacra 6 amplitude

The next phase is deeper consolidation around the canonical customer profile. The winners will be the vendors that both collect the raw event stream and give teams an immediate place to act on it, whether that means analyzing behavior, building segments, or launching campaigns, without forcing the customer to stitch together a fragile chain of separate tools.