Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Enter this placement id in its respective field in SpringServe.

Beachfront

To add a Beachfront header bidding demand tag, select Beachfront from the Platform drop-down.

Once the floor has been set, input the App ID.

Conversant

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.

bRealTime

To add a bRealTime header bidding demand tag, select bRealtime from the Platform drop-down.

Once the floor is has been set, input the Placement ID.

...

NOTE: Similar to bRealTime, district m's integration is done through AppNexus, so the optional bid params for AppNexus can potentially be applied here.

Index Exchange

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.

NOTE: Please check with your Index Exchange account representative to make sure that header bidding is enabled on their end.

OpenX

To add an OpenX header bidding demand tag, select OpenX from the Platform drop-down. 

...

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

PubMatic

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, and select the linearity.

Rubicon

To add a Rubicon header bidding demand tag, select Rubicon from the Platform drop-down. Once Rubicon has been selected, set the floor do its desired type and value.

...

Once these ids are retrieved, input them into their respective fields in SpringServe.

Vuble

To add a Vuble header bidding demand tag, select Vuble from the Platform drop-down.

Once the floor has been set, input the Publisher ID, Zone ID, and select the Environment and Context.

Yield Nexus

To add a Yield Nexus header bidding demand tag, select Yield Nexus from the Platform drop-down.

Once the floor has been set, input the SPID and set the "Is An Interstitial" flag. 

Optional Parameters

SpringServe offers publishers the ability to pass additional parameters on header bidding demand tags for certain platforms. If optional params are available for that platform, you should see a place to add them in the "Bid Parameters" section of the demand tag settings. Simply click "+Optional Parameter" to add a new parameter.  Clicking this button will allow you to choose from a drop-down of keys, with a field for the values to the right. These params will be different depending on the platform that is selected. 

...

NOTE: Similar to AppNexus "keywords", the SpotX "custom" parameter is where custom key-value pairs should be inputted, separated by ampersands.



Removing Fees for Bidders Returning Gross Prices

Some bidders will return bid prices that are gross to the seller, meaning that the bidder's fee(s) have not been taken out of the bid price. This is problematic because it has the potential to give those bidders an unfair advantage over others that return net bids, and it can cause issues for rev share/dynamic supply tags that rely on an accurate revenue number to calculate cost. 

In order to solve for such bidders, SpringServe has the option on the Demand Partner or the Campaign to remove a fee % directly from the bid price. This will allow SpringServe to net out the bids from such bidders and report on this net amount as opposed to the gross value.

Image Added

NOTE: Enabling this option means that the fee is taken out of the revenue in reporting instead of being logged as a third party fee.