Bid Request Missing Restrictions

The OpenRTB Mobile specification included an optional “restrictions” object 
that carried two optional blocklists (i.e., string arrays):  “bcat” for 
blocked content categories for which values would be from Section 6.1 of the 
2.0 draft, and “badv” for blocked advertiser domains.  I understanding that 
the OpenRTB preferred means of communicating such restrictions is a non-RT API 
and this it is in our near term roadmap to support this in our exchange.  
However, not all exchanges and not all bidders will prioritize building support 
for those APIs.  Our experience and that of several bidders who are buying from 
us is that it is easier to get started with the restrictions in the bid request 
albeit less efficient from a bandwidth perspective.

We have built into our exchange the ability to include/exclude these 
restrictions on a bidder by bidder basis.  This way, when we complete our 
non-RT sync APIs, bidders will have the choice of how to receive restrictions.  
Furthermore, we want to reserve the right to suppress restrictions from the bid 
request only after we’re satisfied that a given bidder is properly using the 
non-RT sync.  We can’t necessarily force a bidder to act on restrictions 
however they are sent, but we need to represent to our publishers that we as 
their SSP are doing what we can.

Original issue reported on code.google.com by jim.butler%nexage.com@gtempaccount.com on 22 Jul 2011 at 9:06

rainzq / openrtb

Bid Request Missing Restrictions #20