Header Bidding through BroadFall and More

Feature Additions

Header Bidding through BroadFall


With a traditional waterfall, an ad request will passed to each tag in priority order. SpringServe is excited to announce BroadFall, a new call logic which allows for both a broadcast call and a traditional waterfall. With BroadFall, you can add tags to a broadcast tier. These tags will be called first using an asynchronous call, and if they do not return an impression, the request moves down to the traditional waterfall. BroadFall gives you a higher degree of control of your demand stack, and alpha testing has shown decreased latency and increased fill.

When BroadFall is enabled, demand tags can be added to or removed from the broadcast tier by clicking the broadcast icon. Note that BroadFall is supported on SpringServe’s JS VPAID. For supply tags that return VPAID Both, BroadFall will only work if the JS VPAID is selected.

Video Header Bidding Demand

We have also released a new type of demand tag in SpringServe: Header Bidding. With Header Bidding demand tags, SpringServe integrates directly with external platforms and initializes the auction from the VPAID. Simply select Header Bidding from the Type dropdown on the settings tab of a managed demand tag. Fields will appear for Platform, Floor Type, and Floor Rate.

Fields for required Bid Parameters will appear based on the platform selected.

Aligning Header Bidding demand to supply is done in the same manner as other demand tags in SpringServe – simply use the +Supply or +Demand modal. When aligning Header Bidding demand tags to supply, they will be placed in the broadcast tier of a BroadFall.

Because BroadFall operates through SpringServe’s JS VPAID, Header Bidding demand tags will not appear in the add demand modal on a Flash VPAID or a VPAID none supply tag. If a tag is VPAID Both, Header Bidding and BroadFall will work if the JS VPAID is selected by the player. If the Flash VPAID is selected, no asynchronous call will be made, the broadcast tier will be skipped and the request will go through the traditional waterfall.

For more information on Header Bidding through Broadfall, see our official press release and this blog post from SpringServe General Manager Josh Cohen.

Please see our wiki for additional details on Header Bidding implementation and best practices. If you are interested in beta testing Header Bidding through BroadFall, please contact your account manager or email info@springserve.com.

Bulk Actions

Bulk actions are now available throughout the SpringServe UI. You now have the ability to select multiple objects and easily change their status. Click the checkbox in the first column of a table to select an object and the Bulk Actions menu will be enabled.

You can also click the checkbox in the header to select all objects on the current page. This option is available for your supply tags, demand tags, campaigns, domain lists, and user accounts.

On the waterfall tab of a supply tag, you can do a bulk remove of demand tags. You can also change the tier and priority for multiple tags at once.

With this update, we have removed the ability to toggle between Flat and Tiered waterfalls. Demand tags will be added at priority 1 in the default tier of their demand partner.

Core Improvements

We have added the ability to set multiple KPI goals on a campaign. You can select the desired logic for your KPI targeting. Adding a metric within a group will target KPI 1 AND KPI 2. In the example below, the goal is over 50% Moat Viewability and under 5% WhiteOps IVT.

Adding another group will target group 1 KPI(s) or group 2 KPI(s). In the example below, the goal is over 90% Moat Viewability or over 70% Moat Group M Viewability.

UI Improvements

Visualizing Targeting

In your SpringServe waterfalls, a demand tag will not be eligible for selection if the request does not pass targeting. Targeting icons are shown throughout the platform and allow you to assess your targeting at a glance.

We have split out the icon for player size targeting, which was previously included with Device and OS. We have also added a targeting icon for campaign KPI goals. These updates make it easier to see why a demand tag might be getting fewer requests than expected. If you have IVT enabled filtering or detection enabled for your tags, the shield icon is also shown in the targeting column.

A request must pass targeting on all levels: partner, campaign, and tag. We have therefore added visibility into the targeting at different levels on the targeting tab of a demand tag and campaign. Teal icons indicate that targeting is in place and hovering over the icon will show a tooltip with more details. In the example below, there is a budget or flight dates on the partner level and domain list and KPI targeting on the campaign level.

Domain Lists

We have updated the styling on domain lists to allow for less navigation around the page. This new style allows you to skip the scrolling when you add domains. You also now have the ability to apply changes to a domain list without exiting the page.

More UX Improvements

When duplicating an object, the name field automatically fills in with “old_object_name (copy)” so you can keep track of what has been duplicated.

If you want to keep tighter control over the supply/demand alignment for a tag, you may want to disable supply or demand side edits. When demand side edits are disabled, changes to the waterfall of a supply tag must be done from its demand tags tab – it cannot be added to demand using the add supply modal. The supply side edits setting has been moved to the setting tab on a demand tag; likewise for the demand side edits setting on a supply tag.

In the add demand modal, we have added a filter for demand type so you can properly align your tags. Note that Demand Type is a label that is set by the user. In the add supply modal, you can now enter a minimum as well as the maximum rate to filter your supply tags. These updates allow you to spend less time appropriately aligning supply and demand.

Reporting Improvements

We have added “Last 30 Days” to the Date Range dropdown on the main reporting page. Domain dimensions are available for this period when the Time Zone is set to UTC.

If you have users that are Demand Clients, they can see reporting for their demand tags in your account. They also now have access to Campaign reporting.

Asynchronous API requests are sortable and have page counts.

Bug Fixes

When a supply tag is duplicated, custom environment settings now preserved.

Campaigns are now deleted when the parent partner is deleted.

Recently added features are now available in the changelog for KPI goals on campaigns, applying labels to tags, and enabling demand for broadcast in a waterfall.


SpringServe in ads.txt

SpringServe fully supports the IAB’s ads.txt initiative and its goal of increasing industry-wide transparency between buyers and sellers. With increasing adoption of the ads.txt initiative by a number of buying and selling platforms, we encourage all SpringServe clients to implement ads.txt on their domains and any domains with whom they work.

We have included instructions about how to add SpringServe to an ads.txt file below:

Owned and Operated Domains
springserve.com, {{ACCOUNT_ID}}, DIRECT, a24eb641fc82e93d

springserve.com, {{ACCOUNT_ID}}, RESELLER, a24eb641fc82e93d

Replace {{ACCOUNT_ID}} with your SpringServe Account ID; this ID can be found in the lower right hand corner of the browser when you are logged into your SpringServe account. In the example below, CrushTown USA has Account ID 17.

Leave a Reply

Your email address will not be published. Required fields are marked *