The Deals API Is Final. Here's Why Your PMPs Keep Underdelivering

Ask any ad ops team about private marketplace deals and you will hear the same complaint: deals get set up, everyone agrees on terms, and then nothing spends. The IAB Tech Lab's Deals API, finalized as version 1.0 on February 6 after a public comment period that ended January 31, is aimed squarely at part of that problem. When the spec was released for comment in December, Magnite's Nick Allen was quoted as saying that "two-thirds of deals are configured with the desired supply, yet deliver no or very little revenue."

Whether or not that figure matches your own experience, the pattern is familiar. Here is what the Deals API does, what it does not do, and how to troubleshoot underdelivering deals with the tools you have today.

What the Deals API does

Today, a deal typically gets created in an SSP and then entered separately in a DSP, often by hand, sometimes by email or spreadsheet. The Deals API standardizes that handoff.

• Push and query. One system, typically an SSP, can send deal terms to another, typically a DSP, and then check the deal's status afterward.
• Named parties. The spec identifies the business entities involved in packaging a deal: the seller, the packager and, where relevant, the curator. That brings visibility into curated deals that the bid stream alone does not provide.
• Standard terms. High-level deal terms are communicated in a consistent format, reducing manual entry and the errors that come with it.

It is a separate API, not part of OpenRTB. It carries static deal terms. Implementers are expected to validate those terms against what actually shows up in real-time bid requests.

What it does not do

The Tech Lab is explicit that version 1.0 does not cover proposals, negotiation or marketplace discovery. It communicates deals that have already been agreed. So it will not help buyers find your inventory, and it will not settle pricing. It also depends on adoption: until your SSPs and your buyers' DSPs implement it, nothing changes in your workflow.

Why curation makes this urgent

Curated deals, where a third party packages inventory from many publishers with data and sells it as a deal, have grown quickly. For publishers, curation can bring new demand. It can also make it hard to know who is selling your inventory, at what markup, and to whom. The Deals API's explicit naming of curators and packagers is a step toward the transparency sellers have been asking for. Ask your SSPs when they will support it and whether that information will be visible in your reporting.

Troubleshooting underdelivering deals today

Standards take time to roll out. In the meantime, most deal failures come from a short list of causes. Work through them in order.

1. Is the buyer actually bidding?

Check the deal's bid requests, bid responses and bid rate in your SSP. If the buyer sees requests but never responds, the problem is usually on the buy side: campaign not live, deal not attached to a line item, budget exhausted, or deal ID typed wrong. Send the buyer the data, not just an "it's not spending" note.

2. Is the deal floor realistic?

If bids arrive but lose, compare them with the deal floor and with your open-auction clearing prices. Deals priced well above what the buyer's campaign settings allow will not win. Neither will deals whose floor sits below competing open market bids, when your ad server lets those compete at equal priority.

3. Does the targeting match your real inventory?

Many deals target ad sizes, geographies, devices or content categories that barely exist on your site. A video deal targeting a player size you do not use, or a deal limited to a region that is a small share of your traffic, cannot scale. Forecast available volume before setting a deal live.

4. Is the ad server prioritizing the deal correctly?

In your ad server, check where deal line items sit relative to direct campaigns, price priority lines and header bidding line items. A deal that is technically winning in the SSP can still lose at the ad server if priorities or pricing rules are misaligned.

5. Are the right signals in the request?

Buyers often target first-party data, contextual segments or viewability predictions. If your bid requests do not carry the signals the buyer's campaign requires, the DSP will filter them out silently. Confirm with the buyer exactly what the campaign targets, then confirm those fields are present in your requests.

6. Brand safety and verification filters

Third-party verification settings on the buy side can block impressions for reasons you cannot see. If bid rates are low with no obvious cause, ask the buyer whether pre-bid filters are applied and which pages are being excluded.

Make deals easier to succeed

• Standardize your deal setup template. Record every term, the targeting, the floor and the contacts on both sides.
• Check new deals within 48 hours. Most setup errors show up immediately as zero bids.
• Retire dead deals. Deals that never spend clutter reporting and waste troubleshooting time.
• Ask for Deals API support. Tell your SSP partners you want it. Adoption follows customer demand.

The takeaway

The Deals API will not make buyers spend, but it removes an avoidable source of failure and brings curators into view. Until it is widely adopted, disciplined troubleshooting is what separates deals that deliver from deals that sit idle. This is unglamorous work, and it is exactly the kind of work a managed ad ops team should be doing every week.