Deal ID

A Deal ID is a unique alphanumeric identifier that both the buy side and sell side attach to a negotiated programmatic deal, whether that's a preferred deal, a private marketplace deal, or a programmatic guaranteed deal, so that any bid request carrying that ID is matched to the specific price, inventory, and terms the two parties already agreed on.

How a Deal ID works#

A publisher or its supply-side platform packages a slice of inventory (a placement, an audience segment, a content section) along with a price and any custom terms, then issues a Deal ID for it. That ID gets shared privately with one buyer, who enters it into their demand-side platform as a line-item target.

From there it's plumbing. Under OpenRTB, the Deal ID travels inside the bid request's deal object. When a matching impression fires, the SSP flags the bid request with that ID, and only the buyer holding it sees the negotiated terms, either as a guaranteed price with no competition or as a private auction with a negotiated floor, depending on the deal type. Everyone else's bids on that same impression, if there are any, go through the regular real-time bidding flow.

Why Deal IDs matter#

They let two parties negotiate like a traditional direct buy, fixed price, specific placement, custom terms, while still transacting through the automated programmatic pipe instead of a manually trafficked insertion order. Three deal types commonly ride on a Deal ID: preferred deals (fixed price, first look, no guarantee of volume), private marketplace deals (invite-only auction with a negotiated floor), and programmatic guaranteed (reserved volume at a fixed price, essentially an automated IO).

For buyers, a Deal ID is also the cleanest way to get consistent access to a specific publisher's inventory without relying on header bidding wins in the open exchange, where availability and price both move.

Where Deal IDs break#

Most "the deal isn't spending" tickets in ad ops trace back to a Deal ID problem: a typo copying the string between the SSP and the DSP, a deal that's active on one side but paused or expired on the other, or budget and flight-date mismatches between the two systems. None of these throw an obvious error. The deal simply returns zero bids or zero impressions, and it takes someone checking both platforms side by side to find the mismatch. If you're auditing what inventory a competitor or partner is actually buying at scale, OpenAdLibrary's ad intelligence index is a faster way to see what's live in market than trying to reverse-engineer it from deal reporting alone.

FAQ#

Is a Deal ID the same as a Private Marketplace?

No. The PMP is the deal type (an invite-only auction). The Deal ID is the identifier that routes a specific bid request to that deal's negotiated terms. A PMP deal, a preferred deal, and a programmatic guaranteed deal all use Deal IDs; they just apply different rules once the ID matches.

Who creates a Deal ID?

The publisher or its SSP creates and issues it, then shares it privately with the buyer, who enters it into their DSP's campaign or line-item settings.

Can more than one buyer use the same Deal ID?

Typically no. A Deal ID is issued to a specific buyer for a specific negotiated arrangement. Some SSPs support shared or multi-buyer deal setups, but that's the exception, not the default.

Why would a campaign with a valid Deal ID get zero impressions?

The most common causes are a mismatched ID string between platforms, a deal that's paused or expired on one side, or a budget or flight-date conflict. Check both the SSP and DSP configuration side by side rather than assuming the targeting itself is wrong.