Issue with Filtered fields

zhi nan

unread,

Dec 5, 2024, 3:21:49 AM 12/5/24

to Authorized Buyers API Forum

We read https://developers.google.com/authorized-buyers/rtb/response-guide/bid-filtering?hl=zh-cn#openrtb , as shown in the figure below, and found the following two problems:

1. The document says to pass detected_sensitive_category and detected_product_category to bcat, but the format of detected_sensitive_category is [10007,11496,13418,13934], but the example of bcat is ["IAB6-4","IAB19-18","IAB19-24"], so how to convert these two? Or use the detectedCategories returned in the Creatives API CreativeServingDecision object instead of detected_sensitive_category and detected_product_category, because its format is ["IAB6-4","IAB19-18","IAB19-24"].

2. There are also some problems with the detected_attributes field.
2.1 It is not in the CreativeServingDecision object and it has expired. How should I get its content?

2.2 The data format does not match. In the Creatives API Creative is DeclaredAttributes []string `json:"declaredAttributes,omitempty"`, but in Openrtb2.5, battr is a []int type

Authorized Buyers API Forum Advisor

unread,

Dec 5, 2024, 3:11:10 PM 12/5/24

to wk794...@gmail.com, google-doubleclick-a...@googlegroups.com

Hello,

I'll respond to your questions in order:

> 1. The document says to pass detected_sensitive_category and detected_product_category to bcat, but the format of detected_sensitive_category is [10007,11496,13418,13934], but the example of bcat is ["IAB6-4","IAB19-18","IAB19-24"], so how to convert these two? Or use the detectedCategories returned in the Creatives API CreativeServingDecision object instead of detected_sensitive_category and detected_product_category, because its format is ["IAB6-4","IAB19-18","IAB19-24"].

Rather than trying to convert between the two, we recommend that you do the latter–use the detectedCategories field in the Real-time Bidding API's creatives resource to determine which creatives should be excluded.

> 2. There are also some problems with the detected_attributes field.
2.1 It is not in the CreativeServingDecision object and it has expired. How should I get its content?

I've actually received similar feedback that I already raised with the engineering team. Discussion is ongoing, but it seems that several attributes found in buyer-declarable-creative-attributes.txtare obsolete–an obvious example being ADOBE_FLASH_FLV ( 3 ). We're currently investigating whether there are valid cases where a creative would have no detected attributes, so we'll need to get back to you on that.

> 2.2 The data format does not match. In the Creatives API Creative is DeclaredAttributes []string `json:"declaredAttributes,omitempty"`, but in Openrtb2.5, battr is a []int type

Yes, this was an issue that became apparent a while back. Please see this mapping guide .

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGnWw:ref" (ADR-00277780)

Thanks,

Mark Saniscalchi

Authorized Buyers API Team

Feedback
How was our support today?

zhi nan

unread,

Dec 6, 2024, 1:41:57 AM 12/6/24

to Authorized Buyers API Forum

Hello,

Regarding the first question, I would like to ask again. Is the id in detected_sensitive_category mapped to IAB-xxx?

Authorized Buyers API Forum Advisor

unread,

Dec 6, 2024, 2:39:25 PM 12/6/24

to wk794...@gmail.com, google-doubleclick-a...@googlegroups.com

Hello,

> Regarding the first question, I would like to ask again. Is the id in detected_sensitive_category mapped to IAB-xxx?

No. You must use the values in the Real-time Bidding API creative resource's detectedCategories field to find the category values that are applicable to OpenRTB. At this time, OpenRTB only indicates blocked categories in the bid request using IAB's Content 1.0 taxonomy. The detectedCategories field is the only method of retrieving blocked categories in that taxonomy at this time.

I've discussed your question concerning creative attributes with the engineering team, and they have clarified that returning no detected attributes is working as intended. It isn't unusual for a creative to have no detected attributes–there are cases where no supported attribute is applicable to a given creative. Likewise, there are many attributes that are simply not populated anymore because they are effectively obsolete. As an example, Google once allowed SSL and non-SSL creatives, and so attributes exist that describe both of these cases. We currently don't populate the attribute for non-SSL creatives because Google currently doesn't support them, meaning that they would never be approved for use in RTB. There are other attributes that are unused because they don't make sense in the detection context–e.g. NON_INTERSTITIAL , IS_USER_INTEREST_TARGETED , etc.

As a result of this feedback though, we are looking into simplifying the data file to remove cases that are obsolete.

Reply all

Reply to author

Forward