The Anatomy of the Bid Request

When a user loads a webpage or launches a mobile app, the publisher’s Supply-Side Platform (SSP) must instantly evaluate which advertiser is willing to pay the most for the resulting ad impression. To facilitate this, the SSP generates an OpenRTB bid request—a highly structured JSON payload broadcast to multiple demand-side platforms (DSPs). The DSPs then parse this payload, apply their targeting algorithms, and respond within milliseconds.

The bid request serves as the digital specification sheet for the impression. It contains details about the user, the device, the context of the page, and the specific ad slots available. Governed by the IAB Tech Lab, the protocol ensures that competing platforms speak a universal language, reducing integration friction across the ad tech ecosystem.

The Imp Object

At the core of every bid request is the imp (impression) array. This object defines a single ad placement opportunity. If a page features multiple ad slots, the SSP will include multiple imp objects in a single request, allowing buyers to evaluate the entire page context. The imp object contains a unique ID for the placement, the allowed media types, and crucially, the bidfloor—the minimum CPM the publisher is willing to accept.

Media Types: Banner and Video

Within each imp object, the SSP specifies the exact media formats allowed. The two most common are banner and video.

The banner object details the physical dimensions of the slot (e.g., 300x250 or 728x90), the position on the page (above or below the fold), and any specific formats allowed, such as HTML5 or AMP.

The video object is substantially more complex. It must communicate the required video protocols—typically VAST versions—the maximum and minimum video duration, the placement type (in-stream, out-stream, or accompanying banner), and whether the audio can be muted or initiated by the user. Accurate video specifications are critical, as serving a non-compliant VAST tag into an incompatible player will break the user experience and waste ad spend.

Deals and PMPs

While OpenRTB powers the open exchange, it also facilitates Private Marketplaces (PMPs) through the deal object. When a publisher and an advertiser have negotiated a pre-arranged agreement, the SSP includes a deal object within the imp array. This object contains a unique dealid and may feature a specialized bidfloor. DSPs recognize this ID and prioritize their bidding logic accordingly, often competing against open exchange demand but with a first-look or fixed-price advantage.

The Bid Response

Once a DSP receives the bid request, its predictive algorithms evaluate the user's historical data, the contextual relevance of the environment, and the creative specifications. If the DSP decides to buy the impression, it returns a bid response.

The response is significantly leaner than the request. It centers around the seatbid array. A "seat" represents a specific advertiser or agency on the DSP's platform. Inside the seatbid array is the bid object, which contains the impid (matching the request to ensure proper placement), the exact price the buyer is willing to pay, and the adm—the ad markup itself. For a display ad, adm contains the HTML or JavaScript tag; for video, it contains the VAST XML.

The Auction Mechanics

OpenRTB does not inherently dictate the auction logic; rather, it provides the data necessary for the SSP to run the auction. Historically, programmatic exchanges relied heavily on second-price auctions, where the winner paid $0.01 more than the second-highest bid. However, the widespread adoption of Header Bidding forced a paradigm shift.

Today, the vast majority of OpenRTB transactions are settled via first-price auctions. In a first-price model, the highest bidder pays exactly what they bid. OpenRTB accommodates this transition through specific signaling. Bidders can use the bid object's tmax (maximum time to respond) to manage latency, but more importantly, DSPs now employ sophisticated bid shading algorithms to avoid overpaying in first-price environments while still submitting competitive bids via the standard price field.

The SSP assumes the responsibility of comparing all returned bids, applying any internal publisher rules (like blocking certain creatives), selecting the winner, and firing the appropriate notification URL to inform the DSP of the outcome.

Practical Example: OpenRTB in Action

To understand the protocol's elegance, examining a simplified bid request and response is highly effective.

Consider an SSP sending a request for a 300x250 banner ad to a DSP:

{
  "id": "80ce30c53c16e6ede535",
  "imp": [
    {
      "id": "1",
      "banner": {
        "w": 300,
        "h": 250
      },
      "bidfloor": 0.50,
      "secure": 1
    }
  ],
  "device": {
    "ua": "Mozilla/5.0 (Windows NT 10.0)",
    "ip": "192.168.1.1"
  },
  "site": {
    "id": "1234",
    "domain": "adwireexample.com"
  }
}

In this payload, the SSP tells the DSP that it has one impression (id: 1), it's a 300x250 banner, the Floor Price is $0.50, and it must be served securely. The user is on a Windows machine, and the domain is adwireexample.com.

The DSP evaluates this and responds with a winning bid:

{
  "id": "80ce30c53c16e6ede535",
  "seatbid": [
    {
      "seat": "buyer-123",
      "bid": [
        {
          "id": "bid-001",
          "impid": "1",
          "price": 1.25,
          "adm": "<a href='...'><img src='...' /></a>"
        }
      ]
    }
  ]
}

The DSP bid $1.25 CPM for the impression and provided the HTML ad markup in the adm tag. Because $1.25 exceeds the $0.50 floor, the bid is valid. The SSP will run its auction against other DSP responses, and if this is the highest bid, the adm will be rendered on the page.

Key Takeaways

OpenRTB remains the vital infrastructure of the open web's advertising economy. Understanding its flow and objects is essential for any professional operating in programmatic media.

  • Standardized Communication: OpenRTB is an IAB-sanctioned JSON-based protocol that allows SSPs and DSPs to transact efficiently without bespoke integrations.
  • Imp Object Hierarchy: The imp object is the foundational unit of the bid request, containing media-specific requirements (banner, video) and floor pricing.
  • PMP Integration: The protocol seamlessly supports private marketplaces via the deal object, allowing for negotiated terms within the real-time auction framework.
  • Ad Markup Delivery: The bid response relies on the adm field to deliver the actual creative payload, whether it is HTML for display or VAST XML for video.
  • Auction Flexibility: OpenRTB transmits bid data, but the SSP governs the actual auction logic, with first-price auctions now the industry standard following the rise of header bidding.

As the industry pushes toward OpenRTB 3.0 and adapts to evolving privacy regulations, the core mechanics of the bid request and response cycle will remain the fundamental pulse of Programmatic Advertising.