h2. Integration Process Overview

Once you've discussed and clarified your integration goals with AppNexus, you start onboarding and building your integration:
# AppNexus grants you access to this Supply Partner Integration wiki.
# You read through the entire wiki and discuss any open questions or issues with your AppNexus account representative.
# AppNexus creates a test member for you in the AppNexus Console sandbox environment, as well as login credentials for that particular UI.
# AppNexus creates a default publisher and tag and associates them to your member. {color:#ff0000}I believe the client should{color} {color:#ff0000}{_}create{_}{color} {color:#ff0000}this publisher, then we'll go ahead and will associate that tag as their default. {color}
# You synchronize your inventory structure (publishers, ad quality profiles, tags,  etc.) in the sandbox environment, either via the API or UI. If you wish to accomplish this via the API, please refer to our [API onboarding process|api:API Onboarding Process].
{info}\- It is important to synchronize on a regular basis, ideally automatically, for all publishers that meet a certain impression minimum. Synchronization allows you to 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.{info}
# You build your integration to send bid requests and receive bid responses according to AppNexus' technical specifications (see Bid Request and Bid Response).
# You start testing against the sandbox environment, sending bid requests, receiving bid responses, and analyzing data to confirming that your system and AppNexus are synchronized. AppNexus confirms that your integration is correct and successful.
# AppNexus creates a member for you in the AppNexus Console production environment as well as login credentials for the UI and API.
# You push your synchronization (from step 4) to the production environment and provide AppNexus with your ad call timeout limits.
# You begin low volume testing in the production environment. Testing should include error analysis, call validation, cookie match rates, discrapency analysis, timeouts.
# You work with AppNexus on increasing your volume.

\***User sync/matching - where should this go? Done in preparation fro prod.

, 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.

# 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.