Feeling Lucky with SpringServe

In our latest release, we discuss updates to Header Bidding and improvements to the UI including updated targeting icons, demand class, and easier association of supply and demand.

Core Improvements

Header Bidding

We continue to improve on Header Bidding demand tags in SpringServe. Index Exchange has been added as a beta platform. We have added more optional parameters, and the ability to search for your header bidding demand tags by entering parameters in the search bar on the demand tags tab.

UI Improvements

New Targeting Icons

In SpringServe, you have the ability to apply targeting on multiple levels: tag, partner, and – in the case of demand – campaign. A request must meet criteria on all levels in order to pass targeting.

We have improved the appearance of targeting icons to make it easier to determine applied targeting at a glance. All applicable targeting icons are shown in the full view of the index table. If an object is targeting a given criteria, the icon will appear in teal. If a parent object is targeting a given criteria, the icon will appear in dark grey. A popover describing applied targeting will appear when hovering over an icon.

Demand Class

On the settings tab of a demand tag, we have the Demand Class pillbox. This redesign makes it easier to create Header Bidding and Creative Asset, or Direct MP4 tags.

When Tag is selected, you will be able to select the VPAID type and enter an Endpoint URL as before. Selecting Header Bidding will allow you to select the platform and enter Header Bidding parameters. When Creative Asset is selected, you can upload a video file or enter the URL of a hosted creative.

Supply Updates

Supply labels and environment filters have been added to the supply tags index page, making it easier to find specific supply tags. You can also see the number of demand tags in the broadcast tier when looking at the full view of the supply tag index page.

We have disabled detected targeting and post-impression detection for VPAID none supply tags in the UI. Because detection of the domain and player size is done by the VPAID, the detected domain and size is always unknown on VPAID none tags. Likewise, post-impression detection can occur when JS can be initialized in the player and therefore it is not possible to implement on VPAID none tags. For DirectConnect supply tags that are targeting CTV, these options are also disabled because CTV inventory is always VPAID none.

In the waterfall tab, dynamically priced Open RTB tags now show the actual RPM in the Rate column; the floor rate is shown in parentheses.

Improvements to Associating Supply and Demand

We are constantly working to improve the user experience in SpringServe. Therefore we have made some updates that should make associating supply and demand a faster and easier process for your ad ops team.

When associating supply to demand, you can now search by pasting a comma-separated list of ids in the search bar of the modal.

We have also added the ability to copy demand from an existing supply tag. With this addition, you can get started with waterfalls that have proven to perform well when setting up a new supply tag.

Reporting Metrics

We have improved the design of the metrics section of the reporting page. Both the add all and remove all links appear for each group of metrics. Additionally, only metrics that are compatible with the selected dimensions will be shown. For example, if you are running a Demand Tag report, the supply-specific metrics of Total Calls, Billable Requests, Blocked Requests, Missed Opps, and Player Loads will not be shown.

2-Factor Authentication

If you have enabled your account for 2FA, you can now opt in to remembering your device for 30 days. SpringServe will only require your authentication code after 30 days have passed. Note that clearing your cookies or using a different browser will result in a request for your 2FA code.


Traffic Quality Reports

Moat data is no longer available on the Traffic Quality Report page. However, you can still access these metrics in the IVT and Quality sections on the main reporting page.

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.

Bug Fixes

Various bug fixes and performance improvements



Leave a Reply

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