Inventory > Ad units > General: Media Types
Last edited: 2025/03/19
Media Types: Ad unit configuration where you specify the sizes of Prebid Media Types (e.g., Banner, Video) that can be served on the ad unit. If needed, you also define parameters for Native and Instream / Outstream Video ad units.
Go to Inventory > Ad units > select the ad unit that you want to edit > General: Media Types
Select:
<aside> <img src="/icons/arrow-right_green.svg" alt="/icons/arrow-right_green.svg" width="40px" /> Good practice: We recommend first defining Viewports (Devices) and the list of sizes you want to apply based on the detected user’s viewport width. When you select the option to define sizes per viewport width, the Media Types will already be populated with the list of sizes you defined per Viewport. This allows you to easily exclude unwanted sizes or add additional ones if necessary.
</aside>
Select the Media Types you want to apply to the given Ad Unit. You can use Banner, Outstream Video, and Native simultaneously. However, if you select Instream Video, no other Media Type can be added to the same Ad Unit.
Define the sizes you want to use. These sizes will be requested from Prebid and Amazon UAM/TAM (if applicable). Note that Player size applies to both Outstream and Instream Video.
<aside> <img src="/icons/link_yellow.svg" alt="/icons/link_yellow.svg" width="40px" /> Related documentation:
AB Fixed Size Ad Specifications: https://www.iab.com/wp-content/uploads/2019/04/IABNewAdPortfolio_LW_FixedSizeSpec.pdf
</aside>
If you want to use Outstream, Instream, or Native Media Types, add the JSON configuration object:
Video (Instream / Outstream):
Exemplary Outstream video configuration code:
{
"api": [2],
"mimes": [
"video/mp4",
"video/x-flv",
"video/x-ms-wmv"
],
"linearity": 1,
"protocols": [1, 2, 3, 4, 5, 6],
"maxduration": 10,
"playbackmethod": [2]
}
<aside> <img src="/icons/link_yellow.svg" alt="/icons/link_yellow.svg" width="40px" />
Full list of available parameters: Prebid Documentation.
</aside>
Native
Exemplary, properly formatted native configuration code is below (please pay attention to proper formatting of the brackets):
{
"body": {"required": false},
"icon": {"required": false},
"image": {
"sizes": [[300, 200]],
"required":true
},
"title": {"required": true},
"sponsoredBy": {"required": false}
}
<aside> <img src="/icons/link_yellow.svg" alt="/icons/link_yellow.svg" width="40px" />
Full list of available parameters: Prebid Documentation.
</aside>
<aside> <img src="/icons/new-alert_red.svg" alt="/icons/new-alert_red.svg" width="40px" />
Attention: Makes sure that you use the proper JSON formatting. Learn more.
</aside>
Optionally, if you want to use Instream video Media Type, you can define a Video Player provider. This would mean, that the Yieldbird Platform will add the prebid modules that handle implementation with these players.
<aside> <img src="/icons/link_yellow.svg" alt="/icons/link_yellow.svg" width="40px" />
Learn more about Prebid Video module: Prebid Documentation.
</aside>
To do that:
<aside> <img src="/icons/new-alert_red.svg" alt="/icons/new-alert_red.svg" width="40px" />
Important: Using Prebid Stack on Instream Video or Native Media Type Ad Units requires dedicated Line Items in GAM. Make sure to create them before proceeding. Learn more.
</aside>
On this page: