RTB and Protected Audience

[edison yang]

Hello google,

we are currently trying to combine Protected Audience API with RTB. According to the documentation, if ON_DEVICE_INTEREST_GROUP_AUCTION is 1, the interest group bidding and the final auction runs in the browser. we have the following questions:

1. Should we still bid and return the ad and price as the traditional RTB , or will we return  "intent to participate" (BidResponse.ext.igbid) and wait for the second interaction with the browser to submit a formal bid and price ?
2. For the request with Protected Audience mode, will the traditional RTB bid response and the Protected Audience response be compared together for price, or only one type of them be selected?

Thank you for your help!

Best regards,

Edison

[Authorized Buyers API Forum Advisor]

Hello Edison,

Thanks for reaching out, but unfortunately experimental features like Protected audience aren't in this support alias's domain of expertise. I'm going to reach out internally to see whether I can direct you to a different contact for this topic, or have them assist in answering your question.
 

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

Thanks,
 

Mark Saniscalchi Authorized Buyers API Team

[Authorized Buyers API Forum Advisor]

Hello Edison,

I was able to quickly get some answers to your questions.

> Should we still bid and return the ad and price as the traditional RTB , or will we return  "intent to participate" (BidResponse.ext.igbid) and wait for the second interaction with the browser to submit a formal bid and price ?

When using PA, you can submit bids the traditional way and via in-browser bids. There is no restriction on placing both kinds in the same response.

> For the request with Protected Audience mode, will the traditional RTB bid response and the Protected Audience response be compared together for price, or only one type of them be selected?

Yes, they can be compared against one another.

[edison yang]

Hello ,

Thanks for your reply. 

We would like to ask if there are more detailed links about the integration of RTB and PA (except the document below), specifically for the explanation of the BidRequest.imp.ext field (especially regarding PA)
 https://developers.google.com/authorized-buyers/rtb/downloads/open-beta/openrtb-adx-proto

btw, we also need your help with the following questions:

(1) Will the publisher/browser send <interest group or related information> to Google AdX, and then to DSPs?

(2) If the information is not sent, how will DSPs know if the user has visited their website and thus decide whether to participate in PA?

(3) If such information is sent, what specific details are included? or is it could be a custom JSON?

For a bid request with AE=2(PA):

• DSP_1: bid with price of 100 in the traditional RTB mode.
• DSP_2: bid with 80 + PA.
• DSP_3: does not bid, but PA.
• DSP_4: bid with price of 80 in the traditional RTB mode

(1) Will Google AdX return all 4 DSPs to the browser for the second bid? Or will AdX filter some bids based on specific rules? For example, it could select the highest bid from the traditional RTB and then include all PA-related bids

(2) When the browser receives the request, does DSP_2 need to recalculate the price for PA (e.g., possibly 120)?

(3) If DSP participate in both tworounds of bidding, for the first round, there is a time constraint of 100-300ms (min_ms) , does the second bidding in the browser also have a time limit?

Best regards

Edison YANG

[Authorized Buyers API Forum Advisor]

Hello Edison,

>We would like to ask if there are more detailed links about the integration of RTB and PA (except the document below), specifically for the explanation of the BidRequest.imp.ext field (especially regarding PA)

Yes, there is more content you can reference to learn about the Protected Audience API than the protos themselves. For Authorized Buyers's implementation, we also provide this guide.

For your other Protected Audience API questions, I will once again consult with the engineering team internally.