Every era of digital has been defined by the data layer that shaped it. The next one has consequences the previous layers did not.
In my last article, I argued that context is the defining variable in applied AI, and that artists have been wrestling with the same problem for centuries. This piece takes that argument for granted and asks a harder question: if context is the constraint, what layer of infrastructure actually produces it?
The answer is not a new feature inside an existing platform. It is a new layer. And the clearest way to see it is to look at the layers that came before.
In the beginning, there was no data layer at all. Tags and tracking calls fired directly from page code. Every new tool was a new dev cycle. It worked at the scale of the early web. It did not survive contact with the first wave of serious digital measurement.
The first structured response was the Analytics Data Layer — a standardized object on the page that any analytics tool could read. Google Tag Manager’s dataLayer is the direct descendant. This was the first time anyone said out loud that the data about what was happening should be decoupled from the tools that wanted to know about it. A modest idea in retrospect. It changed everything about how digital measurement scaled.
The next transition was the Universal Data Layer, and this is where Tealium’s story begins. The UDL generalized the analytics layer into something vendor-neutral: one canonical description of what was happening on a page or in a session that could feed any downstream tool. Tealium built the category. The W3C tried to standardize it. The principle was simple and, in hindsight, obvious: the data model should be independent of the tools that consume it.
Then the surface area expanded. Customers stopped living on web pages. They lived across devices, sessions, apps, call centers, stores, and channels. The Universal Data Layer described events in a moment; it could not describe customers across time. The Customer Data Layer — what the industry now calls the CDP — was the answer. Tealium built this layer too. I have written at length elsewhere about why orchestration matters more than storage, and why the organizations that treated customer data as strategic infrastructure rather than a marketing tool have been compounding advantages ever since.
The CDP era is not over. Its infrastructure is the platform that everything after it stands on. But the primary consumer of that infrastructure is changing, and when the primary consumer of a layer changes, the layer itself has to change with it.
The next layer is the one that feeds AI systems — models, agents, and automated decisioning operating at inference-time latency with real consequences. I have gestured at this layer in passing across most of my recent writing: the context layer, the semantic layer, the AI-ready data stream. Here I want to give it a proper name, because the absence of one is what lets organizations keep treating the infrastructure AI actually needs as “CDP plus some connectors” and building accordingly. Which is roughly the architectural equivalent of calling a smartphone a calculator.
What is the AI Data Layer?
It is not a replacement for the CDP. It is what the CDP becomes when its primary consumer is no longer a marketing activation platform but a model or an agent. Most of what makes this layer necessary I have already argued in other pieces — I will not re-make the case for real-time over batch, for first-party over third-party, or for consented context over raw data. Those arguments hold, and they have held for years. What I want to spend this article on is what becomes structurally different about the layer once AI systems are its primary consumers.
Four things
The consumer is no longer predictable. The CDP era assumed the thing reading from the profile was a known set of systems: a campaign tool, an ad platform, a recommendation engine. You could shape the profile to suit those consumers. The AI Data Layer’s consumers are heterogeneous and proliferating — a fraud model, a support copilot, a recommendation system, an autonomous purchasing agent operating on a customer’s behalf. Each one needs a different slice of the customer, composed differently, at a different cadence. The layer has to compose what it serves based on who is asking and for what, and it has to be able to justify, after the fact, exactly what was sent and why. Static profile modeling cannot do this. The layer itself has to be a composer, not a container.
Governance has to move from activation to composition. I have written before about what happens when you poison a model with unconsented data, and the problem is getting worse as models retain more context and agents take more actions. The architectural response is the point. Governance cannot live at the edge of activation anymore. It has to live inside the layer, at the moment context is composed, before anything reaches the model — because once the model has it, enforcement is too late. Consent, purpose limitation, and data minimization stop being compliance layered on top of the profile. They become properties of the profile itself, enforced per signal, per consumer, per decision.
Identity has to resolve across surfaces that did not exist. The identity graph the industry built for web and app was already insufficient a year ago. Voice assistants, chat interfaces, autonomous agents acting on a customer’s behalf, human agents augmented by models — each is a new surface, and each breaks an assumption the CDP-era graph was designed around. The AI Data Layer has to resolve one human being across surfaces the CDP era never contemplated. The resolution has to be correct, and it has to be fast, because the consequences of getting it wrong compound across an agent’s chained actions in ways they never did across a marketing funnel.
The architectural pattern flips. For a decade, the dominant pattern has been consumer system → data lookup → action. In the AI era, the pattern is customer → contextual layer → AI → action. The layer becomes an input, not a query. Architectures that treat context as something to retrieve on demand will lose to architectures that treat it as infrastructure that is already composed, governed, and ready the moment the model needs it.
This is where Tealium sits, and why I think the argument matters beyond our walls. We built the Universal Data Layer. We built the Customer Data Layer. And the work we are doing now is the next layer — the one between the real customer and the AI systems that reason about them on the customer’s behalf. Not because the CDP category was wrong, but because it was early. Everything that era taught us about identity, consent, real-time assembly, and first-party signal quality turns out to be exactly what the AI era needs, with the stakes substantially raised.
One last thing, because I want to signal where this argument is going next.
Everything I have described so far is about giving AI systems the right context to respond. The harder version is giving agents the right context to act, and to keep acting, over time, in ways that remain faithful to who the customer is and what they have consented to. Agents accumulate context. They make decisions that change the context they will operate in next. They chain actions in environments where wrong context produces real-world consequences, not just bad outputs. The AI Data Layer I have described here is already necessary for chat, recommendation, fraud, and support. For agents, it is the minimum viable architecture. I will come back to that in the next piece.
The frame, as I said in the last article, is the argument. It is now also the infrastructure. Build it deliberately.
