Overview

Add event listener support for the Protected Audience API's navigator.runAdAuction to enable better monitoring and response handling of auction states.

Events:

1. auctionstart: Fired when runAdAuction is dispatched.
2. auctioncomplete: Fired when runAdAuction promise is resolved.
3. auctionerror: Fired when runAdAuction promise is rejected.

Event Details:
For now, the event detail can be kept to a minimum to ensure proper user privacy. For this feature request, the required event data includes:

• component sellers and their buyers - As a component seller, I need to understand which auctions I am participating in and who my buyers are.

Example Usage

navigator.runAdAuction.addEventListener('auctionstart', (event) => {
  console.log('Auction started:', event.detail);
});

navigator.runAdAuction.addEventListener('auctioncomplete', (event) => {
  console.log('Auction completed:', event.detail);
});

navigator.runAdAuction.addEventListener('auctionerror', (event) => {
  console.log('Auction failed:', event.detail);
});

User Stories

Given I am a component seller
When I defer control of the runAdAuction call
Then I cannot monitor the number of auctions that are started, completed, or rejected.

FAQ

1. Why do we defer control of the runAdAuction call? - Integration with Google Publisher Tag requires component sellers to defer control so that the ad server auction can complete.