Creative Attributes in Table 5.3 for Bid.attr

[Haskell Garon]

I had a question about Bid.attr and the associated attributes in table 5.3: http://www.iab.com/wp-content/uploads/2016/11/OpenRTB-API-Specification-Version-2-5-DRAFT_2016-11.pdf.

The table has 17 possible attributes, but I don't think there is guidance on exchange specific attributes.  Is it reasonable for us to use IDs 100+ for exchange-specific attributes, or have other companies typically done this with extensions instead?  Any guidance or tips on how others have standardized this would be helpful.

[Jim Butler]

Sounds reasonable, but I'm not sure this has come up before.

:JB

On Thu, Jan 19, 2017 at 4:51 PM, 'Haskell Garon' via openrtb-dev <openr...@googlegroups.com> wrote:

I had a question about Bid.attr and the associated attributes in table 5.3: http://www.iab.com/wp-content/uploads/2016/11/OpenRTB-API-Specification-Version-2-5-DRAFT_2016-11.pdf.

The table has 17 possible attributes, but I don't think there is guidance on exchange specific attributes.  Is it reasonable for us to use IDs 100+ for exchange-specific attributes, or have other companies typically done this with extensions instead?  Any guidance or tips on how others have standardized this would be helpful.

--
You received this message because you are subscribed to the Google Groups "openrtb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrtb-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

James M. Butler, Ph.D.

VP Engineering, Publisher Platforms | AOL Platforms

155 Seaport Blvd, 8th Floor, Boston MA 02210

+1.617.834.2125 | Mobile

jim.b...@teamaol.com

 

This electronic message transmission contains information from AOL Inc., which may be confidential or privileged. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of this information is strictly prohibited. If you have received this electronic transmission in error, please notify sender immediately and delete all copies.

[Ian Trider]

I think native typically uses 500+ to leave ample room, doesn't it?

Alternately, I would argue that perhaps exchange-specific values in standardized fields like this might not be the 'right' thing to do.. rather, introduce your own field in the extension object.

On Thursday, January 19, 2017 at 10:28:42 PM UTC-5, Jim Butler wrote:

Sounds reasonable, but I'm not sure this has come up before.

:JB

On Thu, Jan 19, 2017 at 4:51 PM, 'Haskell Garon' via openrtb-dev <openr...@googlegroups.com> wrote:

I had a question about Bid.attr and the associated attributes in table 5.3: http://www.iab.com/wp-content/uploads/2016/11/OpenRTB-API-Specification-Version-2-5-DRAFT_2016-11.pdf.

The table has 17 possible attributes, but I don't think there is guidance on exchange specific attributes.  Is it reasonable for us to use IDs 100+ for exchange-specific attributes, or have other companies typically done this with extensions instead?  Any guidance or tips on how others have standardized this would be helpful.

--
You received this message because you are subscribed to the Google Groups "openrtb-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openrtb-dev...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.