You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the OpenRTB Mobile specification, the site and app objects define 3 publisher attributes: “pid” (pub ID on the exchange), “pub” (pub name), and “pdomain” (the pub’s domain). This spec pushed these into a “publisher” object and since a “site” or “app” object has only one “publisher” object, this create an unnecessary point of backward incompatibility. Please restore these attributes as “pid”, “pub”, and “pdomain” to the “site” and “app” objects.
This leaves only the “cat” attribute in the “publisher” object, which means we should decide what to do about “cat” and drop “publisher”. My recommendation on “cat” is to drop it. I don’t really understand how an ad serve/bid decision would use this since the publisher is analogous to a parent company of sites; how are content categories about them meaningful to such a decision versus the site/app categories? If there is a meaningful way to use it, then my alternate recommendation is to rename it “pubcat” and move it to “site” and “app” with the other attributes.
Original author: [email protected] (July 22, 2011 21:19:45)
In the OpenRTB Mobile specification, the site and app objects define 3 publisher attributes: “pid” (pub ID on the exchange), “pub” (pub name), and “pdomain” (the pub’s domain). This spec pushed these into a “publisher” object and since a “site” or “app” object has only one “publisher” object, this create an unnecessary point of backward incompatibility. Please restore these attributes as “pid”, “pub”, and “pdomain” to the “site” and “app” objects.
This leaves only the “cat” attribute in the “publisher” object, which means we should decide what to do about “cat” and drop “publisher”. My recommendation on “cat” is to drop it. I don’t really understand how an ad serve/bid decision would use this since the publisher is analogous to a parent company of sites; how are content categories about them meaningful to such a decision versus the site/app categories? If there is a meaningful way to use it, then my alternate recommendation is to rename it “pubcat” and move it to “site” and “app” with the other attributes.
Original issue: http://code.google.com/p/openrtb/issues/detail?id=28
The text was updated successfully, but these errors were encountered: