Skip to content
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

Remove restriction on additional bids requiring toplevelseller to be known in advance #1394

Open
mkendall07 opened this issue Feb 5, 2025 · 1 comment

Comments

@mkendall07
Copy link

mkendall07 commented Feb 5, 2025

https://github.com/WICG/turtledove/blob/main/FLEDGE.md#6-additional-bids indicates that

The ... topLevelSeller fields are used to prevent replay of this additional bid.

Additional bids don't have a corresponding call to generateBid(), and so the seller and topLevelSeller fields in an additional bid are intended to allow for the same acknowledgement as those in browserSignals.

Also documented as such in the spec - https://wicg.github.io/turtledove/#additional-bids-section.

Originally posted by @rdgordon-index in #10740

As discussed during the WICG call on 02/05/25 - removing the requirement for additional bids requiring toplevelseller to be known in advance would be beneficial vs trying to pass back and forth this information if the buyer doesn't care who the TLS is.

Proposal:
Allow TLS in additional bids to be optional in the JSON blob returned by the buyer, or to support a wildcard if they don't care what the TLS is.

Ref: prebid/Prebid.js#10740 (comment)

@dmdabbs
Copy link
Contributor

dmdabbs commented Feb 5, 2025

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants