Artificial Intelligence

What Becomes Possible with the Right Contex

The infrastructure has been the argument across this series. Once it is built, something changes about what a customer relationship is.

Fourth and final in a series. Prior articles: “The Artist Already Knew,” “The AI Data Layer,” and “The Context Has to Keep Up.

The first three articles in this series argued for infrastructure. Context is the defining variable in applied AI. Contextual infrastructure is a generational data layer — the AI Data Layer — continuing a trajectory that runs from the Universal Data Layer through the Customer Data Layer that the industry now calls the CDP. When the AI consuming that layer shifts from responding to acting, the layer itself has to keep up — continuous, bidirectional, governed every time context is assembled for a model rather than only at the moment it’s sent out, and closed into a loop that runs on top of the pipelines feeding it.

Infrastructure was the right argument to make. It is also not the destination. Infrastructure is what makes the next set of possibilities real, and the next set of possibilities is what this final article is about.

I am going to be more speculative here than I have been in the prior three. Some of what I describe is already starting in production at organizations on the leading edge of this work. Some of it is still further out. All of it is closer than most people think, because the underlying infrastructure that makes it possible is being built right now — by companies who walked the trajectory I have described in this series deliberately.

In the near term, three things change about how organizations relate to their customers.

The first change is that the customer profile stops being a record and starts being a representation. A representation, in concrete terms, is a continuously updating digital model of a person — not just what they have done, but where their attention is right now and where it seems to be going. The CDP era produced something close to a digital file cabinet — a unified, identity-resolved set of facts about a person, queryable on demand, updated in batch or in stream. What comes next is materially different. The representation carries the historical record but adds behavioral patterns, predicted preferences, current state of attention, and a sense of where this person is heading — what they seem to be considering, what would matter to them next. Industry analysts have started calling this the digital twin of the customer, and the name fits, because what is being built really is a continuously updating synthetic version of a real person, grounded entirely in consented first-party signal. The shift from record to representation is the shift from looking up a customer to having one.

The second change is that organizations start running their decisions through the representation before running them on real customers. This is the most immediately practical consequence of the digital twin, and the one most likely to land first in production. Today, most marketing and customer experience decisions are tested against live customers — A/B tests, controlled rollouts, post-hoc analysis. Even when limited to a subset of the audience, that approach exposes real customers to experiences the brand does not yet know are good. The paradigm tolerates a baseline rate of failure because it has no alternative. With high-fidelity customer representations available at scale, organizations can simulate journeys, test agent behaviors, and probe decision logic against synthetic populations before committing anything to the real world. A decision that would have been launched and measured can be modeled, refined, and validated first — without putting any real customer through a suboptimal experience to find out. The risk profile of customer-facing decisions starts to look like the risk profile of well-engineered software, where bugs are caught before they reach production.

The third change is that the customer arrives with their own agents. Most customer infrastructure today assumes the customer interacts with the brand through the brand’s own systems. That assumption is already starting to break. A customer in the next year or two will increasingly have personal agents working on their behalf — calendar agents, payment agents, travel agents, shopping agents. Some of those will be embedded in their phone’s operating system. Some will be third-party services they have authorized. Some will be their employer’s. From the brand’s perspective, the practical implication is that a single customer interaction may involve four or five agents acting in concert, each carrying different scope, different permissions, and different needs. The contextual infrastructure has to make the brand legible to all of them while keeping a coherent view of the customer underneath. This is not science fiction; the agent platforms and protocols to make it possible are already in market. The infrastructure to participate in it credibly is the work this series has been describing.

The deeper shifts get more interesting.

The first deeper shift is that the brand builds a twin of itself. Today, a customer twin is something the brand looks at — a tool for making better decisions about that customer. Tomorrow, the brand will have its own twin: a live model of its products, prices, services, and policies that can engage with the customer’s twin directly. The two twins work out an answer between themselves — what offer, what timing, what configuration would fit this person right now — before either side commits. By the time the customer sees the interaction, the work is already done. What used to be a negotiation becomes a confirmation.

The second deeper shift is the disappearance of the campaign as the primary unit of customer engagement. The campaign — a planned, time-bounded effort to move a group of customers from one state to another — has been the operating unit of marketing for fifty years. It assumes a world where decisions are planned in advance and measured afterward. When AI maintains a real-time, continuously updating understanding of each customer, that planning model becomes unnecessary. A continuous stream of small, contextual, simulated-and-validated decisions replaces the discrete campaign. What the customer experiences is an interaction that is always responsive to who they currently are. What the organization manages is the quality of the representation, the integrity of the agents acting on it, and the policies that govern what gets committed to the real world.

The third deeper shift is that customer context becomes the compounding asset of the modern enterprise. For thirty years, customer data has largely been treated as exhaust — a byproduct of operations, occasionally useful, often expensive to clean. That is changing. Across this series, customer context has moved from being infrastructure, to being a strategic asset, to being the asset. The organizations that get there first will not be the ones with the best models, the largest data warehouses, or the most sophisticated agents. They will be the ones who built the contextual layer most deliberately, governed it most carefully, kept it updating in real time, and let it compound the longest. The compounding part is what is easiest to underestimate. Every consented interaction makes the customer twin a little more accurate. Every layer of governance and identity makes the infrastructure a little more capable. The advantage opens slowly — and then, very quickly, becomes structural.

I have been honest across this series that no single vendor, including Tealium, has fully solved any of this, and the deeper shifts in particular are still being figured out by the industry as a whole. What I will say is that the trajectory I have described — Universal Data Layer to Customer Data Layer to AI Data Layer, with the infrastructure for agents in motion already taking shape — has been Tealium’s trajectory. We have spent three generations of architecture preparing for the moment when customer context stops being a marketing tool and becomes the strategic substrate for everything an enterprise does with AI. The market is starting to corroborate the trajectory directly: Scott Brinker’s 2026 State of Martech analysis, released in May, recorded just 0.79% net growth in the marketing technology landscape over the past year — what Brinker called “peak martech.” Beneath the flat headline, the AI-wrapper era is being culled while infrastructure-oriented categories continue to emerge. The ideas in this article are the implications of the trajectory I have walked you through in this series carried forward. Some of these ideas are already on Tealium’s path. Others will require capabilities none of us has invented yet. All of them are why I think this is the most consequential decade for customer infrastructure in a generation.

Four articles ago I opened with Marcel Duchamp and the urinal he submitted to an exhibition in 1917. The argument was that the meaning of an object is not in the object — it is in the frame around it. I have come back to the frame at the end of every article since, because the metaphor has carried each successive argument naturally: the frame is the argument, the frame is the infrastructure, the frame has to hold while the agent acts.

What I want to say in closing is that the frame, eventually, becomes the relationship. The thing we have been building across these four articles is not a better data system. It is a new way for organizations to know the people they serve — continuously, faithfully, and with their consent — and a new way for those people to be served back. The infrastructure is the means. The relationship is the end.

Artists have always known that a frame is not decoration. The frame, built deliberately, is what lets the thing inside become what it is.

It is time we built our customer infrastructure accordingly.

Nick Albertini
Global Field CTO, Tealium
Back to Blog

Ready to see how Tealium fits your stack?

Truman, our AI-powered consultant, gives you instant answers about integrations, features, and implementation—no waiting for sales calls.

Ask Truman a Question