How a real-time bidding auction actually works today

If you run an exchange, the auction is your product. Partners may never see your admin screens, but they feel every decision you make about timeouts, floors and notices. Here is how a programmatic auction works now, and what an exchange operator controls along the way.

The flow, end to end

A user opens a page or an app. The publisher's ad stack builds a bid request describing the impression: the placement and format, the site or app, the device, what may be used about the user under consent rules, and commercial rules such as the price floor. Your exchange receives that request from a supply partner, decides which demand partners should see it, sends it to them server-to-server, collects bids, picks a winner and returns it. Money moves later, based on notifications.

The request carries a time limit, tmax in OpenRTB, in milliseconds. Bids that arrive after it are useless, however high they are.

First price, second price

OpenRTB states the auction type in the at field: 1 for first price, 2 for "second price plus". Values of 500 and above are left for exchange-specific types.

In a second-price auction the winner pays roughly the second-highest bid plus a small increment, or the floor if that is higher. In a first-price auction the winner pays what it bid. Most of open programmatic moved to first price around 2019; Google announced a unified first-price auction for Ad Manager that year and much of the market followed.

The reason was simple. With header bidding, an impression often went through several auctions in a row, each with its own rules, and second-price logic stacked on second-price logic produced prices nobody could explain. First price is blunter: the bid is the price.

For an operator: know which auction type you run on each connection, set at correctly, and make sure your partners agree. A DSP that thinks it is in a second-price auction while you charge first price will notice.

Bid shading, and why bid levels move

In a first-price auction, bidding full value is expensive, so DSPs shade: their algorithms estimate the lowest price likely to win and bid near it. Shade too little and they overpay; shade too much and they lose impressions they wanted.

For an exchange this has two consequences. First, the bids you see are already discounted, so a floor that once looked sensible may now block a lot of demand. Second, shading models learn from what your exchange reports back. Clear, consistent win and loss information helps buyers bid with confidence on your supply.

Floors

Floors travel in each impression of the request (bidfloor and bidfloorcur). Bids below them are discarded. In first price a floor is only a minimum; it no longer sets the price for a lone bidder.

Set floors per supply partner, format and geo, based on the clearing prices in your statistics, and review them on a schedule. Floors nobody revisits lose revenue quietly in both directions: too high, and demand walks away; too low, and supply partners complain about prices.

Timeouts

Your exchange sits between a supply partner with its own deadline and demand partners with their own latency. Wait too long and the supply side gives up on you; cut too early and you drop bids you could have sold. Watch timeouts per demand partner. A partner that is always late is not really demand, it is cost.

Win, loss and billing notices

Winning is not the same as owing money. OpenRTB defines URLs a bid can carry:

  • nurl, the win notice, called when the bid wins;
  • burl, the billing notice, called when the impression becomes billable, usually tied to the ad rendering;
  • lurl, the loss notice, called when the bid loses, often with a reason code.

Prices are passed through macros. ${AUCTION_PRICE} carries the clearing price. Some exchanges also pass a "minimum bid to win" value, but its name and meaning differ between exchanges, so document what yours sends and read each partner's spec rather than assuming.

Most financial disputes between exchanges and partners come down to counting at different points: won versus rendered versus billable. Agree in advance which event you bill on, and make sure your statistics show it.

Deals

Private marketplace deals use the same pipes. The request carries deal IDs, prices and eligible buyers. A deal may win at a fixed price or compete with a deal floor. If deals pass through your exchange, make sure the deal information reaches the right partners untouched.

The operator's short list

  • Know and declare the auction type on every connection.
  • Base floors on observed clearing prices, per partner, format and geo.
  • Track timeouts and cut partners who are always late.
  • Document your notices and macros, and agree the billing event with every partner.
  • Keep supply paths clean so buyers are not shading against noise.

The auction is not complicated. It just has many small rules, and money leaks wherever someone assumes instead of checking.

Want to talk about your own setup? Get in touch with the Xendiz team.