|Starting March 31, 2021, docs.xandr.com is the place to be!|
For more information, see Building a Better Customer Experience.
How It All Works
An Ad Call Is Received By the Impression Bus
At the ad call, the Impression Bus receives the AppNexus user ID and fundamental page information from the AppNexus TinyTag or PriceCheck tag and the user's AppNexus cookie. Either AppNexus tag is how a partner will manage all campaigns with ease and how AppNexus will be able to create a universal way to identify inventory. And since TinyTag and PriceCheck tags are stored server-side, once in place, you will never have to re-tag a publisher page again.
In addition to TinyTag, the Impression Bus will send your Bidder a Pixel Request. Pixel Request creates a simple way to synchronize your user IDs and metadata with the AppNexus user IDs and data.
With TinyTag and the Pixel Request, the Impression Bus will send your Bidder the appropriate user and page information. Your Bidder will receive this information either from your preexisting campaign or from another bidder's preexisting campaign.
The Imp Bus Holds An Auction
When an ad call from one of the AppNexus tags hits the Impression Bus, we review the content and send a bid request to the various bidders on the AppNexus cloud. The bid request will include the content categorization, page information, user information, and in certain cases a reserve price and reserve creative.
Bidding on Impressions At Auction
Data providers integrated on our cloud recognize the user ID and can input any information they may have on that specific ID and will pass the user data to bidders that have the rights that information. The bidders then evaluate the ad call on behalf of their advertisers and return a bid value to the imp bus.
Serving the Impression
The impression is served in one of these ways:
Find Highest Bid and Serve Immediately: The AppNexus Imp Bus determines highest bidder and will serve the winning bidder's creative as dictated in the bidder response.
Highest Bid Wins if Beat Reserve Price: If a reserve price is passed via the AppNexus ad tag, the Imp Bus passes this price as well as the other ad call information to all bidders. Bidders respond with a bid value and creative ID and the highest bid that beats the reserve price will serve it's creative. If no bid beats the reserve price, the Imp Bus will pass the ad call on to a 3rd party system.
Price Check - Send Highest Bid to 3rd Party: The ad call is directed to the AppNexus Imp Bus to get first glance in order to perform a price check. The Imp Bus holds an auction among its bidders and passes the highest bid onto another 3rd party's system to decide how to fill the ad call. Only if the highest bid in AppNexus is chosen as winner the ad call is passed back to AppNexus where the Imp Bus will serve the winning bidder's creative.
Auction Post Mortem
One of the main problems with working in a closed advertising ecosystems is that it is hard for bidders to understand why they won or lost an impression. If you bid $2.00 for a car-buyer on nytimes.com/autos and consistently lose, what action should you take? Are you being outbid by $0.05 or $5.00? If you are selling inventory, which user segments are driving your CPMs? This crucial information will be passed to your bidder via Notify Request.
Couple this with with full reporting and API support and you have all the tools you need to make informed and powerful decisions for your clients.
- Optimize delivery of ads by leveraging the cloud computing environment.
- Brand control and quality.
- Guaranteed range of CPMs for sellers.
- Independence platform allowing deep integration with technologies, optimization engines, and bidders.
- Increase the Number of High Value Users for Your Clients While Decreasing the Number of Low Value Users.