Customer-data work: what is changing is who does it

1H 2026 · Finding 4 of 5

The CDP’s work is being divided among more suppliers, but accountability for the result hasn’t followed.

Four of the five large data platforms leave the CDP to partners or keep it apart

3 route the category to partner CDPsCDP1 keeps its CDP apartCDP1 embeds a CDP3 route the categoryto partner CDPsCDP1 keeps its CDP apartCDP1 embeds a CDP

Positions as of June 30, 2026 (Table 24).

What has been said

All three major analyst firms describe pressure on the standalone CDP as data platforms take on customer-data work.

What the evidence shows

The work is being divided among more suppliers. No large data platform yet supplies it all, and responsibility for the result has not followed.

The five large data platforms take three positions.

As of June 30, 2026, three route the category to partner CDPs, one sells a data platform and a CDP and keeps them apart, and one embeds a CDP in its platform, not yet generally available.

No large data platform supplies what agents depend on.

None of the five supplies consent and data rights, first-party behavioral capture and identity resolution together as generally available first-party products. The one capability all five document, the clean room, depends on all three. Even in this case the work a CDP does is not displaced; what is contested is who packages which parts of it.

Consent anddata rightsFirst-partybehavioral captureIdentityresolution0 of 5large data platforms supplyall three as generally availablefirst-party productsConsent and data rightsFirst-party behavioral captureIdentity resolution0 of 5large data platforms supplyall three as generally availablefirst-party products

Architectures divide the work differently.

Hybrid and warehouse-native vendors claim next-best-action, agent context, interoperability and agent building more often than own-store vendors, and channel execution less often. Profile unification is claimed at a similar rate across the architectures, and every CDP type includes vendors of more than one architecture.

Hybrid and warehouse-native (56)Own-store (152)Channel executionNext-best-actionAgent buildingAgent interoperabilityAgent context and groundingProfile unification0%50%100%Hybrid and warehouse-native (56)Own-store (152)Channel executionNext-best-actionAgent buildingAgent interoperabilityAgent context and groundingProfile unification0%50%100%

Members already obtain AI through several routes.

Two-thirds of members (66.7%) use general AI providers directly and 62.0% use AI built into software they already own. Each route needs access to the same customer record.

66.7%use general AI providers directly62.0%use AI built into software they own66.7%use general AI providers directly62.0%use AI built into software they own

Accountability has not followed.

Buyers still assemble it, from a CDP or from several suppliers acting as one. Responsibility for a failure is getting harder to place.

What this finding does not establish

Vendor documentation shows who supplies each function, not who is accountable when an agent fails, and no published work or this edition links architecture to deployment outcomes (§15).