You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 7, 2025. It is now read-only.
A big part of optimizing revenue for publishers involves establishing baseline requirements around the execution of bids from a timing perspective. The current state of FLEDGE does not seem to indicate controls that would allow sellers to set timeouts on execution or to manage timeouts against specific bidders. This is a big issue because if a bidder takes a long time to execute, overall impressions may go down as a result of less ad bid processes resolving per pageview. Is there a way to control timeouts within the bidding process or is this a function that only the browser decides on?
If it is a function only the browser decides on, how does it make that decision and what limits might it set?
A big part of optimizing revenue for publishers involves establishing baseline requirements around the execution of bids from a timing perspective. The current state of FLEDGE does not seem to indicate controls that would allow sellers to set timeouts on execution or to manage timeouts against specific bidders. This is a big issue because if a bidder takes a long time to execute, overall impressions may go down as a result of less ad bid processes resolving per pageview. Is there a way to control timeouts within the bidding process or is this a function that only the browser decides on?
If it is a function only the browser decides on, how does it make that decision and what limits might it set?