April 19, 2018
App Bundle ID targeting
As part of a larger company effort to streamline traffic-shaping capabilities, OpenX now supports App Bundle ID targeting via a whitelistMarking a particular entity as “approved” in order to ensure it is included. A whitelist will block new entities by default whereas a blacklist will allow new entities by default. For example, you could use a whitelist to only allow the "Technology" industry./blacklistBlocking a particular entity's access to your inventory from the Ad Exchange. A blacklist will allow new entities by default whereas a whitelist will block new entities by default. feature within AXB Line ItemThe primary unit of execution for an order, which represents a specific inventory purchase and the required conditions for ad delivery. settings. This feature allows you to specify individual mobile apps (by bundle id) that you want to receive for more optimized traffic flow and quality from OpenX. Contact your Platform Development Manager with any questions.
October 26, 2017
Mobile OS targeting
Targeting options now include the latest Android (8.0) and iOS (11) operating systems.
October 5, 2017
Single Sign-On (SSO) available in German
The OpenX SSO interface now supports German.
August 23, 2017
OpenRTB 2.5 Metric object
OpenX now supports the Metric object from the IAB's OpenRTB 2.5 specification, which provides an array of Metric objects that offer insight into different metrics about the 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. to assist with 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. decisioning (such as viewabilityOpenX uses the Media Ratings Council (MRC) definition unless otherwise noted. According to the MRC, display ads are considered viewable if 50% of their pixels are in view for a minimum of one second, two seconds for video. This applies to both desktop and mobile environments. However, in some situations, you may be able to set your own definition.). Each metric is identified by its type, reports the value of the metric, and optionally identifies the source or vendor measuring the value.
To enable this object or receive more information, please contact your Platform Development Manager.
Note: OpenX will no longer support our legacy viewability extensions after December 31, 2017. We recommend that our demand partners update their integrations to support the Metric object prior to this date to avoid any interruption in service.
July 14, 2017
Source object support
OpenX now supports the Source object from the IAB's OpenRTB 2.5 specification, which describes the nature and behavior of the entity that is the source of the 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. upstream from the OpenX Ad Exchange. The primary purpose of this object is to define post-auction or upstream decisioning when the exchange itself does not control the final decision. A common example of this is header biddingA monetization tool that exposes each impression to programmatic demand before calling the ad server. This lets publishers realize the true value of their direct and indirect inventory in real time..
To enable this object or receive more information, please contact your Business Development Manager.
April 20, 2017
Signal for guaranteed deals in real-time guaranteed (RTG) requests
DSPs using real-time guaranteed (RTGReal-time guaranteed, a programmatic direct deal type that allows a buyer and a publisher to commit to a flexible guarantee for the purchase of inventory and a buyer-defined audience.) and receiving requests for RTG/guaranteed deals can now identify such traffic via a new extension field of the Deal object in bid requests.
Deactivated legacy reporting user interface
The legacy reporting interface has been deactivated. You may continue to access the expanded data and features in the My Reports reporting interface without interruption. However, you will no longer be able to toggle to the legacy reporting UI.
As part of this change, the Dashboard has been replaced with a Home page that provides performance data.
If you are still using the legacy reporting UI, please switch to the My Reports UI instead, and make use of the pre-configured reports that are equivalent to popular legacy reports.
Please note that this deactivation will not impact the existing Reporting API, and any reporting calls will continue to be supported without interruption, or the need for updates.
March 23, 2017
Targeting based on device ID and ad tracking
You can now target inventory based on whether there is a device ID and ad tracking is enabled or disabled.
March 9, 2017
Targeting based on API frameworks
The API Frameworks field has been added to the targeting module in 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.” line items. It enables you to target and filter requests based on API framework.
February 10, 2017
Targeting based on location source
The Location Source field has been added to the targeting module on the line item form. It enables you to target and filter requests based on location source, such as GPS Detected, IP Derived, and User Info.
See Past releases for updates earlier than 2017.