segtax review and field usage mixup concerns about openrtb HOT 4 CLOSED

@patmmccann do you have thoughts on this one?

from openrtb.

I have no idea why this is even relavent to a non California id

from openrtb.

The working group wanted this to be very specific that it was a segment taxonomy not a category taxonomy.
The seg tax tells you which taxonomy you are using that then the segment.id would be vendor specific identifier for a specified segment.

• segtax = 543 means that you are using cafe media's custom audience taxonomy
• segment.id = abc123 could be cafemedia's id for auto-intenders or for publisher a's custom audience, etc.

it's important to note that segment.id wouldn't work for the segment taxonomy reference, because it's meant to articulate which taxonomy is being used, not the value within the taxonomy itself.

i'm not sure how segment.value is used today, but the working group decided not to use it so that it could be very clear on the name/use of segtax.

from openrtb.

data.segment.value is not used in the SDA proposal. If a prebid seller is setting the fields, this is an example of it https://docs.prebid.org/features/firstPartyData.html#first-party-data---prebidjs

from openrtb.