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.

Sign up for GitHub

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

Jump to bottom

Who chooses the size for a protected audience auction (PAA)—the Publisher, Top Seller, or Chrome internal logic? #908

Open
pm-harshad-mane opened this issue Nov 15, 2023 · 2 comments
Open

Who chooses the size for a protected audience auction (PAA)—the Publisher, Top Seller, or Chrome internal logic? #908

pm-harshad-mane opened this issue Nov 15, 2023 · 2 comments

Comments

@pm-harshad-mane
Copy link

pm-harshad-mane commented Nov 15, 2023 •
edited

When an ad-slot backs various sizes like A, B, and C, the PA only backs one size at a time.
It seems that Chrome has the ability to check the available IGs on a device and the supported ad sizes for each IG in this situation.
Who chooses the size for a protected audience auction (PAA)—the Publisher, Top Seller, or Chrome internal logic?
Can the Privacy Sandbox standardize the supported size consistent in PA to prevent potential data leaks caused by random ad sizes that could identify a user?
@rdgordon-index rdgordon-index mentioned this issue Nov 15, 2023
Merged
@rdgordon-index
Copy link
Contributor

cf. https://github.com/google/ads-privacy/tree/master/proposals/fledge-multiple-seller-testing#faq

@rdgordon-index
Copy link
Contributor

Given all the other changes related to sizes -- for example, #928 -- have we made any headway on this topic?

This was referenced Mar 25, 2024
Open
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pm-harshad-mane @rdgordon-index