A deal ID is a text string that identifies a specific agreement between a buyer and a seller of programmatic advertising. The seller's platform generates it, the buyer enters or accepts it in a demand-side platform (DSP), and from that point the string travels inside every eligible bid request, signalling that the impression on offer is available under negotiated terms rather than on the open market. It exists because automated auctions, left alone, treat every bidder the same way. Publishers wanted to reserve inventory, prices and priority for chosen buyers without returning to faxed insertion orders, and the deal ID is the token that lets the machinery recognise those arrangements one impression at a time.

How a deal ID travels through the auction

The identifier lives in OpenRTB, the IAB Tech Lab protocol that carries most automated ad trading. Each impression object in a bid request can contain a pmp (private marketplace) object, which the 2.6 specification describes as a container for direct deals. Inside sits an array of Deal objects. Only one field is mandatory: id, a string the specification calls a unique identifier for the direct deal. The rest set the terms. The bidfloor field states the minimum price per thousand impressions (CPM), bidfloorcur gives the currency and defaults to US dollars, and at can override the auction type, where 1 means first price, 2 means second price plus and 3 means the floor is the agreed deal price. A wseat array lists the buyer seats permitted to bid, and wadomain restricts eligibility to named advertiser domains.

One flag changes the character of the whole impression. When private_auction is set to 1, only bids against the listed deals are accepted; at 0, open market bids compete too. A guar field marks a guaranteed deal on which the bidder must bid, and for audio and video the mincpmpersec and durfloors fields let sellers price by creative length. According to the implementation guidance, a seller should supply only one form of floor inside a given Deal object.

The return journey is simpler. A DSP bidding under an agreement copies the string into the dealid field of its Bid object. The exchange matches it, applies the terms and decides the winner. As the Explaining buyer entry sets out, a seat identifies who is buying while a deal ID identifies the terms under which inventory is sold.

A worked case shows the order of events. A publisher's sales team agrees a USD 12 floor on sports video with one agency. Its supply-side platform (SSP) creates the deal, the agency accepts it in its DSP and attaches it to a line item, and each matching request then arrives carrying the ID. Where header bidding is involved, Prebid.org documentation describes a key-value pattern, hb_deal_ followed by the bidder code, which the publisher's ad server line item targets so the deal can be prioritised there.

The IAB Tech Lab guidance adds rules that are often ignored. It recommends that a deal ID be used whenever an impression may be awarded on grounds other than price alone, and that DSPs return at least one deal bid plus two open market bids, what it calls "1+1" as a minimum and "M+N" as the ideal. It lists anti-patterns, including attaching the ID to a seat or advertiser instead of to a line item, and silently shaving margin off deal bids.

The deals behind the identifier

The same field carries very different commercial arrangements. Google Ad Manager's help centre associates a deal ID with Preferred Deals, Private Auctions, Programmatic Guaranteed and Marketplace Packages, and describes the ID in reporting as a system-generated number, with "0" shown when no deal was involved. A preferred deal gives one buyer first look at a fixed price; a private auction invites several buyers to bid above a floor; programmatic guaranteed deals fix both price and volume. PPC Land's real-time bidding explainer summarises the middle case as RTB with an invitation list.

Origin and evolution

AdExchanger's 2018 history of programmatic places the birth of DSP private marketplaces and deal ID functionality in the early 2010s, when automated buying began absorbing work once done through insertion orders. In September 2013 the IAB's Programmatic Publishers Task Force published a paper defining four transaction types, automated guaranteed, unreserved fixed rate, invitation-only auction and open auction, and it addressed deal ID alongside prioritisation and floors. OpenRTB 2.2, dated April 2014, added what its version history calls enhancements for private marketplace direct deals, formalising the pmp and Deal objects. Later releases kept the structure and extended it: the 2.6 line brought ad pods for connected television (CTV), and the July 2023 revision added mincpmpersec and durfloors to the Deal object.

Setup remained manual for years, with buyers typing strings copied from emails. Synchronisation arrived through platform APIs; Smart integrated the DV360 API for deal synchronisation in March 2022, removing manual registration errors for its buyers. The IAB Tech Lab formalised its curation standards in December 2024, which then made the deal ID the default delivery vehicle for packaged data and inventory.

Why the string matters to marketers

Curation turned the deal ID from a publisher-direct tool into a distribution format. OpenX's Cookieless Deal Libraryoffered more than 1,000 pre-built IDs in February 2024. The German trade association BVDW, in a March 2026 curation whitepaper, described the output of curation as data-inventory packages delivered through standardised deal IDs in DSPs. The logic is partly technical: when data is applied once at the supply layer, industry analyses cited in PPC Land coverageput the match rate lost at each platform hop between 40% and 70%.

Data owners have followed. LinkedIn's audience programme through Microsoft Monetize requires a buyer's seat name and seat ID before a deal can be generated, a step that can take up to five business days, and the buyer sees only the segment encoded in the deal. Magnite gave advertisers a route to Acxiom data through deal IDs in August 2025.

Limitations and disputes

Deals frequently fail to deliver. When The Trade Desk launched Deal Desk in June 2025, its internal analysis claimed 90% of deal IDs fail to scale, a vendor figure not independently verified. Nick Allen of Magnite said two-thirds of deals configured with the desired supply deliver no or very little revenue, according to the IAB Tech Lab's December 2025 announcement. Both companies sell tools addressing the problem. Google's Ad Manager troubleshooting guidance points to familiar causes: buyers bidding through other sources or under the wrong deal ID, and overlapping private auctions with the same buyer that split delivery.

Transparency is the second dispute. A deal ID says nothing about who packaged it or what they charge, and the SupplyChain object does not disclose node fees either. Curation fees sit inside the price. Executives at IAB Europe's Virtual Programmatic Day on July 3, 2025 debated whether curation was genuine innovation or rebranded private marketplace practice.

Standards compliance is uneven. The IAB Tech Lab's anti-pattern list exists because platforms do run deal bids through internal price auctions and apply silent discounts, both of which can prevent delivery.

Not the same as

Seat ID. Identifies the buying account, not the agreement. A deal can restrict eligibility by seat through wseat, but the two are not interchangeable.

Private marketplace. The environment or transaction type. The deal ID is the token that addresses a specific agreement within it.

Transaction ID. A per-auction identifier used to deduplicate the same impression across exchanges. It changes with every opportunity, while a deal ID persists for the life of an agreement.

Order or line item ID. Internal objects in an ad server or DSP. In Google's DV360 Seller API, a seller's external deal ID becomes an inventory source nested under an order and product, objects that exist only inside the buying platform.

Recent developments

Manual entry is being phased out. Microsoft's publisher documentation for Monetize states that DV360 no longer supported manual deal creation in its interface as of August 7, 2023, while Google's DV360 roadmap listed April 2026 for deprecating manual non-guaranteed deal creation platform-wide, making the Deal Sync API the only route. The IAB Tech Lab released a Deals API for comment in December 2025, naming origin, seller and curator domains and encoding curation fee type as undisclosed, percentage, flat, CPM or none. The specification was marked final on February 6, 2026.

Deal portability is widening too. Google Ad Manager's beta agency deals carry a universal deal ID that an agency can use across all of its DSPs, instead of one deal per platform. Automation is also moving into deal selection. Amazon DSP's automatic deal selection assembles and prunes streaming TV deal IDs during a flight. The Trade Desk's Q2 2026 Kokai release upgraded Deal Desk, and in July 2026 Netflix inventory opened beyond private deals to The Trade Desk's wider marketplace. VIOOH's Seller Agent created more than 100 curated DOOH deal packages in the first half of 2026, and in August Jeff Green described rivals wrapping fixed-price deals in agentic tools at roughly 1% fees. Whichever agent negotiates, the output as of September 2026 is still a string in the pmp object.

Timeline

  • September 2013: IAB publishes "Programmatic and Automation - The Publishers' Perspective", defining four transaction types and addressing deal ID
  • April 2014: OpenRTB 2.2 adds private marketplace direct deal enhancements, formalising the pmp and Deal objects
  • March 30, 2022: Smart integrates the DV360 API for automatic deal synchronisation
  • July 2023: OpenRTB 2.6-202307 adds mincpmpersec and durfloors to the Deal object
  • August 7, 2023: DV360 no longer supports manual deal creation in its interface, according to Microsoft's Monetize documentation
  • December 16, 2024: IAB Tech Lab formalises its curation standards
  • June 9, 2025: The Trade Desk announces Deal Desk
  • August 2025: Magnite opens Acxiom data to buyers through deal IDs
  • December 2025: IAB Tech Lab releases Deals API version 1.0 for public comment
  • February 6, 2026: Deals API marked final at version 1.0
  • March 3, 2026: BVDW publishes its programmatic curation whitepaper
  • April 2026: DV360 deprecates manual non-guaranteed deal creation; Deal Sync API becomes the only route
  • May 2026: Amazon DSP introduces automatic deal selection for streaming TV
  • June 26, 2026: VIOOH reports more than 100 agent-created DOOH deal packages in the first half
  • July 20, 2026: Netflix inventory opens to The Trade Desk's Sellers and Publishers 500+ marketplace

Summary

Who. Publishers and their SSPs, ad servers and curators create deal IDs; agencies and advertisers accept and target them in DSPs such as Display and Video 360, The Trade Desk and Amazon DSP. The IAB Tech Lab defines the fields through OpenRTB and, since 2026, the Deals API.

What. A string identifying a pre-negotiated agreement, carried in the Deal object of an OpenRTB bid request and echoed in the dealid field of the bid. It can represent a private auction, a preferred deal, a programmatic guaranteed buy or a curated data package.

When. The mechanism spread in the early 2010s, was addressed by the IAB in September 2013 and formalised in OpenRTB 2.2 in April 2014. Synchronisation APIs replaced manual entry from the early 2020s, and Google made its Deal Sync API mandatory for new non-guaranteed deals in DV360 in April 2026.

Where. In the pmp object of each impression in server-to-server auctions, in hb_deal key-values inside header bidding setups, and in the deal interfaces of SSPs, ad servers and DSPs across display, video, CTV, audio and digital out-of-home.

Why. Open auctions treat every bidder alike. The deal ID lets sellers grant chosen buyers priority, price and data access while keeping the efficiency of automated trading, at the cost of setup friction, frequent under-delivery and limited visibility into who packaged a deal and what they charge.