Last updated January 16, 2019

OpenX supports real-time bidding via the IAB's OpenRTB 2.5 specification.

You can use the OpenRTB structure and its enumerated values to write applications that bid on ad space in OpenX Ad Exchange and other compatible exchanges and supply sources. Bidders that are already compatible with these versions should be able start using the OpenX OpenRTB implementation with minimal custom integration work.

When participating ad inventoryAd space available on a website or app. The basic unit of inventory for OpenX is an ad unit. becomes available, OpenX sends JSON data in an OpenRTB BidRequest to describe the ad inventory, the user, and other details. Demand Partners can send an OpenRTB BidResponse in JSON format and set up optional win notifications and loss notifications.

OpenX provides its publishers with an OpenRTB ad call parameter to send additional data to buyers in each BidRequest. For details, see supplemental data enrichment.

The diagram below provides a graphical overview of the process described above:

How real-time bidding works

Real-time bidding (RTBReal-time bidding, auctioning online inventory within an ad exchange. Buyers bid for the impression based on the value of the user, whereas the seller sets pricing floors and awards the impression to the highest bidder. The auction process takes place in milliseconds, which is why the process is referred to as “real-time.”) in OpenX Ad Exchange is a server-to-server interaction between the OpenX ad serving infrastructure and bidders.

OpenX Ad Exchange communicates with bidders using the OpenRTB (JSON) Real-Time Bidding API. OpenX supports the IAB's OpenRTB 2.5 specification.

Here's how the RTB process works:

  1. Real-time bidder selection. OpenX Ad Exchange receives an ad requestCommunication from a web browser or app to an ad server to display an ad. for an available impressionA single display of an ad on a web page, mobile app, or other delivery medium. For deals, impression is a metric to relay the total number of ads that have served. See also billable impression, forecasted impressions. and selects a set of DSPs from whom to solicit bids based on individual DSPDemand-side platform, a platform or provider that allows advertisers to manage multiple ad exchange and data exchange accounts through one interface, often in real time. inventory targeting settings and their QPSQueries per second, a measurement of bid request traffic volume. Higher QPS corresponds to more bid requests. Demand Partners can set QPS limits for RTB endpoints and traffic sets, depending on endpoint server capacity and how much traffic they want to receive. allocations.

  2. Bid requestWhen OpenX Ad Exchange receives an ad request, it sends a communication containing details about the impression to selected real-time bidders to solicit bids for it. from OpenX Ad Exchange. OpenX Ad Exchange passes a bid request with details about the specific impression to the selected real-time bidders and solicits bids for it. The bid request may contain optional targeting information. If a single bidder has multiple matching traffic sets, OpenX Ad Exchange includes all of the matching traffic sets in the bid request.

  3. Bid responseAfter evaluating a bid request, a real-time bidder’s communication to OpenX Ad Exchange, indicating if they’re interested in the impression, and if so, how much they’re willing to pay for it.. Each bidder receives the request, evaluates the bidding opportunity, and responds with a bid response (even if the bidder does not want to place a bid).

    Important: The response contains either a CPMCost per mille, a pricing method which calculates cost based on the number of impressions (per 1000). bid or a "no bid" response. Bidders must respond to bid requests because timeouts have a negative impact on the number of bid requests sent to the bidder.

    Bidders with multiple matching traffic sets must provide a CPM bid or a "no bid" response for one of the matching placements so that OpenX Ad Exchange can attribute the impression to the appropriate business unitA logical grouping of traffic sets in a Demand Partner's account., traffic setA grouping of properties that controls the kind of traffic a Demand Partner wants to bid on and how they want to receive that traffic. Properties include buying models, spend cap, targeting criteria, maximum QPS, and routing endpoints., and ad. Bidders can include multiple bids in their bid response for a single matching ad.

  4. Auction. After OpenX Ad Exchange receives bids (or after an allotted amount of time), it executes an auction. Publishers can set a floorThe minimum price a publisher is willing to accept for a given impression. price for their inventory. In those cases, any winning bid must be higher than the publisherAn account type that represents a business with ad space to sell.'s floor price.

  5. Ad delivery. OpenX Ad Exchange delivers the ad of the winning bidder. The BidResponse contains the HTML for the ad the bidder wants to serve. When the bidder wins the auction, the viewer's browser or app loads this HTML.

    Important: Macros for tracking clicks must be included in the HTML. Additional macrosFor OpenX, a command enclosed in curly braces {} that dynamically inserts attributes into your HTML or third-party ad creatives and click-through URLs when OpenX serves an ad. Other macros, like from your video player, may have alternate formatting., like price macros, can also be included.

  6. Result notifications. OpenX Ad Exchange sends result notifications, in the form of an auction results message, for each bid it received for a given auction.

OpenX supports real-time bidding via the IAB's OpenRTB 2.5 specification.

Fill out my online form.