Header Bidding
SpringServe allows publishers to include video header bidding (both client-side and server-side) as part of their demand stack.
NOTE: On VPAID supply tags, these demand tags are automatically added to a Broadcast tier of targeted supply tags' waterfalls.
- 1 Creating Header Bidding Demand Tags
- 1.1 Platform
- 1.2 Floor Type
- 1.3 Floor Rate/Margin
- 1.4 Tier Breakout
- 1.5 Bid Parameters
- 2 Adding Header Bidding Demand Tags to Supply Tags
- 3 Supported Platforms
- 3.1 33Across
- 3.2 AMX (AdaptMX)
- 3.3 AdYouLike
- 3.4 Amazon
- 3.5 Audience Media TV
- 3.6 Beachfront SSP
- 3.7 Beachfront Unified Decisioning
- 3.8 BrealTime (EMX Legacy)
- 3.9 Chocolate Platform
- 3.10 Conversant
- 3.11 Criteo
- 3.12 DMX
- 3.13 Digital Remedy
- 3.14 Elemental TV DSP
- 3.15 Equativ (Legacy Smart Ad Server)
- 3.16 Facebook Audience Network (Beta)
- 3.17 Freewheel (Sticky Ads)
- 3.18 Glewed
- 3.19 GumGum
- 3.20 Improve Digital
- 3.21 InMobi
- 3.22 Index Exchange
- 3.23 Kargo
- 3.24 Legacy VGI CTV
- 3.25 Magnite DV+
- 3.26 Magnite Streaming
- 3.27 Magnite: Telaria
- 3.28 NoBid
- 3.29 OneTag
- 3.30 OpenX
- 3.31 Opera Ads
- 3.32 Origin Media
- 3.33 PubMatic
- 3.34 PulsePoint
- 3.35 Rise (Legacy Iron Source)
- 3.36 Roku
- 3.37 Samsung and Samsung Staging
- 3.38 Sharethrough
- 3.39 Smaato
- 3.40 Smartclip
- 3.41 Sonobi
- 3.42 Stroeer
- 3.43 Synacor
- 3.44 TappX
- 3.45 Teads
- 3.46 TheMediaGrid
- 3.47 TheViewPoint
- 3.48 TripleLift
- 3.49 TrustX
- 3.50 Unruly
- 3.51 Unruly Client Side
- 3.52 VGI CTV
- 3.53 Verizon Media
- 3.54 Video Intelligence
- 3.55 Vuble
- 3.56 Xandr
- 3.57 Xaxis
- 3.58 Yahoo SSP and Yahoo SSP Multibid
- 3.59 Yield Nexus
- 3.60 YieldLab
- 3.61 Yieldmo
- 3.62 district m
- 4 Optional Parameters
- 5 Removing Fees for Bidders Returning Gross Prices
Creating Header Bidding Demand Tags
To create new header bidding demand tags, go to the Demand tab and begin the standard demand tag creation process which can be done through a specific demand partner, campaign, or in the Demand tab by selecting "+Demand".
Enter the desired settings for the tag as usual, and set the tag Demand Class to Header Bidding
Once this demand class is selected, a few new options will appear. These are:
Platform
Select the platform this header bidding tag belongs to. This will reveal the bid parameters specific to that platform, as well as an icon next to platform indicating which integration types are supported (i.e. client-side and/or server-side). More information on integrating tags from these platforms can be found in the "Supported Platforms" section below.
Floor Type
Choose which type of floor will be applied to the bids coming through this tag. A Static floor is a fixed rate that SpringServe will use to ignore any bids that fall below the entered value.
NOTE: Depending on the demand partner, this floor may not be the same as the floor entered in the bidder's platform. See "Supported Platforms" for more information on what to enter for each partner.
A Dynamic margin will adjust the floor value depending on the rate of the supply tag (e.g. a 20% dynamic margin on a $10 supply tag will submit a floor of $12).
NOTE: A demand partner with a dynamic margin running on a supply tag with revshare or dynamic payment terms will set the submitted floor to $0.01.
Floor Rate/Margin
The static value or margin to calculate when SpringServe submits the floor in the header bidding request.
Tier Breakout
All demand can now compete with a better chance for monetization even when direct-sold campaigns sit at a higher tier than programmatic demand. Tier breakout allows you to set a secondary floor for programmatic demand. When a bid comes back at or above the breakout bid value, it competes in first look regardless of the tier set on the demand tag.
To report on the number of times an impression has served at or above the breakout bid, run a report including the "Breakout Imps" metric.
Bid Parameters
The platform-specific id(s) that connect this demand tag with the header bidding partner's tag. This can usually be found in the endpoint of the partner's tag (for more details, reference "Supported Platforms").
Adding Header Bidding Demand Tags to Supply Tags
Connecting header bidding tags to supply follows the standard process in SpringServe.
Either navigate to the Supply Tags tab on the header bidding demand tag to Add Manually or Copy From Demand
Or once the demand tag has been created, add it from the Demand Tags tab on the desired supply tag:
Adding header bidding demand tags will enable BroadFall on the targeted supply.
NOTE: Header bidding demand tags must be inside a broadcast-enabled tier and cannot serve on Flash or VPAID None supply.
Supported Platforms
33Across
Supported Integrations: Client Side
To add a 33Across header bidding demand tag, select 33Across from the Platform drop-down.
Once the floor has been set, input the Site ID.
Select an option from the Product ID dropdown.
AMX (AdaptMX)
Supported Integrations: Server Side
To add an AMX header bidding demand tag, select AMX from the Platform drop-down.
Once the floor has been set, input the Tag ID and Ad Unit ID
AdYouLike
Supported Integrations: Client Side
To add an AdYouLike header bidding demand tag, select AdYouLike from the Platform drop-down.
Once the floor has been set, input the Placement ID.
Amazon
Supported Integrations: Server Side
To add an Amazon header bidding demand tag, select Amazon from the Platform drop-down.
Creating a Bid Map
You can add an Amazon HB bid map under the Settings in your account
Then Click + HB Bid Map to make a new bid map.
Select Amazon as the Platform, select the bid map type, and upload a csv of your bid map. Then hit Apply.
A user can make as many bid maps as they need. Typically, most clients will want a bid map for their inventory share and a separate one for their paid demand. However, if you want to make additional bid maps to split out higher paying demand, you can do that as well.
You can see entries on the Entries Tab.
Example Bid Map CSV:
The CSV’s do not need column names.
The left column is the bid price and the right column needs to be the bid map.
Inventory share bid map example
Paid Bid Map Example
Once the floor has been set, select the HB Bid Map that was created, and input the PS Policy ID
* Frequency capping unique to Amazon:
Amazon bids are retrieved from a cache via key values that are passed in the supply tag request. To prevent these cache urls from getting called more than once, Springserve performs a check against the Amazon Impression URL including a lookup of these key values, making sure it is unique before making the request. if it is not unique then we do not call the same Amazon Cache URL again.
amznregion={{AMZNREGION}}
amznbrmId={{AMZNBRMID}}
ps={{AMZNSLOTS}}
Audience Media TV
Supported Integrations: Client Side and Server Side
To add an Audience Media TV header bidding demand tag, select Audience Media TV from the Platform drop-down.
Once the floor has been set, input the Member ID and Placement ID.
(Optional) Select an option from the Use Payment Rule.
Beachfront SSP
Supported Integrations: Client Side and Server Side
To add a Beachfront SSP header bidding demand tag, select Beachfront SSP from the Platform drop-down.
Once the floor has been set, input the App ID.
Beachfront Unified Decisioning
Supported Integrations: Server Side
To add a Beachfront Unified Decisioning header bidding demand tag, select Beachfront Unified Decisioning from the Platform drop-down.
Once the floor has been set, input the Ad Pod ID.
BrealTime (EMX Legacy)
Supported Integrations: Client Side
To add a BrealTime header bidding demand tag, select Brealtime from the Platform drop-down.
Once the floor has been set, input the Member ID and Placement ID.
(Optional) Select an option from the Use Payment Rule.
NOTE: bRealTime's header bidding integration is done through Xandr, so the optional bid parameters used in the Xandr platform can be used here as well.
Chocolate Platform
Supported Integrations: Server Side
To add a Chocolate Platform header bidding demand tag, select Chocolate Platform from the Platform drop-down.
Once the floor has been set, input the Pub Identifier.
Conversant
Supported Integrations: Client Side
To add a Conversant header bidding demand tag, select Conversant from the Platform drop-down.
Once the floor has been set, input the Site ID.
Criteo
Supported Integrations: Server Side
To add a Criteo header bidding demand tag, select Bidder: DSP and select Criteo from the Platform drop-down.
Once the floor has been set, input the Required Publisher ID, Network ID. Ad Unit ID is optional.
Criteo Required and Optional Parameters
See https://publisherdocs.criteotilt.com/cdbssai/#bid-request for complete details and best practices.
Object | Required Parameters |
|---|---|
App/Site |
|
Imp |
|
DMX
Supported Integrations: Server Side
To add a DMX header bidding demand tag, select DMX from the Platform drop-down.
Once the floor has been set, input the Tag ID and Publisher ID.
Digital Remedy
Supported Integrations: Client Side and Server Side
To add a Digital Remedy header bidding demand tag, select Digital Remedy from the Platform drop-down.
Once the floor has been set, input the Member ID and Placement ID.
(Optional) Select an option from the Use Payment Rule.
Elemental TV DSP
Supported Integrations: Server Side
To add an Elemental TV DSP header bidding demand tag, select Elemental TV DSP from the Platform drop-down.
Once the floor has been set, input the Ad Unit.
Equativ (Legacy Smart Ad Server)
Supported Integrations: Client Side and Server Side
To add a Equativ header bidding demand tag, select Equativ from the Platform drop-down.
Once the floor has been set, input the Site ID, Page ID and Format ID.
(Optional) Input Network ID.
Facebook Audience Network (Beta)
Supported Integrations: Client Side
To add a Facebook Audience Network header bidding demand tag, select Facebook Audience Network from the Platform drop-down.
Once the floor has been set, input the Placement ID.
Freewheel (Sticky Ads)
Supported Integrations: Client Side and Server Side
To add a Freewheel header bidding demand tag, select FreeWheel from the Platform drop-down.
Once the floor has been set, input the Zone ID.
Glewed
Supported Integrations: Server Side
To add a Glewed header bidding demand tag, select Glewed from the Platform drop-down.
Once the floor has been set, input the Deal ID.
GumGum
Supported Integrations: Server Side
To add a GumGum header bidding demand tag, select GumGum from the Platform drop-down.
Once the floor has been set, input the Zone.
(Optional) Select an option from the Linearity.
Improve Digital
Supported Integrations: Client Side and Server Side
To add an Improve Digital header bidding demand tag, select Improve Digital from the Platform drop-down.
Once the floor has been set, input the Placement ID and Publisher ID.
InMobi
Supported Integrations: Client Side
To add a InMobi header bidding demand tag, select InMobi from the Platform drop-down.
Once the floor has been set, input the Placement ID.
Index Exchange
Supported Integrations: Client Side and Server Side
To add an Index Exchange header bidding demand tag, select Index Exchange from the Platform drop-down.
Once the floor has been set, input the SiteId.
Select playback method and video placement type.
(Optional Params): eids and multi_imp_enabled
NOTE: Please check with your Index Exchange account representative to make sure that header bidding is enabled on their end.
Index Exchange Required and Optional Parameters
See the Index Exchange Knowledge Base for complete details and best practices. Note: If you require a login to see the Index Knowledge Base, contact your Index Representative.
Object | Required parameters | Recommended parameters |
|---|---|---|
App |
| Note: Index requires that all CTV publishers pass a bundle ID for each application. If your CTV application does not have a bundle ID, see the IAB's OTT/CTV Store Assigned App Identification Guidelines.
|
Device |
|
|
Video |
|
|
Content |
|
|
Kargo
Supported Integrations: Server Side
To add a Kargo header bidding demand tag, select Kargo from the Platform drop-down.
Once the floor has been set, input the Placement ID and Publisher ID.
Legacy VGI CTV
Supported Integrations: Client Side and Server Side
To add a Legacy VGI CTV header bidding demand tag, select Legacy VGI CTV from the Platform drop-down.
Once the floor has been set, input the Publisher ID and Site ID.
Select an option from the Output Format.
Magnite DV+
Supported Integrations: Client Side and Server Side
To add a Magnite DV+ header bidding demand tag, select Magnite DV+ from the Platform drop-down.
Once the floor has been set, input the Account ID, Site ID, and Zone ID.
Select an option from the Size ID.
Magnite Streaming
Supported Integrations: Server Side
To add a Magnite Streaming header bidding demand tag, select Magnite Streaming from the Platform drop-down.
Once the floor has been set, input the Ad Code.
Select: Respect External Tier
Magnite: Telaria
Supported Integrations: Client Side
To add a Magnite: Telaria header bidding demand tag, select Magnite: Telaria from the Platform drop-down.
Once the floor has been set, input the Supply Code/Seat Code and Ad Code.
NoBid
Supported Integrations: Server Side
To add a NoBid header bidding demand tag, select NoBid from the Platform drop-down.
Once the floor has been set, input the Publisher ID.
OneTag
Supported Integrations: Client Side and Server Side
To add a OneTag header bidding demand tag, select OneTag from the Platform drop-down.
Once the floor has been set, input the Pub ID.
OpenX
Supported Integrations: Client Side and Server Side
To add an OpenX header bidding demand tag, select OpenX from the Platform drop-down.
Once the floor is set, input the Delivery Domain and the Ad Unit ID into their respective fields in "Bid Parameters".
NOTE: Please check with your OpenX account representative to make sure that header bidding is enabled on this ad unit.
The delivery domain and ad unit id can usually be found in the OpenX endpoint, with the ad unit id identified by the auid= parameter – e.g. https://testing-d.openx.net/v/1.0/av?auid=987654&cb={{CACHEBUSTER}}&url={{URL}}&vwd={{WIDTH}}&vht={{HEIGHT}}&c.size=small
Opera Ads
Supported Integrations: Client Side
To add an Opera Ads header bidding demand tag, select Opera Ads from the Platform drop-down.
Once the floor has been set, input the Placement ID, Publisher ID, and Endpoint ID.
Origin Media
Supported Integrations: Server Side
To add an Origin Media header bidding demand tag, select Origin Media from the Platform drop-down.
Once the floor has been set, input the Ad Unit.
PubMatic
Supported Integrations: Client Side and Server Side
To add a PubMatic header bidding demand tag, select Pubmatic from the Platform drop-down.
Once the floor has been set, input the Publisher ID, Ad Slot, Video Placement Type(IAB) and select the linearity.
(Optional) Select an option from the VPOS(startdelay) and Skippable
PulsePoint
Supported Integrations: Client Side and Server Side
To add a PulsePoint header bidding demand tag, select PulsePoint from the Platform drop-down.
Once the floor has been set, input the Publisher ID, Tag ID, and Video Placement Type(IAB).
Rise (Legacy Iron Source)
Supported Integrations: Client Side
To add a Rise header bidding demand tag, select Rise from the Platform drop-down.
Once the floor has been set, input the Rise Publisher ID
(Optional) Input the Placement Id, and RTB Domain.
Roku
Supported Integrations: Server Side
To add a Roku header bidding demand tag, select Roku from the Platform drop-down.
Once the floor has been set, input the Roku Domain, Seat ID, Tag ID, and HB Bid Map.
For HB Bid Map, use same instruction as described for Amazon.
Samsung and Samsung Staging
Supported Integrations: Server Side
To add a Samsung header bidding demand tag, select Samsung from the Platform drop-down.
Once the floor has been set, input the Samsung App ID and Samsung HB Tag.
Sharethrough
Supported Integrations: Server Side
To add a Sharethrough header bidding demand tag, select Sharethrough from the Platform drop-down.
Once the floor has been set, input the Publisher ID.
Smaato
Supported Integrations: Server Side
To add a Smaato header bidding demand tag, select Smaato from the Platform drop-down.
Once the floor has been set, input the Publisher ID and Ad Space ID.
Smartclip
Supported Integrations: Server Side
To add a Smartclip header bidding demand tag, select Smartclip from the Platform drop-down.
Once the floor has been set, input the Pub ID and Site ID.
Sonobi
Supported Integrations: Client Side and Server Side
To add a Sonobi header bidding demand tag, select Sonobi from the Platform drop-down.
Once the floor has been set, input the Placement ID.
Stroeer
Supported Integrations: Client and Server Side
To add a Stroeer header bidding demand tag, select Stroeer from the Platform drop-down.
Once the floor has been set, input the Tag Id.
Synacor
Supported Integrations: Client Side and Server Side
To add a Synacor header bidding demand tag, select Synacor from the Platform drop-down.
Once the floor has been set, input the Contango Section ID/Tag ID.
(Optional) Input the Seat ID.
TappX
Supported Integrations: Server Side
To add a TappX header bidding demand tag, select TappX from the Platform drop-down.
Once the floor has been set, input the TappX Key, Endpoint, and Host.
(Optional) Input the mktag.
Teads
Supported Integrations: Server Side
To add a Teads header bidding demand tag, select Teads from the Platform drop-down.
Once the floor has been set, input the Placement ID.
TheMediaGrid
Supported Integrations: Client Side and Server Side
To add a TheMediaGrid header bidding demand tag, select TheMediaGrid from the Platform drop-down.
Once the floor has been set, input the Ad Unit ID.
TheViewPoint
Supported Integrations: Server Side
To add a TheViewPoint header bidding demand tag, select TheViewPoint from the Platform drop-down.
Once the floor has been set, input the Account ID and Placement ID.
TripleLift
Supported Integrations: Client Side and Server Side
To add a TripleLift header bidding demand tag, select TripleLift from the Platform drop-down.