CustomerLake: What It Means for Retailers

Traditional CDPs only ever saw part of the picture. Customer profiles, transactions, email engagement, useful, but incomplete.

Inventory, pricing, promotions, and in-store activity lived somewhere else. Getting those systems to talk to your CDP was a permanent engineering project, not a one-time setup.

For a retailer running stores, ecommerce, and fulfillment across multiple systems, that gap wasn't a technical footnote. It was the reason personalization stayed generic.

Instead of pulling customer data into a separate CDP, CustomerLake builds CDP capabilities directly into the Lakehouse, where the data already lives. 

Customer data, behavioral signals, product data, and in-store transactions now sit in the same governed foundation. In practice, that means a shopper's in-store purchase history, online browsing activity, and real-time inventory levels live in one system, instead of being split across a POS, a website analytics tool, and a separate CDP.

The platform replaces one-off campaigns with continuous, always-on agent loops that react to customer context in real time, rather than static, pre-planned campaigns.

That's a shift from "export data, build a campaign, hope it lands" to a system that's always watching and always acting.

Take a retailer that runs store systems on a large scale: 1,600 locations, each generating its own transaction and inventory signals. Reconciling that with online behavior has always been the hard part of omnichannel.

In simple terms: we're now able to reconcile and match in-store data with online data. In-store purchases, online browsing, and stock levels can be matched and unified in one place, instead of living in separate systems. That means personalization engines can finally work with the full commercial picture.

That matters more in specialty retail than almost anywhere else. A shopper comparing spec sheets for a bike or an office chair needs consistency between what they saw online and what a store associate can confirm in person.

Stitching together offline purchases, loyalty accounts, and anonymous browsing into a single customer profile is not simple. Loyalty data helps, but the hard part is connecting scattered identifiers, an email here, a phone number there, a customer with two or three separate profiles that never got merged.

CustomerLake's Profile Agents run this as an ongoing, automated process instead of a periodic batch job, what the platform calls agentic identity resolution.

For omnichannel retailers, that's the difference between a customer profile that's accurate on launch day and one that's still accurate six months later, after every new store transaction and every anonymous browsing session.

Marketers have chased true 1:1 personalization, not segments, not rules, an actual individual experience, for years without the data infrastructure to deliver it.

With complete data and dynamic segmentation agents in one governed environment, that goal is now within reach at meaningful scale. Launch materials put the target at delivering personalized experiences roughly a billion times a day, a figure worth treating as a company claim, not an independently verified benchmark.

That number matters less than what it implies: personalization that runs continuously, not personalization that ships once per quarter. It's also why activation partners matter here, Bloomreach's own CustomerLake launch announcement covers how a unified data layer connects to real-time execution across email, web, and other channels.

If your shoppers are high-consideration buyers, researching specs, comparing fit, checking reviews before they commit, the value of a unified profile compounds. Product content, browsing behavior, and purchase history all need to line up on the same page.

Knowing what to recommend, and when, gets easier with a single customer view. That's a merchandising problem as much as a data problem.

And if you're running BOPIS, ship-from-store, or any blend of in-store and online fulfillment, this is the layer that's supposed to make that complexity invisible to the shopper, not just faster on the back end.

Helping clients structure, consolidate, and activate their commerce data is work Datmos has been doing for years. CustomerLake formalizes a direction we already believe in: complete data, not partial data, drives real personalization.

We're building in this space alongside partners in the CustomerLake ecosystem, including Bloomreach and Databricks.

If you're thinking through what this means for your stack, your product data, your store systems, your identity resolution, contact us.