Original author: logar.da...@gmail.com (October 24, 2011 10:36:01)
We believe that bidresponse.brespextensions should be defined as object and not as string, since this is data specified by exchange. Therefore both exchange and dsp should be able to interpret/process/use it. Same applies to bidresponse.bidset[x].bid.bidextensions.
bidresponse.customdata is ok as string, since this is used only by dsp and exchange will not process/intrpret/use this data in any way. If DSP sends data encoded as string, so can dsp also interpret this (his) string received back from adexchange.
Original issue: http://code.google.com/p/openrtb/issues/detail?id=39
Original author: logar.da...@gmail.com (October 24, 2011 10:36:01)
We believe that bidresponse.brespextensions should be defined as object and not as string, since this is data specified by exchange. Therefore both exchange and dsp should be able to interpret/process/use it. Same applies to bidresponse.bidset[x].bid.bidextensions.
bidresponse.customdata is ok as string, since this is used only by dsp and exchange will not process/intrpret/use this data in any way. If DSP sends data encoded as string, so can dsp also interpret this (his) string received back from adexchange.
Original issue: http://code.google.com/p/openrtb/issues/detail?id=39