Get started with Prebid Stack

Last edited: 2024/05/02

Before you start please implement Yieldbird Platform. Learn more.

Yieldbird team will add the first Domain, including ad units for you. This way you will be able to use this implementation as a template for adding additional Domains. If you need assistance in the process, do not hesitate to reach out to your Customer Success Manager.

1. Set general settings

In Setup > General > Timeouts define the general timeouts for the entire workspace. Unless you set specific timeouts per domain, page, or device, these are the timeouts that will apply everywhere.

Set general settings for Prebid Stack and

Prebid Timeouts

2. Add bidders

Next step is defining which Bidders (SSPs) you want to use with Prebid Stack. You can use:

Own Accounts (Own Bidders). These are the Bidders with whom you have a direct relationship (have signed a contract) and they have whitelisted your domain.

Yieldbird account (Yieldbird Bidders). These are Bidders with whom Yieldbird has signed contracts and owns the accounts. You can request to use them.

Add Bidders

3. Set up Prebid Stack in your GAM

Prebid Stack requires implementation in Google Ad Manager. This includes:

Creating Orders and Line Items or enabling Header Bidding trafficking (GAM 360 & limited number of Bidders only)
Creating key values

Set up Prebid Orders in your GAM

4. Update your ads.txt

To ensure the proper authorization and transparency in the selling of ad inventory, it is essential to update the ads.txt file on a domain after adding a new SSP to the header bidding stack. By updating the ads.txt file, you allow buyers to verify that the new SSP is authorized to sell ad space on your domain, preventing unauthorized sellers from misrepresenting your inventory.

Update your ads.txt

On this page: