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 4 Next »

Integration Process Overview

Once you've discussed and clarified your integration goals with AppNexus, you start the process of onboarding and building your integration:

  1. AppNexus grants you access to this Supply Partner Integration wiki.
  2. You read through the entire wiki and discuss any open questions or issues with your AppNexus account representative.
  3. AppNexus creates a member for you in our AppNexus Console sandbox environment as well as login credentials for the UI and API.
  4. You synchronize your inventory structure (publishers, ad profiles, tags, etc.) in the AppNexus Console. It's best to synch programmatically via the API, but you can also do this manually in the UI.
    //

    This synchronization ensures that you can analyze discrepancies between AppNexus and your system, investigate publisher or domain performance, and enforce ad quality and publisher blocking preferences to ensure that AppNexus provides acceptable bids.

  5.  
  1. You build your integration to send bid requests, receive bid responses, and send notify requests according to AppNexus' technical specifications (see Bid Request, Bid Response, and Notify Request).
  2. AppNexus creates a member for you in our AppNexus Console sandbox environment as well as login credentials for the UI and API.
  3. You set up your inventory structure (publishers, ad profiles, tags, etc.) in the AppNexus Console, either via the UI or the API. This synchronization ensures that you can analyze discrepancies between AppNexus and your system, investigate publisher or domain performance, and enforce ad quality and publisher blocking preferences to ensure that AppNexus provides acceptable bids.
  4. You set up your
Unknown macro: {show-to}

, where you . This allows those building bidders to learn and experiment with the API and request/response protocols with no risk to their operations. If you don't have access to the sandbox environment, please contact your AppNexus account representative.

1.Onboarding, IC creates member, login credentials, grants API access, wiki access, (in sand)

2. Based on member ID, can have end point to test agains.

Build default publisher, default tag, associate default tag to member. Any request, gets that default tag and can be auctioned off. Can test at this point.

2.

  1. can analyze discrepancies in publisher impressions and spend between AppNexus and your system, investigate between the impressions and spend that AppNexus recorded for a publisher and compare a publisher's impressions and spend in the AppNexus system with that publisher's data in your system. impressions and spend that AppNexus has recorded for a particular publisher AppNexus has associated to analyze discrepancies This synchronization set up a default publisher and default tag for your member.
  • No labels