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.
This checklist applies to all external supply partners, (existing as well as new), who aim to integrate via OpenRTB.
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.
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 is being sent to AppNexus. It is best to start with a small chunk of traffic (around 10%), and go from there.
AppNexus will verify your bid requests automatically 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.