16 Nov 2026 · 3 min read
What Happens When Your Agency's Platform and Your Publisher's Don't Speak the Same Protocol?
TL;DR: When a buyer's agent is built for one protocol or platform and a seller's agent is built for a different one, with no shared standard bridging them, the two systems simply can't exchange a structured request at all. That failure mode is quiet rather than dramatic, usually a missed opportunity rather than a visible error, which is exactly why it is worth naming plainly.
The failure mode in plain terms
Two agents that don't share a protocol are not able to negotiate badly, they are not able to negotiate at all. There is no common structure for a proposal, a counter, or an acceptance to travel through. In practice this doesn't look like an error message. It looks like a buying agent simply never discovering a piece of relevant inventory, or a selling agent never receiving a request it could otherwise have filled, because the two systems were never able to talk to each other in the first place. This is a quieter and more easily missed failure than a negotiation that goes wrong, because nothing visibly breaks, an opportunity simply never materialises.
Why this is becoming more likely, not less
As more individual platforms build their own agentic stacks, each one has an incentive to make its own ecosystem work well internally first, which is a reasonable product decision for any single company to make. The side effect, industry-wide, is a growing number of platform-specific agent implementations that were never required to speak to each other at all. Shared standards such as IAB Tech Lab's AAMP and AgenticAdvertising.org's AdCP exist specifically to reduce this fragmentation, by giving agents built by different companies a common structure to exchange requests through, but adoption of any shared standard takes time, and a buyer's agent and a seller's agent can each individually be well built and still fail to connect if they were built against different standards, or against no shared standard at all.
What actually mitigates this
A platform or agent that works within an open standard rather than only its own proprietary format is choosing interoperability over short-term convenience. This is part of why working within AAMP, rather than only building a closed ecosystem, matters beyond compliance: it is a direct bet against this specific failure mode, that a buying agent and a selling agent with no prior relationship, built by different companies, can still find each other and exchange a structured proposal because both sides chose to support the same shared format.
Frequently asked questions
Is this the same problem as the deal-record question covered in other pieces on agentic advertising?
No, it's an earlier-stage problem. A shared protocol is what lets two agents exchange a proposal at all. A deal record is what happens afterwards, once terms have actually been agreed, recording what was committed to. A platform could solve one of these problems and not the other.
Does supporting multiple standards solve this completely?
It reduces the risk considerably compared with supporting only one proprietary format, though full interoperability across every platform in the market is still a work in progress industry-wide, since standards themselves are still maturing.
What should a buyer ask a vendor to check for this risk?
Ask explicitly which open standards the vendor's agent supports, rather than assuming broad compatibility from a general claim of being "agentic." A platform that only speaks its own proprietary format is a narrower, more isolated choice than one built against a shared, multi-party standard.