Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No-Bid Possibilities #33

Open
chompi opened this issue Jan 23, 2013 · 0 comments
Open

No-Bid Possibilities #33

chompi opened this issue Jan 23, 2013 · 0 comments

Comments

@chompi
Copy link
Owner

chompi commented Jan 23, 2013

Original author: jim.but...@nexage.com (July 22, 2011 21:29:41)

The bid array (Section 4.3.2) is specified as required as is its parent. This makes sense, since a no bid can be expressed as a completely empty bid response. Our experience in integrating bidders to our OpenRTB Mobile compliant exchange, however, is that some send empty responses, some send an empty seatbid array or no seatbid array, some send seatbid objects without bid objects. We found that it is acceptable simply to interpret the absence of any of these essentials as a valid no-bid. There’s really nothing else for the exchange to do; if it doesn’t have the essentials for a bid, then it’s a no bid.

Based on this, the bid and seatbid arrays are not technically required since the bidder is not required to make a bid. I would update the spec to reflect this, but I would also recommend adding a “Best Practice” statement indicating that the preferred means of expressing a no-bid is the bandwidth friendly empty response.

Original issue: http://code.google.com/p/openrtb/issues/detail?id=33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant