This document includes the necessary information to review, plan, and execute a new OpenRTB integration - or migrate from a custom SSP protocol integration to OpenRTB standard, in a self-paced fashion.
Note: It is mandatory to use the Customer Support Portal for communication to complete each step of the integration process. If you do not already have a portal account, please visit the Login page, proceed as a Guest, and request a new user registration.
In order to provide transparency to our buyers and improve our optimization, we require our partners to break out their inventory by publisher. For more information regarding our inventory structure standards please visit our wiki page Use the Console API to Synchronize Your Inventory Structure.
In order to create or edit publishers in the Console UI or Console API, you have to declare the Inventory Relationship. The requested information is basic business information about how the inventory is accessed and will be used to support AppNexus inventory quality efforts. For a complete list of fields and their usage requirements, please refer to the Publisher Service documentation on the AppNexus wiki.
Use the endpoints below to send server-to-server OpenRTB bid requests to AppNexus:
http://MEMBER_ALIAS-useast.adnxs.com/openrtb2?member_id=MEMBER_ID&test=1 http://MEMBER_ALIAS-uswest.adnxs.com/openrtb2?member_id=MEMBER_ID&test=1 http://MEMBER_ALIAS-emea.adnxs.com/openrtb2?member_id=MEMBER_ID&test=1 http://MEMBER_ALIAS-apac.adnxs.com/openrtb2?member_id=MEMBER_ID&test=1
*NOTE: MEMBER_ID and MEMBER_ALIAS should be replaced with your individual partner member ID and alias - provided by AppNexus contact.
We encourage a gradual traffic ramp-up where distinct portions of your inventory are being sent to AppNexus. General recommendation is to start with a small chunk of traffic (100-200 QPS).
AppNexus will run a delivery test from a dedicated buy-side member seat and notify you of any discrepancies before scaling your inventory further.
AppNexus will validate your OpenRTB bid requests and notify you in case the format needs to be corrected.
Notify your AppNexus contact about the completion of the self-paced integration/migration, who will initiate the final OpenRTB requirement validation tests - and provide you with final results and feedback.