Prebid Timeouts
Last edited: 2024/05/16
Prebid Stack requires some time to gather bids. This time is controlled by number of timeouts explained in this article.
The dependencies and flow of particular timeouts is presented on the chart below:
Failsafe Timeout
In Yieldbird Platform Failsafe Timeout applies to the entire Yieldbird configuration, not only to Prebid. Learn more about 
Failsafe timeout
Prebid Auction Timeout
Prebid Auction Timeout sets the duration available for coordinating header bidding activities on the page. In other words, this is the timeframe within which Yieldbird will await for bids from SSPs that are connected to your inventory.
Setting default Prebid auction timeout
Default Prebid auction timeout applies to all inventory in your Workspace unless you select value specific for particular Domain, (or in Old Platform’s case Page or Viewport). To manage it:
Old Platform:
Go to Setup > General > Timeouts.
In the New Platform:
Go to Global setup > Prebid > Defaults: Timeouts.
Setting the timeout for specific Domain
If you require more granular settings, you can adapt the Auction Timeout for particular Domains. To do that:
Old Platform:
- Go to Inventory > Domains > select the domain you want to edit
- Click
Add custom settings. You will be navigated to Custom settings tab, where you can set a timeout and failsafe timeout for the particular domain. - Click
Save
In the New Platform:
- Go to Inventory > Domains > select the domain you want to edit > Prebid Stack: Auction timeout
- Toggle <on> Customize Prebid Auction timeout on this Domain
- Set the Timeout that you want to apply to this Domain only
- Click
Save
Setting the timeout for specific Page
Page architecture If you require you can set timeout for specific Page only. It will override the Timeout set for Domain.
This functionality is available only in the Old Platform. To control it:
- Go to: Inventory > Pages, and then edit the page you want to set a timeout for.
- Toggle <on> Custom Timeout
- Input the desired timeout value
- Click
Save
Setting the timeout for specific Size mapping
Viewports (Devices) If you require you can set timeout for specific size mapping. It will override the Timeout set for Domain and Timeout set for Page.
This functionality is available only in the Old Platform. To control it:
- Go to Inventory > Domains > select the domain you want to edit > Devices
- Toggle <on> Timeout enabled on the Device where you want to set custom timeout
- Set the Auction Timeout that you want to apply to this Device
- Click
Save
How to efficiently manage Prebid Auction Timeouts?
Setting this value requires careful consideration:
- if it's too brief, there isn't sufficient time for header bidding
- if it's too extended, it could decrease revenue by postponing the ad server call until after users have departed the page.
Publishers need to identify the optimal value by weighing various factors such as the average time users spend on the page, direct sell-through rates, the importance of different advertising channels, and the typical network delay experienced by users.
Typically, from our experience the efficient timeout is within 800 - 2000ms range.
Also, setting Prebid Auction timeout require to take into account Failsafe timeout as well - Generally, the recommended relationship between Prebid Auction timeout and Failsafe timeout is that Failsafe is at least 2x longer than Prebid Auction timeout. To make it easier to set it up properly Yieldbird Platform automatically validates the relationship between these two. You can also see the current setting of Failsafe timeout in the Related settings info box.
- Use Revenue as success metric, not rCPM - longer Prebid Auction timeouts (e.g. >3s) reduce the number of ad requests that reach Google Ad Manager, hence analyzing rCPM may lead to wrong conclusions (it simply misses the fact that you decreased the number of ad requests).
- Take a look at your whole Revenue including Directs. Potentially cutting some ad requests will impact not only Open Market, but also Directs. Hence, you must take them into account when looking for optimal timeout setting.
From our experience, once you set the right timeout you don’t have to change it frequently (unless of course you do some significant changes to the setup, especially those including changing the set of bidders.
Timeout Buffer
This setting is applicable to Yieldbird Platform 2.0 only
Timeout Buffer - The JavaScript timer environment lacks perfect accuracy, as other JavaScript running on the page may interfere with the timing of the header bidding auction or delay the recognition of auction results. To compensate for this inconsistency additional Prebid Timeout buffer is added. This buffer helps accommodate the disruptive environment.
This setting is available only on workspace level. To set it up go to Global setup > Prebid > Defaults: Timeouts.
S2S config timeout multiplier
This setting is applicable to Yieldbird Platform 2.0 only
To ensure that bids from Prebid Server return to the client in time for the ad server call, the timespan for Prebid Server to return the bids to the Client is lower than the Prebid Auction Timeout.
S2S config timeout multiplier set’s the timeout for performing S2S auction as percentage of entire Prebid Auction timeout. This means that for example if the Prebid Auction Timeout is 1000ms and the S2S config timeout multiplier is 75%, the S2S timeout for that auction will be 750ms.
This setting is available only on workspace level. To set it up go to Global setup > Prebid > Defaults: Timeouts.
S2S timeout adjustment
This setting is applicable to Yieldbird Platform 2.0 only
To reduce the risk of missing the ad server call on the client side, Prebid Server trims a safety buffer and sends a response to the client slightly before the S2S config timeout. For example, if for particular ad requests the S2S config timeout is 750ms and S2S timeout adjustment is set to 40ms, S2S Bidders will actually time out at 710ms.
This setting is available only on workspace level. To set it up go to Global setup > Prebid > Defaults: Timeouts.
Prebid Timeouts when using Amazon UAM / TAM
When you are using Amazon UAM/TAM implementation through the Yieldbird Platform, the same timeouts that you set for Prebid apply to Amazon as well. To ensure optimal competition between Amazon and Prebid, we do not allow setting different timeouts for Amazon and Prebid.
Amazon UAM/TAM On this page:
- Prebid Timeouts
- Failsafe Timeout
- Prebid Auction Timeout
- Setting default Prebid auction timeout
- Setting the timeout for specific Domain
- Setting the timeout for specific Page
- Setting the timeout for specific Size mapping
- How to efficiently manage Prebid Auction Timeouts?
- Timeout Buffer
- S2S config timeout multiplier
- S2S timeout adjustment
- Prebid Timeouts when using Amazon UAM / TAM