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

How to include Google Interest Groups in Publisher-run Protected Audience API? #82

Open
wojciech-bialy-wpm opened this issue Nov 20, 2023 · 0 comments

Comments

@wojciech-bialy-wpm
Copy link

We're now testing Protected Audience API (PAAPI) on our websites. At the moment, we've split PAA-enabled inventory into two sets:

  • on 50% of the inventory, PAAPI auction is initiated by the Google Ad Manager, and includes component auctions provided by the publisher
  • on the remaining 50% of the inventory, PAAPI auction is initiated by the publisher, and runs partly in parallel to header bidding / adserver calls

This test setup is described in the following issue to WICG/Turtledove github:
WICG/turtledove#851

The purpose of this test is to ascertain both revenue and UX impact of sequential and parallel PAAPI setups.

However, validity of the test depends on executing both types of auctions with the same set of buyers. This is ensured for our partners (using the same component auction configs in publisher-initiated and Google-initiated top level auctions), but is there a additional 3rd party demand from Google Ads, that is used in Google-initiated top level auctions? If so, can You provide a Google component auction config we can use?

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

1 participant