This article was written by Greg Kihlström for CMSWire. Read the full article here:
The marketing technology industry names a shift after the part of it that has the best demos and makes the best headlines. We called the last decade “composable” after an architecture, and we are now calling this one “agentic” after a mechanism. Both labels describe the mechanism and miss what actually changed.
With Databricks’ announcement of their CustomerLake CDP, the customer data platform stopped being a separate system and became a function of the platform where the data already sits.
CustomerLake, the agentic CDP the company announced at its Data + AI Summit and built natively inside the lakehouse, asks: Does a customer data platform need to exist anywhere other than where your data and your agents already are? Many enterprises with upcoming contract renewals would do well to figure out the answer.
What Is Databricks CustomerLake?
Databricks CustomerLake is a natively integrated customer data platform built inside the Databricks lakehouse. It combines Customer 360, identity resolution, audience building and AI-driven campaign activation in a single governed environment — eliminating the need to copy data into a separate CDP. For enterprises already running data and AI workloads on Databricks, it removes the reconciliation layer that has historically sat between the warehouse and the CDP.
This article was written by Greg Kihlström for CMSWire. Read the full article here:
Original Source:
The Martech Futurist Blog – Greg Kihlström Marketing Technology & Digital Transformation
Original URL:
