The Eighteen Protocols Behind Agentic Advertising — And Why Your Team Doesn't Need to Know Them All

In every discussion about agentic advertising, sooner or later a diagram appears that looks like a wiring schematic and reliably intimidates marketing leads. Eighteen named protocols, distributed across seven functional classes, with arrows between them suggesting that everything connects to everything else. ads.txt, sellers.json, app-ads.txt, OpenRTB, Prebid.js, OpenRTB Native, VAST, VMAP, SIMID, SCTE-35, TCF and GPP, PAAPI, UID2, MRAID, SKAdNetwork, OM SDK — and for about eighteen months now the agentic layer with MCP, AdCP, AIP, AdMesh, and AAMP. The question every CMO instinctively asks is legitimate: do I now have to understand all of this to play in agentic marketing operations?

The short answer is: no. The long answer is that you need an architecture which hides exactly this complexity. Before we get to the architecture, however, it pays to sort the eighteen protocols once — not to memorize them, but to understand the structural logic behind them. Four govern the supply chain — who is allowed to sell what to whom. Three govern the bidding itself — how a real-time bid lands on an ad slot. Four govern video-specific delivery. Two govern privacy and consent. One governs identity. Two govern mobile-specific effects. One governs measurement. And five — the youngest — govern the agentic layer.

The agentic layer is the only one where active definition work is happening right now. MCP, the Model Context Protocol, governs how an AI agent talks to external tools. AdCP, the Agentic Discovery and Capabilities Protocol, governs how agents find each other and describe their capabilities. AIP and AdMesh address agent identity and agent-to-agent routing. AAMP, the IAB Agentic Advertising Marketing Protocol, is the industry-wide attempt to cast agentic buyer-seller workflows into a common data format. These five protocols sit today at different maturity levels — some are standards drafts, others are already in production. Anyone landing on the wrong side of these standards will have an integration problem in eighteen months.

That is the actual strategic difficulty. There are too many protocols, there is no unified standard yet for the agentic layer, and regulation plus governance are being renegotiated. With current infrastructure, agentic mediabuying is technically possible but operationally not yet realistic — because no marketing team in Switzerland has the capacity to integrate, maintain, and protect against standards drift across all eighteen. This is the task of a platform layer, not of a CMO office.

We have therefore built an architecture inside the opua brand family that deliberately abstracts this protocol complexity. The Digital Campaign Manager — DCM — takes the role of the agent orchestrator and speaks with all relevant protocols without the marketing team needing to know any of them. The sell-side connection runs via our sister platform Nexbid, which natively implements AdCP, AAMP, and the payment layer x402. The programmatic connection runs via OpenRTB 2.x and Prebid.js. Privacy and consent are handled via TCF and GPP. Identity runs via UID2 in markets where cookie identity is still viable, and via contextual signals where it is not. Measurement happens via OM SDK plus our own MMM backbone.

The unified steering logic on top is what makes the difference. DCM accepts KPI hierarchies — goals, trade-offs, tie-breakers — in a machine-readable form and translates them into target values that each individual protocol understands. A brand-safety requirement becomes inclusion lists in OpenRTB. A frequency cap becomes user capping in AdCP. A consent status becomes a TCF vector. A budget constraint becomes bid-floor logic. This happens in the platform, not in the head of a media planner. The marketer formulates the steering logic once, the system continuously translates it into the eighteen languages the ad-tech ecosystem speaks.

Strategically this is the most important architectural decision a company can make for agentic marketing operations. Anyone betting today on a single US-based SaaS vendor depends on that vendor's protocol choice. If the vendor decides tomorrow not to support AAMP or to replace MCP with a proprietary format, the CMO office has no negotiating power. Anyone betting on a modular orchestrator architecture — DCM as cockpit, Nexbid as agent stack, MMM-Wizard as attribution backbone, AiCMO as AI-citation layer — can swap individual protocols without replacing the entire stack. That is the Swiss answer to US vendor concentration.

Pragmatically there are three protocols a marketing lead should engage with personally, because they will dominate the strategic discussion of the next twelve months. First, AAMP, because it is the standard the IAB Tech Lab members are currently co-writing — anyone listening here understands the direction agentic buyer-seller workflows are converging toward. Second, AdCP, because it defines how agents find other agents — the foundation of every cross-platform activation. Third, x402, the payment layer out of the Linux Foundation ecosystem, which establishes HTTP 402 as the standard for machine-triggered micropayments. Whoever knows these three is strategically capable of acting. Everything else is platform implementation work.

What we see in practice is the following division of labor. The CMO office defines KPI hierarchy, brand-safety corridors, target markets, and escalation policy. The platform — DCM plus Nexbid plus MMM-Wizard plus AiCMO — translates these constraints into protocol configuration and watches them continuously. The performance teams work on output review, calibration, and bias audit. Nobody has to read OpenRTB 2.6 specs. Nobody has to debug VAST wrappers. Nobody has to track IAB Tech Lab working group sessions. That is the actual reason why agentic marketing operations are becoming accessible for Swiss companies now — not because agents got smarter, but because the orchestrator layer is finally there.

Anyone wanting to check which protocols their own marketing setup currently uses — and which they should add as a next step — can request a two-hour architecture analysis at audit@digital-opua.ch. The audit shows which of the eighteen standards are currently relevant, which can be delegated, and which remain critical for your industry. Anyone wanting to see the DCM agent orchestrator live before the pilot beta opens in Q3 2026 can sign up at demo@digital-opua.ch. And anyone wanting to study the open reference implementation of the agentic protocol stack can find the Nexbid codebase at github.com/nexbid-dev/protocol-commerce, licensed under MIT. The eighteen protocols stay. What changes is who has to know them.