BidsCube Real-Time Bidding Specification

Overview

Bidscube provides a real-time bidding platform that allows buyers to make real-time buying decisions while sourcing ad inventory. Interface of this platform is implemented as per the IAB’s OpenRTB Specification Version 2.4 and uses JSON (Content-Type: application/JSON; charset=UTF-8) as its message format.

Data format

By default, JSON (JavaScript Object Notation) supported for bid request and bid response data payloads. We can support other data format for specific integrations. Default header: Content-Type: application/JSON header.

Open RTB Version HTTP Header

By default we support Open RTB 2.4, but we can support 2.3, 2.0, 1.0 versions for specific integrations. Default header: x-openrtb-version: 2.4

RTB implementation details

DSP’s Open RTB features must correspond to the following requirements: first or second price auction (at=1 or 2). For Display, Mobile and Native: win notification must be configured using ad markup instead of nurl. For video: win notification must be configured using nurl and impressions count using VAST field “Impression”.

We run screening against bcat, so that filtering by bcat on DSP’s side is essential.

Transport

By default, all calls should return HTTP code 200 with body containing bid response in JSON format. For “no bid” response, the call should return HTTP code 204 with empty body.
However, for specific integrations we can support other options like HTTP code 200 with empty body, or with body containing “nobid” message.

Accordance with IAB Specifications and Guidelines

We work in accordance with IAB Specifications available here.

Bid Request

Bidscube sends a Bid Request when an image becomes visible within the browser.

Latest version of detailed bid request specification including attributes, types and description is available here. Page 1.

Bid Response

Bidscube expects to receive a Bid Response for each BidRequest. The following table describes the fields and objects in the BidResponse message. All calls should return HTTP code 200 except for an empty bid response (no bids) which should return HTTP code 204.

Latest version of detailed bid response specification including attributes, types and description is available here. Page 2.

User Syncing

Bidscube can present the DSP’s user identity in each bid request. User profile syncing is accomplished via a “cookie swap”. The steps are as follows:

DSP gives Bidscube a user sync pixel URL that Bidscube will fire whenever it encounters an unmapped user:

http://example.dsp.com/usersync?partner_id=Bidscube &i=[SSP_USER_ID]

Bidscube gives SSP a user sync pixel URL that SSP will fire whenever it encounters an unmapped user:

US — http://n1.Bidscube .com/?t=match&ssp_id=[ssp_id]&ssp_user_id=[ssp_user _id]

EU — http://n2.Bidscube .com/?t=match&ssp_id=[ssp_id]&ssp_user_id=[ssp_user _id]

Bidscube then associates its own user ID with the DSP user ID so it can include it in each bid request.

Pixel Redirection

Bidscube can optionally redirect the user sync request to a different pixel if the DSP supplies a
redirect URL parameter as follows:

US — http://n1.Bidscube .com/?t=matchr&dsp_id=[DSP_ID]
EU — http://n2.Bidscube .com/?t=matchr&dsp_id=[DSP_ID]

Note: All request parameters should be properly URL encoded. Also, secure URLs (https) are supported for user sync calls.

In-App Banner Bid Request Example

Native Bid Request Example

Banner Bid Response Example

Native Bid Response Example