AppNexus Bidder Release Notes
The following table lists AppNexus product releases, updates, and deprecations. Dates may shift if necessary.
|Release Date||Status||Feature||Product Theme||More Info|
Support IFA Fields for CTV Impressions in OpenRTB Bid Requests
AppNexus is releasing an update to our handling of CTV impressions to align to new IAB Identifier for Advertising (IFA) OTT guidelines.
This update supports the implementation of additional IFA fields for CTV impressions. In accordance with the IAB guidelines, AppNexus will now be supporting the following fields on CTV impressions when available:
If necessary, we recommend that you update your bidder to ingest and decision on these fields.
Deprecate AppNexus Bidding Protocol and Legacy OpenRTB
AppNexus will no longer support the AppNexus Bidding Protocol and Legacy OpenRTB Protocol on December 1st, 2018. All bidders will be expected to migrate to OpenRTB 2.4.
Deprecate Bid Shading and Spend Protection Fields in OpenRTB Bid Requests
We are deprecating the following fields from our OpenRTB Bid Request Protocol:
Though we are removing bid shading fields from the request, AppNexus still offers a bid shading product. You can see more information about how to enable it here.
Native Ad Markup Bidding (Beta)
AppNexus now supports Native Ad Markup Bidding, which enables your bidder to submit native ad markup via
Your bidder must be enabled to use this feature. Please contact your AppNexus account representative if you would like to be enabled.
|Native, Creative, OpenRTB|
Support Video Placement Field in OpenRTB Bid Requests
All video bid requests will now contain the OpenRTB 2.5 video.placement field in the request.
The following values are supported:
This field can be used for additional video bidding logic by external partners.
New AdX Bid Errors
We are introducing three new bid errors in the Bidder Bid Error Report and Notify Request related to bidding on Google AdX inventory. The errors are:
Bid rejections for these errors were previously categorized under bid errors 117 and 122. Information on how to handle these errors is available in Bid Error Codes.
Expired Creative Inactivity Period Decreased
The inactivity period before a creative is expired will be decreased from 45 days to 15 days. Currently, when a creative (1) has not run and (2) has not been modified for 45 consecutive days, it is expired. When this happens, the
If your bidder resumes bidding with an expired creative, the creative will soon be unexpired due to automated Creative Unexpiration released in March 2018.
AppNexus will now automatically unexpire and reactivate your expired creatives if your bidder bids with them. This release will substantially reduce bid errors 102 and 307 generated by your bidder, and you are no longer required to manually unexpire your creatives. Automatically unexpired creatives will not be resubmitted for creative audit; instead they will maintain the audit status set in the most recent audit.
Supply Type Detection
AppNexus will begin releasing changes to how the supply type field is set on inventory. No action is required from bidders.
Currently, supply type is a field that sellers set on placement groups to identify impressions as “web,” “mobile web,” or “app,” and bidders can choose to target supply type in bidder profiles. To reduce errors from sellers misclassifying or leaving the default, AppNexus will now detect and set supply type implicitly on every impression. As a result, bidders will be able to more accurately target the inventory they want, and sellers will have one less operational task in managing their inventory. Bidders specifically targeting mobile web may also see a bump in QPS as this is a commonly misclassified supply type.
WiFi Carrier Renamed
The "WIFI" carrier (id 1) will be renamed "Unknown". The Carrier service and
Split Bid Error 102 into Two Errors
We are splitting bid error code 102 "Creative id was not found or inactive" into two errors. The new errors are:
|Creative, Reporting, Troubleshooting|
API Version 1.18 Release - Breaking Change
We are pleased to announce the release of version 1.18 of the AppNexus Imp Bus API.
The following services will be changed:
The syntax of the following services have been changed:
Update Bcat Behavior to Include Brand Override
Update device.os Field in OpenRTB
Support ipv6 in OpenRTB Bid Request to Bidders
OpenRTB bid requests will contain device.ipv6 when provided by supply.
Support Privacy Link in OpenRTB Native
Change in Bcat and Battr Behavior
Remove AppNexus Categories from OpenRTB Bid Requests
Change in Click URL Behavior
New Quick Start Buying Guide
Support Multiple Media Types in a Single Bid Request from AST Supply
Banner Sizes Extension Deprecated
We have deprecated the imp.banner.ext.appnexus.sizes field from bid requests. Please use the imp.banner.format field instead.
Native 1.0 Bid Requests Deprecated
We have deprecated support for Native 1.0 bid requests. We now support Native 1.1.