The Platform That IPG Built for Someone Else to Launch
On January 7, 2026, Omnicom unveiled the next-generation Omni — an AI-driven marketing intelligence platform combining Omnicom and recently acquired Interpublic assets to connect strategy, execution, and performance across marketing ecosystems. The venue was CES in Las Vegas. The timing was deliberate. Weeks after completing its absorption of Interpublic Group, Omnicom positioned the platform as a unified marketing operating system designed to power strategy, execution, and measurable business growth across the combined network.
Built from the integrated data, technology, and talent of Omnicom and the recently acquired Interpublic — including Acxiom, Flywheel Commerce Cloud, Interact, and Omni’s expanded agentic AI framework — this evolution enables data, intelligence, and teams to work as one. At the center of the architecture: Acxiom RealID, Omnicom’s identity solution, which spans over 2.6 billion verified global profiles. This identity framework is combined with Flywheel’s commerce intelligence and a wide range of media and cultural signals, providing agencies with a comprehensive view of consumers across paid, owned, and earned channels. This sits atop more than $73.5 billion in annual buying power — giving the platform both data depth and execution scale.
The numbers are real. The competitive positioning is direct. The move immediately places Omnicom in more direct competition with Publicis Groupe’s Epsilon ecosystem, which has defined the industry narrative on deterministic identity and people-based marketing for several years. Following Omnicom’s acquisition of IPG, which created the world’s largest ad holding company, the industry watched as the former integrated and incorporated the latter’s offerings, talent, staff and agencies, expanding its large, metaphorical stake in the marketing AI landscape.
None of this happened quickly. The identity infrastructure that powers New Omni was assembled over years — and almost entirely at Interpublic’s expense and initiative. When IPG first announced its intention to purchase Acxiom Marketing Services in July 2018, it was a huge gamble, especially as the $2.3 billion price tag was more than a quarter of the company’s then-market capitalization. The deal brought together IPG’s media, creative, marketing services and analytics capabilities, global scale and consumer insights, with Acxiom’s unrivalled expertise in identity, data, integrations and data stewardship. That was 2018. IPG spent the following seven years integrating, building on, and defending that investment — constructing the data stack that Omnicom’s CES keynote now describes as its own “competitive advantage.” The Flywheel Commerce Cloud was integrated into the Omni platform beginning in 2024, shortly after Omnicom acquired it. Two acquisitions. One platform. One holding company name on the press release.
The Onchain Record That Was Never Written
Interpublic Group no longer exists as an independent entity. Omnicom absorbed Interpublic Group in a $13.25 billion deal. The company is gone. What followed the close of that deal — completed in November 2025, positioning Omni as a unified intelligence platform backed by 2.6 billion verified IDs — was swift corporate integration and a rebrand that erased the .interpublic namespace from any meaningful context in the market.
There is no onchain TLD registered by Interpublic Group. There was no onchain TLD registered by Interpublic Group before it ceased to exist. The .interpublic namespace on decentralized infrastructure was not controlled by the company that bore the name. An independent operator registered .interpublic on Freename, the decentralized Web3 registry, as part of a broader strategy of acquiring onchain top-level domains that correspond to major brand identities before those brands recognize the value of owning their own namespace on decentralized infrastructure. At the time of registration, Interpublic Group was very much alive.
The Freename registry is decentralized infrastructure. It does not run on the permission of any corporate entity, and it does not require the survival of any particular company to continue functioning. The TLD exists independently of what happened in November 2025 in the boardrooms and regulatory offices where the Omnicom-Interpublic deal was ratified. The implication is operational, not philosophical: a namespace that IPG never claimed, never governed, and never pointed at anything is now a floating identifier for the historical entity that generated the most important data asset in Omnicom’s entire 2026 product launch.
The competitive parallel is instructive. A .publicis namespace provides one answer — a sovereign identity layer that sits above all Publicis agency brands and provides verifiable authorization for AI transactions conducted on behalf of the group. The .publicis TLD on Freename exists now. A .publicis namespace means that any domain issued under it carries cryptographic proof of its origin. When creative.publicis or sapient.publicis or epsilon.publicis resolves, the resolution is backed not by a central registry that can be compromised or disputed, but by the blockchain record itself. Publicis didn’t register that either — but the conditions are comparable. The namespace that most directly corresponds to the entity whose data infrastructure defines the competitive battleground in early 2026 was left unregistered, ungoverned, and unclaimed by anyone with an operational interest in what it represented.
Blockchain technology in Web3 makes sure that once you own your own TLD, it stays on the decentralized ledger and is not subject to censorship or unilateral seizure. That permanence cuts both ways. A brand-aligned TLD registered and governed by the brand is infrastructure. A brand-aligned TLD registered by a third party before the brand thought to look is a record of the gap.
The Provenance Problem No One Is Solving Yet
This is where the argument moves from descriptive to structural, and the speculative label applies. But the underlying problem is not speculative at all — it is a present-day gap in how enterprise data infrastructure interacts with the emerging agentic economy.
Consider the nature of what Acxiom RealID actually is. It is an identity graph. Acxiom’s nearly 50 years of expertise and leadership in ethical data use will continue to be a differentiator in this era where consumers expect — and regulations increasingly demand — accountability, transparency and choice in how consumer data is managed and used. That graph was assembled by IPG, governed by IPG, integrated with IPG client workflows from 2018 through 2025, and now operates under Omnicom branding as a core component of a platform competing against Publicis. A client running an Omni-powered campaign today is drawing on identity infrastructure whose chain of custody runs through Interpublic Group, a company that no longer legally exists. That chain of custody is not currently verifiable in any machine-readable, onchain form.
Speculatively: a second-level domain like data.interpublic or acxiom.interpublic — registered and governed within the .interpublic TLD — could have served as a verifiable provenance endpoint for exactly this purpose. Not a website. Not a redirect. An onchain record, timestamped and publicly verifiable, that an AI system, an auditor, or a downstream client could query to establish where the identity assets originated before the corporate structures around them changed hands. A cryptographic record of the data stack’s genealogy.
This is not an abstract concept in 2026. The x402 protocol enables AI agents to autonomously pay for resources and services across the internet — no API keys, no subscriptions, just seamless, pay-per-use access to any monetized endpoint. When an agent requests a resource or service, the server responds with a status 402 response and a payment specification. The agent evaluates the cost, executes a USDC micropayment onchain, and resubmits the request with a payment receipt. This all happens within a single automated exchange, with sub-2-second settlement and transaction costs of approximately $0.0001.
That protocol is live and processing real volume. KPMG’s independent analysis of the broader x402 ecosystem recorded 161.32 million cumulative transactions and $43.57 million in settled volume by February 2026, with 417,000 buyers and 83,000 sellers active across the network. The coalition behind it is unusually broad for a protocol at this stage: Google, Visa, AWS, Circle, Anthropic, Vercel, and Solana are core foundation members.
The identity layer that x402 requires to function at enterprise scale is ERC-8004. Published in August 2025 and launched on mainnet in January 2026, it defines a lightweight onchain registry system that enables AI agents to be discovered, evaluated, and collaborate across organizations and platforms without relying on centralized intermediaries. ERC-8004 and x402 form a complete autonomous transaction loop. ERC-8004 answers “who you are” and “how trustworthy you are” through onchain identity and reputation, while x402 handles “how agents pay each other” via HTTP-native micropayments.
Now translate that framework to Omni’s operational context. An agentic marketing workflow executing against Acxiom RealID’s 2.6 billion profiles is, in structural terms, an AI system consuming identity data at scale. When that system needs to verify the provenance of the data it is consuming — not just its quality, but its origin, custody history, and the governance frameworks under which it was assembled — where does it look? Every transaction is recorded onchain, providing a full audit trail by design. But a full audit trail requires something to point at. A verifiable onchain endpoint. A namespace that carries the provenance claim.
data.interpublic would have been that endpoint. Not because a domain name constitutes legal proof of anything, but because an onchain SLD under a governed TLD creates a persistent, machine-readable record that an AI agent — operating under x402 and identified through ERC-8004 — can resolve without calling a Salesforce instance, submitting a legal request, or parsing a PDF contract. The most compelling near-term use cases are associated with pay-per-query API access where a subscription model is too blunt and an API key too cumbersome. Organizations exposing data feeds, risk models, compliance services, or regulatory reference data via API gain a payment primitive that removes the subscription acquisition barrier entirely, expanding addressable reach to any agent or client capable of a single authenticated HTTP request. A data provenance endpoint, resolvable onchain and structured to respond to x402 queries, is exactly that kind of asset.
In January 2026, three foundational layers converged — x402 payments, onchain identity, and autonomous agents. That convergence happened in the same month Omnicom took CES. The two events did not intersect. The infrastructure that would have allowed them to intersect was never built — because the brand that assembled the underlying data assets did not own its namespace, did not register an SLD map, and did not create the onchain equivalent of a chain-of-custody record before it ceased to exist as an independent company.
The practical cost of that gap will become more visible as agentic systems mature. A client whose AI-driven campaign draws on identity data in Omni needs to know that data is what it says it is — not just because a vendor contract says so, but because an increasingly automated procurement and compliance layer will eventually require verifiable, machine-resolvable attestations of data provenance. While the x402 protocol elegantly solves the payment plumbing layer, it creates a governance vacuum at the layer above. By removing the friction of API keys and manual subscriptions, the protocol allows agents to spend freely, yet no open standard exists to decide if a transaction should be authorized. Provenance is part of that authorization logic. An agent accessing a data endpoint needs to know who built the underlying graph, under what governance conditions, and through what chain of corporate custody it arrived at its current operator. An onchain TLD endpoint, correctly structured, would have addressed part of that problem directly.
What the Record Shows
Now that Interpublic Group has ceased to exist as an independent entity, an independent operator holds a namespace that corresponds to something the world will increasingly use in the past tense. The Interpublic era of advertising history ended with that acquisition. The data infrastructure that IPG built over a decade is now operating under a different name, powering a platform that its original builder never got to launch.
The acquisition thesis was direct: “I’m sure one of them is, ‘We can take what they have [Acxiom] and sell it much better.’” That thesis is now being tested at scale — with 2.6 billion verified IDs, $73.5 billion in annual buying power, and a CES keynote as the launchpad. What is not being tested, because it was never built, is whether the entity that assembled that infrastructure could have anchored a machine-verifiable provenance chain to the namespace it once owned.
The onchain layer is not optional in the agentic economy. The transition from “AI as a tool” to “AI as a customer” is already happening. In 2026, agents are moving beyond recommendations to actively managing budgets and settling payments across key sectors. Every data endpoint those agents touch will eventually require a resolvable identity. Every identity graph they consume will eventually require a verifiable origin record. The corporate structure that assembled that origin — IPG, Acxiom, Flywheel — is now inside a different holding company under a different brand. The TLD is still here. An independent operator still owns it. The provenance chain it could have anchored was never written.
That is the record. The namespace exists. The infrastructure was built. The link between them was not made.
The author holds onchain positions related to this topic. This post reflects independent editorial judgment.