Integration Process

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.

Pre-requisite Checklist

The checklist below applies to all external supply partners aiming to integrate with AppNexus via OpenRTB protocol. Note: It is mandatory to use the Customer Support Portal for communication to complete each step of the integration process.

  1. Open a ticket with our support team to confirm the following information:
    1. Global auction timeout limits and data center IPs closest to the AppNexus datacenter regions: US-east, US-west, EMEA and APAC.
    2. Member seat ID and if not requested yet, new member seat creation and API login credentials for AppNexus Console API.
    3. Endpoints for incoming bid requests, and if not requested yet, new endpoint creation on AppNexus.
    4. Usersync pixel in order to map your user IDs to AppNexus user IDs, and if not requested yet, new usersync pixel activation.
  2. Review the documentation outlined below and discuss any open questions with our support team:
    1. Review the OpenRTB Specs.
    2. Review the FAQ - Integration Process.

Integration Steps

Step 1: Self-guided API/UI training and creation of objects (Estimated time: 7-10 days)

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. 

The code field is required for all external sellers at both the publisher and placement levels and is highly recommended for all other sellers to ensure that your inventory is as granular as possible so that it can be investigated accurately for quality issues, and specifically for domain detectability. This step will help you to split your inventory into highly detectable and less detectable tags, allowing you to isolate the impacts of non-detectable domains on the rest of your inventory's viability.

Step 2: OpenRTB bid request endpoint testing (Estimated time: 7-10 days) 

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. 

Step 3: Discrepancy checks and OpenRTB requirement validation 100QPS (Estimated time: 7-10 days)

Final OpenRTB requirement validation 100%

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.