Creating inventory in Yieldbird Platform

Last edited: 2024/02/26

In order to be able to configure the settings of particular products in the Yieldbird Platform, you need to first replicate your Domains and Ad Units.

1) Create Domains

First you must create the Domains. To do that:

  1. Go to Inventory > Domains > ‘Add new’
  2. Provide Domain name
  3. Click ‘Save’

Once you create a domain, you can:

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> Creating domains is necessary to be able to Implement Yieldbird Tags. However, you can add your ad units before the tag is implemented.

</aside>

2) Create ad units

To create ad units you can do one of the following:

  1. Use Bulk management (recommended, as it allows you to add all ad units at once)
  2. Add ad units manually:

    1. Go to Inventory > Ad Units > ‘Add new’

    2. Provide at least <ad unit path>

    3. If the ad unit is one of out of page formats (Interstitial / Anchor), also define it

      <aside> <img src="/icons/new-alert_red.svg" alt="/icons/new-alert_red.svg" width="40px" /> Attention: if you do not define ad unit as out of page:

      • Prebid Stack will not pass on the info that ad unit is in out of page format to Bidders, and they would not be able to bid accordingly (potentially this means lower eCPMs)
      • If you are using Smart Tags they will not work properly on these ad units. </aside>

    4. Click ‘Save’

Rules for creating ad units:

  1. Ad unit path is required, however you don’t have to provide the full path unless you need a to configure a distinct ad unit path differently.

    Example:

    You want the same config in Yieldbird Platform for all child ad units of an ad unit /network_code/parent except a single child /network_code/parent/child1/child2

    In such scenario you need to define two ad units in Yieldbird Platform: one with path /network_code/parent and one with path /network_code/parent/child1/child2. Then Yieldbird Tag will pass on the same config to all children of /network_code/parent except /child1/child2 which will get its own config

  2. You can leave the <div id> empty, unless your setup includes cases where you use the same ad unit path on multiple div ids within one Domain.

Flow of detecting ad units and passing the configuration to them

Below is the explanation on how does Yieldbird Platform create the configurations and key value targeting for particular ad units that

  1. First we look for ad unit path only (down to the most granular level defined in the platform
  2. Then we look for combinations of ad unit path and div id (if there are any defined on a given domain)

Example:

You defined the following ad units in Yieldbird Platform

ID (Yieldbird) Ad unit path Div id Configuration* number:
#Y1 /3210/parent1 - Config A
#Y2 /3210/parent2 - Config B
#Y3 /3210/parent1/child1 - Config C
#Y4 /3210/parent1/child2 - Config D
#Y5 /3210/parent1/child2 div1 Config E
#Y6 /3210/parent1/child2 div2 Config F

*The configuration refers to the configuration in Yieldbird platform - which Yieldbird modules are on and with which parameters (e.g. which bidders are enabled and their bid params etc.)

Then, on a given pageview we detected we detected the following ad units:

ID (page) Ad unit path Div id Final configuration received:
#P1 /3210/parent1/child2 div1 Config E
#P2 /3210/parent1/child3 div2 Config A
#P3 /3210/parent2/child1 div3 Config B
#P4 /3210/parent2/child2 div4 Config B

What exactly happened?

  1. First we looked for ad unit paths:
    1. /3210/parent1 (#Y1) → found ad units #P1 and #P2 and gave them config A
    2. /3210/parent2 (#Y2) → found ad units #P3 and #P4 and gave them config B
  2. Then we looked for ad unit paths:
    1. /3210/parent1/child1 (#Y3) → found ad unit #P1 and gave it config D
    2. /3210/parent1/child2 (#Y4) → didn’t find it, nothing happened
  3. Then we looked for ad units that were defined with not only ad unit path but also div id in Yieldbird Platform:
    1. /3210/parent1/child2 - div1 (#Y5) → found ad unit #P1 and gave it config E
    2. /3210/parent1/child2 - div2 (#Y6) → didn’t find it, nothing happened
  4. The final configs passed to particular ad units on the page are shown in the column Final configuration received in the table above.

When should I add div ids to the configuration of ad units?

Adding div id to ad unit definition is optional in Yieldbird Platform. There are however several use cases it might be helpful to add them.

#1 General rule of thumb: every time you use multiple GAM ad units (ad unit paths) on one div id

If your setup involves using the same GAM ad unit in multiple places on the page (on different div ids), you need to add div ids to the ad unit definition in Yieldbird Platform if you need to set different configurations for each div id.

Example:

You have Top banner ad showing on all your article pages. Let’s assume you have 3 article categories: news, sport, finance. For each of these articles you need different configuration of e.g. Prebid (e.g. different set of Bidders) and Refresher.

You current technical setup looks as follows:

Now if you want to differentiate the setup of Yieldbird Platform for each of these ad units you must add the following ad units to the platform:

  1. ad unit path: /[GAM network code]/top-banner div id:top-banner-news
  2. ad unit path: /[GAM network code]/top-banner div id:top-banner-sport
  3. ad unit path: /[GAM network code]/top-banner div id:top-banner-finance

<aside> <img src="/icons/arrow-right_green.svg" alt="/icons/arrow-right_green.svg" width="40px" /> Good practice: In case you have such setup we recommend to align the list of div ids and ad units created in GAM so as they are 1:1 the same.

</aside>

#2 When you want to use Smart Tags

Since Smart Tags replace gpt tags in the body section of your page, we require div ids in order to be able to generate them.

#3 When you want to disable Auction per ad unit