Implementing Yieldbird Tags
Path in Platform: Download tags
Last edited: 2024/02/26
The Yieldbird Tag is implemented only once. You do not have to update nor adapt it in any way when you change the configuration inside Yieldbird Platform or try new products.
By Default we recommend using Open Tags which are implemented only in the Header. Open Tags are able to serve configurations of all Yieldbird’s products.
Types of Yieldbird tags:
Warning: Yieldbird Platform Tags are meant only for Web (Mobile & Desktop). If you want to implement with AMP and / or App please contact your Customer Success Manager.
See 
On which environments can I use Yieldbird Platform? article to see the availability of particular Yieldbird Platform modules for particular environments.
On which environments can I use Yieldbird Platform? article to see the availability of particular Yieldbird Platform modules for particular environments.Open Tags vs Smart Tags: key differences
We recommend using Open Tags since they are much quicker and very secure during the implementation process (they basically cannot disrupt your ad serving process).
However, you can switch between Open Tags and Smart Tags any time - all you need to do is replace the existing tag with a new one.
In the table below, you can find a few key differences between these two:
Area | Open Tags (Default) | Smart Tags |
Controls GPT? | no | yes, actually replaces existing GPT tags |
Tag structure | The functions associated with auction rules are “open” and visible; theoretically, this may cause interference between different scripts that affect auction rules (e.g., refresher or lazy load). | All functions associated with auction rules are encapsulated within the script (not visible); the values and state of structured data are protected. |
Script execution | Page script, ad units, and Yieldbird scripts are executed asynchronously and independently. | Page script and Yieldbird scripts are executed asynchronously, but ad units are executed after the Yieldbird script in the header is fully executed. This allows to be sure that all ad units are rendered only when Yieldbird configuration is fully rendered - this prevents situations where ad units are rendered before e.g., Prebid configuration is fully executed, which leads to no Prebid working on such ad unit in a given page view. |
Key upsides | Simpler implementation | Allows to be 100% sure that all configuration and Yieldbird targeting are executed before rendering ad requests. |
Implementation | In the Header only | In the Header and in Body (for each ad unit separately) |
Recommended usage | All Yieldbird products | Cases when:
- you are using Yieldbird’s Prebid Stack and want to be 100% sure that Prebid will always fully execute.
- you are using PriceGenius with Yieldbird’s demand |
← Previous
On this page:
Not sure if the tag is implemented properly?
Contact Yieldbird as soon as it is live (even if just on staging), we will double verify it.