-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose full URL to buyer's K/V server for content/contextual/site targeting #1105
Comments
Worth noting that this will potentially significantly reduce cache hit rates, in cases where key/value responses allow caching (particularly for DSPs, where requests are more likely to have the same keys again and again). So we'd probably want to make getting the full URL opt-in, in addition to gating it on using a TEE server. |
We (Chrome and TEE KV server team) are discussing internally about the potential approaches and we'll provide some update next week. |
We appreciate your interest in using the fully attested production version of the KV server in TEE. Here's what you need to know:
|
Hi - Taboola team also wants to point out that this proposal can help with native advertising ad quality needs where the buyer wants to avoid showing the ad on a seller page based on the full URL and other page contextual taxonomies ("Contextual / brand safety classification") |
Yahoo DSP is highly interested in the ability to receive the full URL to our K/V server for Protected Audience buying. This is a prerequisite for scaled adoption of Protected Audience by our customers (advertisers) and enables 2 critical use cases:
Along with offline loading of per-URL classification data and campaign configuration data into the K/V server, we intend to create a user-defined function (in our K/V server) that would perform efficient filtering of eligible campaigns through trusted bidding signals. We would prefer to implement this as soon as possible within the existing client-side auction environment, as opposed to waiting for future availability of Bidding & Auction Services.
Per existing issue #892 we understand Chrome has considered making the URL available to a K/V server running in TEE mode over an encrypted request protocol. Yahoo DSP would prefer an opt-in feature that can be configured by the buyer only (corresponding to the first suggestion from @michaelkleber in issue #892- "Making it possible for an IG to pick a K/V server which the browser can be sure is running in a TEE"). Assuming that is made available in Chrome, Yahoo DSP would begin testing the capability by creating interest groups with the opt-in flag set and pointing to an instance of our K/V server configured appropriately (running in TEE mode with required encryption keys / attestation etc).
The text was updated successfully, but these errors were encountered: