search

csepena / openrtb

Automatically exported from code.google.com/p/openrtb
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

OpenRTB User Association & Token Service API #6

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
>> 3. Do you have plans to add user matching in the spec? If so, when 
>> could we expect to see a draft of it?
>>
>> 4. Have you considered custom data? By that I mean if the buyer wants 
>> to add cookie-like data to be added in the user matching step or in 
>> the response of a bid, and then expect it to be available in the next 
>> bid request originating from the same user.

Original issue reported on code.google.com by js...@pulsepoint.com on 21 Mar 2011 at 4:21

GoogleCodeExporter commented 9 years ago 
We have attached a proposal for a specification regarding User Matching and 
Custom Data. 

We also have three points we would like to discuss:

1. Name convention. In the OpenRTB both buyer and bidder are used. We use 
bidder since it seems to be the most correct description. Maybe something to 
look into to standardize more.

2. Time format. In the blocklist spec, you use Unix/Posix time. We would really 
want to use iso8601 instead since it's a more descriptive and future proof 
format.

3. We don't have great experience in json, but passing json object in the url 
seems to be widely used. We had a thought that it could be an alternative way 
of sending User Matching objects back and forth. What is your opinion on this?

Best Regards,

Patrik Oscarsson, Admeta AB

Original comment by patrik.o...@gmail.com on 23 Mar 2011 at 7:53

Attachments: