Skip to end of metadata
Go to start of metadata

Bidders in Pictures

Buying through AppNexus

A bidder is a "decisioning brain" that calculates auction bids using an algorithm and some parameters, such as user data, recency, location, etc. Many of our clients use our hosted full-featured bidding system, the AppNexus Console, which has built-in optimization and ad serving capabilities. Clients with existing in-house ad servers and sophisticated proprietary optimization logic may wish to build their own bidder. If you build your own bidder, you will host it on your own AppNexus server or on another server in close proximity to our datacenters, and it will be owned and maintained by you. 

Selling Through AppNexus



  
1)     TinyTags.  A TinyTag is an AppNexus tag placed on a publisher's page. At the ad call, the AppNexus Impression Bus looks up all information associated with the tag, such as a minimum acceptable reserve price and a reserve creative. The Impression Bus sends bidders the appropriate user and webpage information and asks for their bids in 1/20th of a second.  If the reserve price is beaten, the highest bidder will win the impression.  If no bidder meets the reserve price, and a reserve creative was specified, the reserve creative will be served.  


  

2)     Preemptive Tags.  The exact steps for PriceCheck will depend on the type of tag a publisher has on a page. In general, the ad call will be routed first to the AppNexus Impression Bus, which will hold an auction based on the user and page information as described above.  Bids are returned to the AppNexus Impression Bus which then passes the highest bid to your adserver. The adserver can then decide how best to fill the impression; most commonly there will be another auction that includes the AppNexus bid.  If AppNexus wins the impression, the ad call returns to our Impression Bus and the winning bidder serves the ad.

 
 
  • No labels