Advanced prebid.js settings
Last edited: 2025/05/27
The Prebid Stack in the Yieldbird Platform allows you to granularly control advanced prebid.js settings to adapt them to your specific needs.
Setting advanced prebid.js settings
You can configure Prebid advanced settings either as a default for the entire Workspace or customized for specific Domains.
Workspace Defaults To apply advanced settings across all Domains in your Workspace:
- Go to Global Setup > Prebid > Defaults.
- Set the desired parameters. These defaults will apply to all Domains unless you override them on a Domain level.
Domain-Level Customization To customize advanced settings for a specific Domain:
- Go to Inventory > Domains > (Edit).
- Scroll to Prebid Stack: Advanced Settings.
- Toggle <on> ‘Customize [setting name] on this Domain’
- Specify the desired parameters - these will apply only to the selected Domain.
Activity controls
Activity Controls in Prebid.js manage "potentially restricted activities" related to privacy regulations, such as:
- Setting cookies
- Syncing IDs
- Transmitting user data
These controls act as gatekeepers, deciding whether an activity is allowed in a given context (e.g., "Can I set a cookie for bidder A?"). The configuration can come from modules, custom page functions, or a JSON rules file.
Attention: Due to the complexity and variability of use cases for allowActivities, this feature requires JavaScript snippets instead of standard JSON configuration files. Please refer to the example below for correct implementation.
Example: Config that disables accessing local storage (including cookies) for everything except the bid adapterbidderX
(source)pbjs.setConfig({ allowActivities: { accessDevice: { default: false, rules: [{ condition(params) { return params.componentName === 'bidderX' }, allow: true }] } } })
auctionDelay
Auction Delay (auctionDelay
) is the duration of time added after loading prebid.js but before sending bid requests to Bidders. Some User ID or Vendor Specific modules may require this delay to be extended, allowing more time for them to complete their actions.
Best practices:
- In most implementations, auctionDelay should be set to 50ms.
- Some AdOps teams use the following guideline to calculate the appropriate auctionDelay based on the number of Vendor-Specific Modules implemented for a Domain:
- 1 Vendor-Specific Module: auctionDelay = 50ms
- 2 Vendor-Specific Modules: auctionDelay = 100ms
- 3 Vendor-Specific Modules: auctionDelay = 150ms, and so on.
- If you are unsure about the auctionDelay requirements for the Vendor-Specific Modules you use, we strongly recommend reaching out to the module provider directly for the most up-to-date guidance.