Publishers RTB Overview
Find out about integration with Open RTB and ExoClick RTB here:
Bid Request/Response Structure:
Bid Request/Response Specifications are here:
Bid Request/Response Examples:
Bid Request/Response Examples are here:
The IP networks used by ExoClick RTB are detailed here:
Open RTB standards version 2.4 is supported, however, the ADM is different from the standards. If the client supports Open RTB, they need to ensure that they adapt their ADM to ours.
If the client supports XML, they need to provide ExoClick with their RTB specifications and they will need to adapt their system to ours.
There are two servers located in New York and the Netherlands. Normally, the requests of a certain geo will be sent from the nearest server, but not always. The system distributes the requests from one server to another depending on the workload of the server at any given moment. For this reason, if the client asks to only be sent requests from the US server, it is not possible to do this.
The 'tmax' (the maximum time in milliseconds that SSP allows for bids to be received to avoid timeout) is 300ms. This information is not passed at the request as its always the same.
Currency is not passed either at the requests with RTB Floor CPM 0, as the currency is set up at the account level. If the advertiser requests the currency to be passed at the request, a very low RTB Floor CPM should be set.
The total amount of requests will depend on the format, geo, categories selected and 'RTB Manual Throttle' set up. Publishers will have an RTB Automatic throttle switch on the zone level to reduce queries and thus server cost. This is mostly be enabled on zones which are not generating revenue in certain geos. In this case, the automatic throttle will temporarily reduce the requests to 1%. When the Revenue raises and zone starts generating profit again on those Geo, the throttle will be automatically increased.