13
1 | Page Real-Time Bidding Specification & Integration Kit Version 1.0 Overview CRONBID programmatic channel provides a real-time bidding DSP 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.5 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. 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: https://www.iab.com/wp- content/uploads/2016/01/OpenRTB-API-Specification-Version-2-4-DRAFT.pdf This page aims to help our Publishers/Supply Partners to get integrated via our RTB Demand Side Platform and Real-Time Bidding Specification.

Real-Time Bidding Specification & Integration Kit Version 1

  • Upload
    others

  • View
    2

  • Download
    0

Embed Size (px)

Citation preview

1 | P a g e

Real-Time Bidding Specification & Integration Kit

Version 1.0

Overview

CRONBID programmatic channel provides a real-time bidding DSP 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.5 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.

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: https://www.iab.com/wp-

content/uploads/2016/01/OpenRTB-API-Specification-Version-2-4-DRAFT.pdf

This page aims to help our Publishers/Supply Partners to get integrated via our RTB Demand Side Platform and

Real-Time Bidding Specification.

2 | P a g e

Introduction

CRONBID build on top of the RTB standard and offer publishers easy integration.

As RTB is a wide spread and accepted standard it should not take more than 20min to integrate CRONBID

DSP into your own ad flow.

Integrate with us CRONBID receives traffic based on OpenRTB

Welcome to our platform. We'd love to integrate with you.

The purpose of this page is to guide you through the steps to get integrated as a SSP (Supply Side Platform) into

CRONBID DSP.

The CRONBID DSP supports RTB 2.0, 2.1, 2.2, 2.3, 2.4 and 2.5.

1. Get in Touch

Get in touch with your queries at [email protected] or [email protected]

Do not forget to send answers of below Integration questions:

Which OpenRTB versions do you support?

What is your average response time?

Bidder you use( 3rd party or your own)

You’re top 5 strongest Geo.

3 | P a g e

2. Partner registration

You can contact us via email or Fill Registration form directly from our website,

https://www.cronbid.com/register.html

One of our AM will get in touch with you to move forward.

Later we will send you our DSP endpoint URL for integration.

4. SSP must send low QPS traffic for testing

Create a Demo Campaign and send us demo traffic on low QPS.

We will review the demo traffic and after that we’ll approve the SSP based on certain conditions or agreements.

Compression

We support gzip-compression

We accept compressed RTB payload when the request contains the header "Content-Encoding: gzip"

We return a compressed response when the header "Accept-Encoding: gzip" is set in the request

4 | P a g e

Our Endpoint URL may look like this POST Request Endpoint URL

http:// ad-rtb.cronbid.com/rtb/bids/[YOUR_HASH]

Example of RTB Bid Requests Bid Request for a Banner Ad – Example

1

2

3

4

5

6

7

8

9

10

11

12

{

"id": "22222222222222222",

"tmax": 1000,

"bcat": ["IAB24", "IAB25", "IAB26"],

"badv": ["test.com"],

"imp": [

{

"banner": {

"api": [3, 5],

"battr": [1, 2, 3, 17],

"topframe": 1,

"h": 50,

5 | P a g e

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

"w": 320

},

"bidfloor": 0.10,

"bidfloorcur": "USD",

"id": "1111111111",

"instl": 0,

"secure": 0

}

],

"app": {

"bundle": "com.cron.cleaner",

"cat": ["IAB1", "IAB3"],

"id": "234218",

"name": "Test Banner 320X50 - 234218",

"domain": "my.domain.com",

"storeurl": "https://demo.com”

},

"user": {

"yob": "1794",

"gender": "F",

"keywords": "baseball,cars,books",

"ext": {

"consent": "0"

}

},

6 | P a g e

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

"regs": {

"ext": {

"gdpr": 0

}

},

"device": {

"ifa": "00000000-0000-0000-0000-000000000000",

"ua": "Mozilla/5.0 (iPhone; CPU iPhone OS 8_0 like Mac OS X) AppleWebKit/600.1.3 (KHTML, like Gecko) Version/8.0 Mobile/12A4345d Safari/600.1.4",

"ip": "212.232.28.95",

"dpidsha1": "B602D594AFD2B0B327E07A06F36CA6A7E42546D0",

"dpidmd5": "9F89C84A559F573636A47FF8DAED0D33",

"dnt": 0,

"lmt": 0,

"js": 1,

"geo": {

"lat": 28.2000,

"lon": 26.3667

}

}

}

Bid Request for a Video Ad

1

2

{

"id": "22222222222222222",

7 | P a g e

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

"tmax": 1000,

"bcat": ["IAB24", "IAB25", "IAB26"],

"badv": ["test.com"],

"imp": [

{

"video": {

"w": 640,

"h": 480,

"api": [3, 5],

"battr": [1, 2, 3, 17],

"startdelay" : 0,

"minduration" : 5,

"maxduration" : 60,

"mimes": [

"video/x-flv",

"video/mp4",

"application/x-shockwave-flash",

"application/javascript"

],

"linearity": 1,

"boxingallowed": 1,

"playbackmethod": [ 1, 3 ]

},

"bidfloor": 0.10,

"bidfloorcur": "USD",

8 | P a g e

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

"id": "1111111111",

"instl": 0,

"secure": 0

}

],

"app": {

"bundle": "com.cron.cleaner",

"cat": ["IAB1", "IAB3"],

"id": "234218",

"name": "Test Video",

"domain": "my.domain.com",

"storeurl": "http://demo.com"

},

"user": {

"yob": "1794",

"gender": "F",

"keywords": "baseball,cars,books",

"ext": {

"consent": "0"

}

},

"regs": {

"ext": {

"gdpr": 0

}

9 | P a g e

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

},

"device": {

"ifa": "00000000-0000-0000-0000-000000000000",

"ua": "Mozilla/5.0 (iPhone; CPU iPhone OS 8_0 like Mac OS X) AppleWebKit/600.1.3 (KHTML, like Gecko) Version/8.0 Mobile/12A4345d Safari/600.1.4",

"ip": "212.232.28.95",

"dpidsha1": "B602D594AFD2B0B327E07A06F36CA6A7E42546D0",

"dpidmd5": "9F89C84A559F573636A47FF8DAED0D33",

"dnt": 0,

"lmt": 0,

"js": 1,

"geo": {

"lat": 28.2000,

"lon": 26.3667

}

}

}

10 | P a g e

Object Bid Response:

Object/Parameter Type Description

bidid string Unique identifier generated by as per SSP request, which can be used for debugging

Specific bid responses.

BidResponse

cur string Bid currency, always "USD"

Ext object

ext.nbr_reason string Human readable unique error code to identify the type of the encountered error. This

comes in addition to the details communicated in the nbr field for a better integration.

ext.nbr_verbose string Verbose description of the error. This comes in addition to the details communicated in

the nbr and ext.nbr_reason fields for a better integration.

id string Identifier that was sent in "bidRequest.id" in the Bid Request.

nbr integer The no bid reason code as per RTB specification. Refer to the List 5.24 in the OpenRTB

documentation.

Seatbid object

array

Seatbid.Bid object

seatbid.bid.adm string Ad markup containing the actual ad with its trackers.

11 | P a g e

Object/Parameter Type Description

seatbid.bid.adomain string

array

Advertiser domain for block list checking

seatbid.bid.cid string Campaign ID

seatbid.bid.crid string Creative ID

seatbid.bid.h integer Height of the creative

seatbid.bid.id string Unique identifier generated by CRONBID as per each bid, which can be used for debugging

specific bid responses.

seatbid.bid.impid string Identifier that was sent in "bidRequest.imp.id" in the Bid Request.

seatbid.bid.price double Bid price of the winning bid

seatbid.bid.w integer Width of the creative

12 | P a g e

Useful Information

CRONBID DSP ENDPOINT

CRONBID DSP servers are located at multiple physical locations for easy and fast bidding solution.

We’ll provide the URLs of our endpoints and state where they are physically located.

MACROs

CRONBID will replace these macros in ad markup and nURL:

${AUCTION_PRICE}

${AUCTION_CURRENCY}

${AUCTION_AD_ID}

${AUCTION_SEAT_ID}

${AUCTION_IMP_ID}

${AUCTION_BID_ID}

${AUCTION_ID}

13 | P a g e

Locations

Singapore: - 1 Raffles Place, #40-02 One Raffles Place, Office Tower 1, Singapore 048616

India:- 48, 4th Floor, #307, Regent Prime, Whitefield Main Road, Bangalore, Karnataka 560066

Call Us:

+65 97358397 or +91 8042102071

Mail Us:

[email protected] or [email protected]