Summer Time with SpringServe

Core Improvements

Custom Time Zones

Users have long been able to see performance graphs and quickstats tables throughout the SpringServe UI. Until now, these graphs and stats were always shown in US Eastern time. We have released custom time zones for accounts and individual users. To change the account time zone, go to Settings –> Account Settings. At the bottom of the second column is a dropdown to select the account time zone. This time zone will apply to any new admin or ad ops user.

Existing users can also change their time zone by selecting Edit Profile from the menu under the user icon. In the third column, select your desired time zone from the dropdown. Time zones are listed in order by number of hours offset from UTC. Make sure to save to apply your custom time zone.

The default time zone is US Eastern time. All charts and tables in dashboards and quickstats will be shown in the time zone of your user. Additionally, the default time zone in the reporting UI will reflect your time zone settings.

Feature Additions

Give Up

SpringServe has released Give Up, an optimization feature that deprioritizes poorly performing demand in a waterfall. For a demand tag to enter Give Up, it must have 120K requests in the waterfall and a fill rate below 0.05% over the last 24 hours. When placed in Give Up, requests are throttled to the demand tag and allocated to tags with a historically higher fill rate. A demand tag can exit Give Up if its performance improves or if the request threshold is no longer met. Initial tests have shown an improvement in performance of up to 2%.

Tags that have entered Give Up have a tooltip next to the checkbox and italicized text.

Targeting Updates

Account level geo targeting is now available in the Basic Settings of your account. Requests from these countries will be blocked across all your SpringServe supply.

SpringServe player size targeting is based on the player width. With the release of aspect ratio targeting, you can specify a desired range of aspect ratios. This feature allows blocking of display sizes such as 728 x 90. To use aspect ratio, select Custom and choose a minimum and maximum ratio.

Aspect ratio is calculated as width/height, so a square player has an aspect ratio of 1.0, a tall and skinny player has a smaller aspect ratio, and a long and skinny player has a higher aspect ratio. The green rectangle shows the approximate shape of a player of the selected ratio.

UI/UX Improvements

Quickstats Summary Updates

Budget values are now shown above the budget bar in the quickstats summary.

With this update, you no longer need to navigate to the targeting tab to confirm the budget value.

We have increased the maximum frequency cap value from 10 to 50. Frequency capping is available for supply tags, demand partners, campaigns, and demand tags.

Reporting Improvements

VAST Error Code Reporting

Run a VAST Error Code report by selecting VAST Error Code in the dimensions. These reports return the number of errors and timeouts. In addition to standard VAST Error Codes, SpringServe shows custom 13xx and 15xx error codes, which would otherwise be grouped into a more general error code such as 901. For more details on VAST Error Codes, please see our wiki.

Dimension & Metric Additions

Data for first and third quartiles is now available in reporting. Select 25% Completes and 75% Completes from the Quality Metrics section in the reporting UI.

Operating Systems are now available in reporting dimensions and filters.


Waterfall Clean Up

SpringServe is implementing a new policy to automatically remove old demand tags from waterfalls. If a demand tag has been on a waterfall for at least 90 days and has zero requests in the last 90 days, it will be removed from the waterfall. This policy will increase UI speed on the waterfall page and help automate the clean up of old tags in your account. If you have any questions or concerns about waterfall clean up, please contact your account manager.

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, {{ACCOUNT_ID}}, DIRECT, a24eb641fc82e93d

Resellers, {{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 *