Page tree

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 38 Next »

Integration Process

Once you've discussed your integration goals with AppNexus, you start onboarding and building your integration. The process is generally as follows:

  1. AppNexus grants you access to this Supply Partner Integration wiki.
  2. You read through the entire wiki and discuss any open questions with your AppNexus Account Representative.
  3. AppNexus creates a test member for you in the AppNexus Console sandbox environment, as well as login credentials for the sandbox UI and API.
  4. You provide AppNexus with your auction timeout limit as well as the IPs & geographies of your datacenters. Your AppNexus account representative sets your auction timeout limit within the AppNexus system accordingly.
  5. You start placing user sync pixels on your pages to map your user IDs to AppNexus user IDs.
  6. You build your integration to send bid requests and receive bid responses according to AppNexus' technical specifications.
  7. You provision the inventory objects that you will need for initial sand testing in the sandbox environment, either via the UI or API. For self-guided API training and certification, get started here.
  8. You start testing against the sandbox environment, sending bid requests, receiving valid bid responses, and analyzing data to confirm that all parameter values are being correctly passed. AppNexus confirms that your integration is correct and successful.
  9. AppNexus creates a member for you in the AppNexus Console production environment, as well as login credentials for the production UI.
  10. You have a conversation with your AppNexus account representative to determine how best to synchronize your inventory structure. Per this conversation, you synchronize your inventory within the production environment.
  11. You begin low volume testing in the production environment. Testing should include error analysis, call validation, cookie match rates, discrepancy analysis, and timeouts.
  12. You work with AppNexus on increasing your volume.
  • No labels