Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

OpenRTB Integration Process

This document includes the necessary information for supply partners 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.

...

  1. Open a ticket with our support team to confirm the following information:
    1. Global auction timeout limits, QPS 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. OpenRTB Specs
    2. FAQ - Integration Process

 

Warning

NOTE: Pre-requisite checks are only complete after the contract is signed and member ID is created. Prior to that, only point 1a. can be processed. However, until the contract is countersigned, we'd still love to kickoff the conversation in Customer Portal with your integration team so that you can get familiar with the customer case process and get your technical questions addressed right away!

 

Integration Steps

  • Engagement is expected to take 3-4 weeks.
  • The client must fully review the Pre-requisite Checklist (this document) - and gather all the information prior following the steps below.
  • The client confirms with our support team the completion of the checklist. This is accomplished prior to the integration steps below.

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

  • Provision the objects that you will need for initial testing, either via the Console UI or Console API. See API Documentation for more details. 
  • Please use the code field to map your bid requests to your publishers and placements. For more details and examples read here and here.
Note

*NOTE: 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. 

...

Code Block
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
Warning

Do not leave &test=1 in your production traffic, we will not log those impressions on our platform. &test=1 is intended to safely test OpenRTB protocol format issues. Make sure to remove &test=1 as soon as you start sending test inventory to AppNexus.

Note

*NOTE: MEMBER_ID and MEMBER_ALIAS should be substituted with your individual partner member ID and alias. 

...