-
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
Client Hints HTTP Headers in Buyer Trusted Server Calls #1031
Comments
@talbizit do you mean the "trusted server" as in the KV TEE being used with on-device, KV TEE being used with B&A, or do you mean an untrusted BYOS being used with the on-device? Either way, as a non-Googler I'm interested in what you'd want to use UACH for in the KV call. |
There is a Monorail/buganizer request for this: |
@thegreatfatzby different platforms and OS has different vectors that influence the bid, as these handled by the trusted server, this is why this input is important. @dmdabbs thanks for the update. |
Hi @thegreatfatzby @dmdabbs - and word from the Chromium team on fix ETA? |
None @omriariav. I just inquired on that buganizer ticket. I suggested that the new Real-Time Reporting API histogram postbacks include low entropy UACH. Paul Jensen suggested I note that interest on this issue. @JensenPaul I'd like to also register interest in receiving low entropy UACH on PAAPI
|
Is this also being considered for trusted scoring signals HTTP calls? And, if so, does this need a separate issue? |
@michaelkleber, as discussed in the WICG meeting, I'd appreciate it if you relay here as well the explanation you made in the call. Thanks! |
@rdgordon-index et al., per today's discussion I have opened #1239 (Real-Time Reporting) and #1240 (updateURL fetches). |
Hi all. As we discussed last week (notes), including these signals in the calls to the Buyer Trusted Server does not seem particularly pressing, because the information is already available in the auction through several other channels — it can be injected at the time of calling For example, if you want to pick and choose which ads ought to be shown on this device based on its device type, then that's a decision you can make at There is a more compelling case for making the low-entropy UACH signals available during the IG's periodic calls to its |
Currently, the buyer trusted server does not receive Client Hints HTTP headers. Can this feature be added?
The text was updated successfully, but these errors were encountered: