Ad Tech Briefing: IAB Tech Lab accelerates push to make agentic AI more practical - Digiday
The advertising industry has spent two decades building interoperability on a handful of well-worn standards — OpenRTB for real-time bidding, VAST for video ad serving, OpenDirect for direct deals. Those standards were designed for machines talking to machines in well-defined transactions. AI agents are different: they reason, they adapt mid-flight, they operate on briefs and constraints rather than rigid bid requests. The question is whether to extend what already works — the IAB's bet — or replace it with something built from the ground up for agents. That's the standards war nobody is calling a standards war yet, but everyone is fighting.
On March 24, 2026, the IAB Tech Lab formally integrated its AAMP Buyer Agent SDK into StationOne, Kochava's desktop orchestration platform, making the integration available to Tech Lab members to test and implement AAMP-based workflows. The move marks StationOne's exit from beta and the first time the Agentic Advertising Management Protocols — the IAB's umbrella standard for AI-driven ad buying — has shipped inside a real product, not just a spec document. StationOne itself is a downloadable app that CEO Sean Manning described as "an integrative AI hub — a fully downloadable app that brings together various different tools with various different skills across various different AI models." The app connects demand-side platforms, data tools, and campaign execution infrastructure via API keys and Model Context Protocol integrations. The pitch: agency and brand teams drowning in multiple DSP interfaces with divergent workflows use StationOne as a single orchestration layer rather than context-switching between platforms.
This is not a trivial architectural problem, and the infrastructure underneath is more concrete than the typical standards-body announcement. AAMP, formally named by the IAB Tech Lab on February 26, 2026, has three layers. The first is the Agentic Real Time Framework — ARTF — which defines how agent services run inside a host platform and can be called directly to accomplish bidstream processing tasks. ARTF uses OCI-compliant containers with gRPC and protobuf, no external network egress, and mandatory intent declarations. The stated goal is an 80 to 90 percent reduction in bid request-response latency — bringing round-trips down from 600 to 800 milliseconds to roughly 100 milliseconds. That threshold matters: an RTB auction must complete in under 100 milliseconds to participate. An agent that can't hit that window doesn't participate at all. The spec has been in public comment since November 2025 with v2.0 already underway, sample code exists on GitHub, and the Container Project Working Group includes 14 companies — Amazon Ads, Index Exchange, OpenX, The Trade Desk, Netflix, Yahoo, Paramount, Optable, HUMAN Security, Magnite, PubMatic, WPP Media, and Basis Technologies. The latency reduction claim comes from IAB Tech Lab's own documentation; independent production validation isn't available yet.
The second layer is Agentic Protocols: seven protocol components connecting buyer and seller agent hierarchies across the three-tier ad stack. The IAB's approach here is additive rather than disruptive — it extends OpenRTB, AdCOM, OpenDirect, VAST, Deals API, UCP, and CloudX with modern protocols including Model Context Protocol, Agent2Agent, and gRPC. The philosophical divide between this approach and the Advertising Common Protocol — AdCP — is the structural tension worth understanding.
AdCP, announced in October 2025 by six founding companies (Scope3, Yahoo, PubMatic, Swivel, Triton, and Optable), was built natively for agents rather than extended from existing standards. The IAB's counter-argument, made explicitly by board member Alison Levin, is that extending what already works avoids fragmentation rather than solving it: "just because you design a new car, doesn't mean you need to build a new track." The AdCP camp's rejoinder is that agents need a clean-sheet protocol designed around their operational model, not a compatibility shim bolted onto OpenRTB. Neither side is obviously wrong. But the fragmentation risk is real: if agencies have to support both AAMP and AdCP integrations, the industry trades the cost of a single standard for the cost of two.
The third AAMP pillar is the Agent Registry — a trust and transparency layer that reached 10 registered agents as of March 11, 2026. The registry is where the standards war becomes operational. In a world where buyer agents negotiate with seller agents autonomously, you need a way to verify the counterparty is who it claims to be, that it's privacy-compliant, and that it's operating in good faith. The registry requires companies to validate domain names, legal entities, and privacy compliance IDs (GPP and TCF) before an entry is approved — a gating function that carries real regulatory weight. The March 11 update introduced a three-tier deployment classification: Remote (internet-accessible), Local (download and install), and Private (enterprise on-premise or VPC). Of the 10 current entries, nine are Remote and one is classified as Private. Zero Local deployments yet. That asymmetry reflects where ad tech vendor architecture lives today: mostly cloud-hosted, not on-premise. Notably, no A2A agents are registered yet — all 10 entries are MCP servers.
Amazon Ads's entry illustrates the timeline complexity. The Amazon Ads MCP Server entered open beta on February 2, 2026, at the IAB Annual Leadership Meeting — not in March. The March 11 date in the registry update marks its addition to the IAB Agent Registry, not the beta launch. Amazon's VP of product, Paula Despins, framed the value proposition at the event: a single integration replacing bespoke connections to individual ad platforms. The distinction matters for anyone tracking when the infrastructure actually became available versus when it appeared in the registry.
FreeWheel's MCP server, also announced in March 2026, is positioned as an infrastructure layer for agencies. PMG is confirmed as a pilot partner through its Alli OS platform, participating in FreeWheel's Buyer Cloud closed beta program — a separate initiative from the MCP server launch proper. The two programs are distinct: the MCP server handles the protocol layer; Buyer Cloud is FreeWheel's own agentic execution environment. Separately, PubMatic's AgenticOS — which powers its own agentic stack — ran a real campaign execution pilot that produced the most concrete data point on agentic ad buying available.
The Butler/Till test: real numbers, narrow scope
Butler/Till, an independent media agency, ran a fully automated campaign execution pilot with PubMatic's AgenticOS for Geloso Beverage Group across December 2025 and January 2026. The results were notable: an 82 percent reduction in supply chain costs — specifically DSP tech fees — a 40 percent lift in impressions delivered, and a 30 percent fall in cost-per-thousand rates. Video completion rate hit 98 percent. An independent audit by Jounce found an MFA (made-for-advertising) rate of less than 1 percent.
The efficiency gains came from compressing the DSP fee layer entirely — not from removing human judgment, but from bypassing the fee structure that human workflow typically triggers. The process itself is worth describing because it's not fully autonomous. Butler/Till's agent, built on Anthropic's Claude LLM, received a client brief written by human staff and communicated targeting parameters to PubMatic's agentic systems. PubMatic retrieved curated inventory, which was relayed back to agency staff for approval. Butler/Till's agent confirmed, and the remainder of the buy was handled automatically. "There were checks and balances throughout," said Gina Whelehan, group director of strategic partnerships at Butler/Till. Campaign setup time dropped 98 percent in PubMatic's own tests — from hours to minutes for configuration tasks. Ad tech consultant Jonathan D'Souza-Rauto noted that setup time is systemically underappreciated: "Everyone underappreciates how much time is spent in setting things up."
The important caveat is that this is a single campaign, run with a single DSP partner, for a single brand category. The structural question — whether this model holds across multiple SSPs, multiple DSPs, and multiple brand categories — remains open. Forrester analyst Evelyn Mitchell-Wolf told Digiday that SSPs like PubMatic will increasingly compete on the quality and explainability of their agentic systems rather than positional advantage: "That includes explainability, it includes transparency and trust building because we're still in the growing pains of this whole thing."
What this means for builders and investors
The AAMP integration into StationOne is real plumbing. Code exists, a desktop app exists, and an open-source workspace is available to Tech Lab members today. That's unusual for a standards body announcement and worth crediting as such — this isn't a roadmap or a working group whitepaper.
For investors and founders evaluating the ad tech agentic stack, the frame to hold is this: the money in this market is in the execution layer, not the protocol layer. AAMP and AdCP will compete, but the winning protocols will be invisible to buyers the same way TCP/IP is invisible to web users. The value is in what gets built on top — StationOne's MCP integration, Butler/Till's proof-of-concept campaign, PubMatic's AgenticOS. These are the leading indicators of where the work is.
The risk is the 1990s intranet problem: incompatible standards proliferating in a supposedly connected industry, with the market paying the integration tax until consolidation. The IAB Tech Lab has the membership, the relationships, and the GPP/TCF privacy compliance infrastructure to make AAMP sticky. Whether it can move fast enough before the AdCP camp and proprietary stacks like PubMatic's own AgenticOS establish beachheads is the open question.
The irony of a standards body publishing Agentic Advertising Management Protocols in March 2026 while the AdCP camp is already shipping open-source agents on GitHub is not lost on anyone following this space. The IAB has history, trust, and privacy compliance infrastructure. The newcomers have velocity and a clean slate. The actual battle — agency mindshare — is already underway.