The client-side logic is based on a driver implementation, so that on decision points custom actions can be provided. Read your logic is easily implemented.
Allows multiple auctions to run simultaneously. This allows to create complex client side logic. (For example: create a tier based setup, or create pricing rules for banners which have an alternative size: let’s say on a 728×90 placement a billboard is served. That the billboard should have at least a10% uplift above the average 728×90 price.) And the possibility to create complex webpages as infinite scrolling pages or SPA’s. As the bidding process becomes independent of the rendering and decision process.
Easy integration with the defined placements for the ad server via TAGMAN.
Collection of statistics of the returned bids.
Client and ad server side decision options. (For example the client could decide the received bid is valuable enough to directly render it. By-passing the ad server. Or the ad server might decide to render the ad of a certain bidder, even if it has not provided the highest bid but you want to push a certain amount of volume to a certain source regardless.)
ADBid™ runs in its own container, this allows for memory management to recycle an often used instance, or will be able to recover if a library won’t load at all.
With ADBid™ the total inventory can be exposed to the exchanges, in essence giving them the same first view the ad server has. This allows for parallel decision making instead of a waterfall based.