Get Setup to Bid
This section provides information required by bidders to configure and conduct bidding following the API integration.
As always, the ONE by AOL: Mobile Demand Services staff is available to provide assistance.
Configuration & Traffic Control Settings
There are a number of settings available to bidders to influence various aspects of RTB functionality as presented in the following table. Users can adjust these setting in the UI. An API will be established in the future.
|Bid Request URL||Base URL for receiving bid requests.|
|Win Notice URL||Win notice URL used by default if not specified in bid response.|
|Bid Units||Bid pricing units if not specified in bid response, default to $CPM.|
|Rate Limit||Maximum bid requests per second (0 suspends); default is unlimited.|
|Auction Types||Auction types allowed – 1st Price, 2nd Price Plus, or Both (default).|
|Country List||List of countries on which to filter; default is null.|
|Country Filter Type||Specify whether the country list is a block list or a white list.|
|Category List||List of site content categories on which to filter; default is null.|
|Category Filter Type||Specify whether the content category list is a block list or a white list.|
|Location Filter||Block bid requests that do not have location information.|
|Device ID Filter||Block bid requests that do not have device ID.|
The first three settings listed above are generally referred to as configuration settings. The configuration settings are established prior to enabling RTB traffic and tend to be rarely adjusted thereafter. The remaining traffic control settings allow bidders to filter the bid requests sent to them from the Marketplace. Traffic can be filtered by auction type, country of origin, and/or content category of the site. Traffic meeting these filter criteria can also be rate limited to a maximum number of bid requests per second.
Rate limiting is approximate.
Maximum Auction Time
For the protection of our publishers and their users against excessive latency, the ONE by AOL: Mobile Marketplace enforces a time limit on each auction. The timing begins when each bid request is issued. Any bid responses not received within the allotted time window will be flagged as a timeout and not eligible to participate in the auction. Frequent bidder timeouts can have a negative effect on overall Marketplace performance and therefore must not be used by bidders as an intentional means of communicating no-bids.
Currently, the auction time limit is 200ms, but this is subject to change.
ONE by AOL: Mobile reserves the right to disable bidders with unusually high levels of timeouts.
HTTP connection management is a substantial factor in participating in an RTB Auction. One of the simplest and most effective ways of improving connection performance is to enable HTTP Persistent Connections, also known as HTTP Keep-Alive. This has a profound impact on overall performance by reducing connection management overhead as well as CPU utilization for both bidders and the Marketplace.
ONE by AOL: Mobile reserves the right to disable bidders not using HTTP Keep-Alive.