Agentic Advertising Standards (IAB Tech Lab)

Table of Contents

  1. Definition
    1. How It Relates to Marketing
  2. How the Standards Work
  3. How to Utilize the Standards
  4. Comparison to Similar Approaches
  5. Best Practices
  6. Future Trends
  7. Frequently Asked Questions
  8. Related Terms
  9. Sources

Definition

Agentic advertising standards are the technical specifications that let AI agents plan, negotiate, and execute advertising transactions with each other in a consistent, interoperable way. The leading effort comes from IAB Tech Lab, the global standards body for digital advertising, under the umbrella name AAMP — the Agentic Advertising Management Protocols. AAMP is the coordinating framework for all of the organization’s agent-focused specifications and open-source tools, developed with the broader advertising ecosystem. IAB Tech Lab formally named it on February 26, 2026, with CEO Anthony Katsur announcing it at the Beet Retreat event.

The naming itself solved a problem. Since late 2025, the industry had been treating individual pieces — the Agentic Real-Time Framework and the Agentic Audiences work — as if they were the whole program, which Katsur described as confusion in the market with real consequences. AAMP is the label for the coordinated whole, organized around three pillars: execution, protocols, and an Agent Registry. The core design principle is build, don’t rebuild. Rather than inventing a new foundation, IAB Tech Lab is “agentifying” the standards that already run digital advertising and layering agent capabilities on top.

Back to Top

How It Relates to Marketing

For advertisers, agencies, and publishers, these standards decide whether agentic media buying actually works across the partners they use or fractures into incompatible silos. The reasoning Katsur offers is direct: agents only create value when they can work together across platforms, partners, and workflows. Without shared standards, every buyer agent and seller agent would need a custom integration with every counterparty — the same interoperability problem that open standards like OpenRTB solved for programmatic a decade ago, now reappearing at the agent layer.

The practical stakes show up in who’s adopting it. PMG integrated its Alli operating system with AAMP’s Buyer Agent architecture and Agent Registry in April 2026 to enable standards-based agentic media buying. Kochava folded the AAMP Buyer Agent SDK into its StationOne platform as an open-source workspace for testing AAMP workflows. And the Agent Registry drew participants including Amazon within weeks of launch. The argument industry leaders keep making is that these existing standards represent compressed knowledge refined through billions of transactions, so building on them is faster and less fragmenting than introducing competing new ones. For a marketer, that translates to a bet worth tracking: if AAMP becomes the common layer, agentic buying scales; if it splinters, the efficiency gains stall.

Back to Top

How the Standards Work

AAMP extends a robust base of established advertising standards into the agentic execution layer. The foundation includes transaction and delivery standards like OpenRTB, AdCOM, OpenDirect, VAST, and the Deals API; measurement standards like the Open Measurement Interface Definition (OMID) and the ECAPI outcome specification; privacy frameworks like the Global Privacy Protocol (GPP) and the Transparency and Consent Framework (TCF); and core taxonomies for ad products, audiences, content, and privacy. In 2026, IAB Tech Lab began agentifying these and releasing Agentic Protocol SDKs on top of them.

The three pillars organize the work:

  • Execution covers how agents actually carry out media operations, anchored by the Agentic Real-Time Framework (ARTF), which defines how agent services run in real-time environments for fast, reliable execution. It was released for public comment in November 2025.
  • Protocols translate the existing standards for machine-speed agent use, including Protocol Buffers and gRPC mappings, plus alignment with modern agent protocols. The Agentic Audiences schema (formerly the User Context Protocol) standardizes audience signals for agents.
  • Agent Registry sits at the top layer as a free directory where companies register their agents and discover others to work with, bringing trust and transparency to the ecosystem.

A few specifics matter for understanding the current state. The standards lean on the Model Context Protocol and Agent2Agent (A2A) for agent communication — when the registry first expanded to ten agents in March 2026, all ten were MCP servers, with no A2A entries yet. IAB Tech Lab also published open-source Buyer and Seller Agent SDKs built on AdCOM and OpenDirect, and released a Commerce Protocol (CoMP) specification requiring AI systems to have commercial agreements in place before transacting. The organization is prioritizing trust, provenance, measurement, and transaction-integrity signals throughout.

Back to Top

How to Utilize the Standards

For most marketing organizations, engaging with these standards is less about implementing protocols directly and more about choosing partners and tools that support them. The clearest near-term moves: confirm that ad-tech vendors and agency platforms are building toward AAMP-compatible buyer and seller agents, watch the Agent Registry for counterparties to work with, and treat standards alignment as a procurement criterion the way programmatic buyers once treated OpenRTB support.

Teams building their own agentic capabilities have more direct entry points. The open-source Buyer and Seller Agent SDKs demonstrate how agents integrate with existing advertising systems, and platforms like Kochava’s StationOne offer a workspace to test AAMP workflows before committing. Registering an agent in the directory is free and improves discoverability.

Common use cases sit across the media-buying lifecycle: standards-based agentic media buying where a buyer agent transacts with seller agents, automated planning and execution at machine speed, measurement and compliance handled through the agentified specifications, and cross-partner coordination that depends on interoperability. A grounding note worth keeping: AAMP is early and evolving. Several components remain in post-comment review with industry feedback being incorporated, so the standards a brand builds against in mid-2026 are still moving.

Back to Top

Comparison to Similar Approaches

Standard / EffortPrimary domainBacked byRole
AAMP (IAB Tech Lab)Agentic advertising execution and interoperabilityIAB Tech Lab and the ad ecosystemIndustry-wide standards for agent-driven advertising
Ad Context Protocol (AdCP)Agentic ad transactionsIndependent / openA specific protocol for agent ad buying
Model Context Protocol (MCP)Agent access to tools and dataAnthropic, broad adoptionGeneral agent capability layer AAMP builds on
Agentic Commerce Protocol (ACP)Retail checkout in AI interfacesOpenAI, StripeConsumer purchase, not advertising

The key distinction is scope. AAMP is an industry-wide umbrella specifically for advertising, assembled by the body that already sets digital advertising standards, and it deliberately builds on the existing OpenRTB-era foundation rather than replacing it. The agent communication protocols it relies on, like MCP and A2A, are general-purpose layers AAMP adopts rather than competes with. Commerce protocols like ACP solve a different problem entirely — a consumer’s purchase inside an assistant, not the machine-to-machine buying and selling of ad inventory.

Back to Top

Best Practices

  • Treat AAMP compatibility as a partner and vendor selection criterion, the way OpenRTB support became table stakes in programmatic.
  • Monitor the Agent Registry for counterparties and for which deployment types and protocols are actually live.
  • Use the open-source Buyer and Seller Agent SDKs and test workspaces to prototype before building production agents.
  • Build on the existing standards the SDKs are trained on rather than inventing parallel ones, to avoid fragmentation.
  • Prioritize the trust, provenance, and measurement signals the framework emphasizes, since interoperability without integrity invites fraud.
  • Expect change and version against current specs deliberately, since several components are still in review.
Back to Top

The momentum through early 2026 was toward making the standards practical rather than theoretical. The Agent Registry moved from announced to operational within weeks, integrations with platforms like PMG’s Alli and Kochava’s StationOne arrived, and the CoMP specification added a commercial-agreement requirement that signals where governance is heading. The recurring industry message is that intent, execution, and governance have to evolve together for agentic advertising to scale.

Two directions are worth watching. The first is the MCP-versus-A2A balance in the registry — every early entry was an MCP server, and whether A2A adoption follows will shape how agents coordinate. The second is consolidation versus fragmentation, the central tension the whole effort addresses: IAB Tech Lab is betting that one shared foundation built on proven standards beats a proliferation of competing ones, and the degree of ecosystem buy-in over the next year will test that bet. For marketing, AAMP connects the advertising-specific corner of agentic commerce to the broader stack — it’s the layer that decides whether the media-buying agents now appearing across the industry can actually transact with one another.

Back to Top

Frequently Asked Questions

1. What is AAMP? AAMP stands for Agentic Advertising Management Protocols, IAB Tech Lab’s umbrella framework for the standards and open-source tools that let AI agents plan, negotiate, and execute advertising transactions interoperably. It was formally named in February 2026.

2. Why did IAB Tech Lab create it? To bring its scattered agentic work under one coordinated name and to enable interoperability. Agents only create value when they can work together across platforms and partners, and shared standards make that possible.

3. What are AAMP’s three pillars? Execution (how agents carry out media operations, via the Agentic Real-Time Framework), protocols (translating existing standards for machine-speed agent use), and the Agent Registry (a directory of agents for discovery and trust).

4. Does AAMP replace existing ad standards? No. It extends them. IAB Tech Lab is agentifying established standards like OpenRTB, AdCOM, OpenDirect, and VAST rather than rebuilding the foundation, on the logic that they represent knowledge refined through billions of transactions.

5. What is the Agent Registry? A free directory where companies register their agents and find others to work with, aiming to bring trust and transparency to agentic advertising. Early entries were all Model Context Protocol servers, with participants including Amazon.

6. How does AAMP relate to MCP and A2A? It builds on them. MCP and Agent2Agent are general agent-communication protocols AAMP adopts for agent coordination, alongside gRPC and Protocol Buffers for high-performance execution.

7. Is anyone using it yet? Yes. PMG integrated its Alli operating system with AAMP’s buyer agent architecture, Kochava added the Buyer Agent SDK to its StationOne platform, and the Agent Registry launched with multiple active participants. It’s early but seeing real adoption.

8. How should a marketer engage with it? Mostly by choosing AAMP-compatible vendors and platforms and tracking the registry. Teams building their own agents can use the open-source SDKs and test workspaces, while remembering the standards are still evolving.

Back to Top
Back to Top

Sources

Back to Top

Tags: ,

Was this helpful?

Previous

Agent2Agent (A2A) Protocol

Next

Agentic AI as a Service (AaaS)