SpringServe allows publishers to include video header bidding (both client-side and server-side) as SpringServe allows publishers to include video header bidding (both client-side and server-side) as part of their demand stack.
...
The size id in Rubicon indicates the position of the video ad.
| Size ID | Position |
|---|---|
| 201 | Pre-Roll |
| 202 | Interstitial |
| 203 | OutStream |
| 204 | Mid-Roll |
| 205 | Post-Roll |
| 207 | Vertical Video |
...
The supply code is the "code" of the parent supply for this Telaria tag. For example, if I have an ad unit called "Header Bidding Tag" whose parent supply in Telaria is "Example.com", the supply code is Example.com", the supply code is the string of characters in the Code field for Example.com:
The ad code is the "code" of the Telaria ad unit itself, so in this case, the string of characters in the Code field for Example.com:
The ad code is the "code" of the Telaria ad unit itself, so in this case, the string of characters in the Code field for Header Bidding Tag:
Alternatively, both of these ids can be found in the exported ad code of the ad unit.
The supply code is the id directly before "ads.tremorhub.com" (in red), and the ad code is found in the "adCode" querystring parameter (in purple).
Once these ids are retrieved, input them into their respective fields in SpringServe.
TheMediaGrid
Supported Integrations: Client Side
TripleLift
Supported Integrations: Client Side and Server Side
...
Code field for Header Bidding Tag:
Alternatively, both of these ids can be found in the exported ad code of the ad unit.
The supply code is the id directly before "ads.tremorhub.com" (in red), and the ad code is found in the "adCode" querystring parameter (in purple).
Once these ids are retrieved, input them into their respective fields in SpringServe.
TheMediaGrid
Supported Integrations: Client Side
TripleLift
Supported Integrations: Client Side and Server Side
Unruly
Supported Integrations: Client Side and Server Side
| Name | Description | Example | Type |
|---|---|---|---|
| Path | String issued by Unruly to the publisher | mvo | str |
| Placement ID | ID issued by Unruly to the publisher | 123456 | str |
| Zone | String issued by RhythmOne to the publisher | 1R | str |
Verizon Media
Supported Integrations: Client Side and Server Side
| Name | Description | Example | Type | Path | String issued by Unruly to the publisher |
|---|---|---|---|---|---|
| Pub Id | Publisher ID of the publisher provided by Video SSP | mypub | str | ||
| Site Id | Identification number of the site | 12345 | str | ||
| Placement ID | ID issued by Unruly to the publisherof the RTB Inventory source setup in Video SSP platform for this ad unit | 123456 | str | Zone | String issued by RhythmOne to|
| api | List of API frameworks supported by the publisher | 1R2 | str |
Verizon Media
...
Vuble
Supported Integrations: Client Side
...