In our latest release, we discuss multi-tier BroadFall, account blacklists, UI improvements, reporting additions, and GDPR.
Core Improvements
Multi-Tier BroadFall
With SpringServe’s BroadFall logic, you are able to combine a asynchronous broadcast call and a traditional waterfall. Previously, a single tier at the top of the waterfall was eligible for broadcast. The first tier in the waterfall has been renamed from Broadcast to First Look; the First Look tier is enabled for broadcast by default, but you have the option to disable broadcast for this tier. Select 1L as the tier to put demand in the First Look tier.
We have updated BroadFall to allow for multiple broadcast tiers within the waterfall, giving you more control. With this update, you can set any of your tiers to broadcast by clicking the broadcast icon to the left of the tier name. You can disable BroadFall entirely if broadcast is not enabled on any tier. Alternatively, if each tier is set to broadcast, you can have up to six broadcast tiers in a waterfall. Note that each broadcast tier has a limit of 10 active tags. Contact your account manager if you need this limit increased.
By default, header bidding demand will be added to the First Look tier of a waterfall, but you can move this demand to a different tier if desired. You may want to do this if you have a direct campaign that you want to give the first chance to buy specific supply. Any tier that has header bidding demand will automatically be enabled for broadcast, so if you want to disable a tier for broadcast, remove any header bidding tags first.
We recommend taking advantage the Bulk Action option to Change Tier if you want to make changes to large numbers of tags in your waterfall.
Note that multi-tier broadcast is available for managed supply tags only. The First Look tier in DC supply is reserved for header bidding demand.
Multi-Device Support
We continue to improve our user experience for your multi-device business. We have made updates to our User Agent Targeting options for both the supply and demand tags. Device Targeting now has an option for Smart TV which includes Apple TV, Roku, Amazon Fire Stick, Google Chromecast, game consoles, and internet-ready televisions. We have also added more options to Operating System (OS) targeting for even more control over desired inventory.
New Mobile Macros
We have added support for device make and device model macros. Device make shows the manufacturer of the device, such as Apple or Samsung; this information is passed to SpringServe through device_make={{DEVICE_MAKE}}. Device model shows the specific product such as iPhone 8 or Galaxy S9; this information is passed to SpringServe through device_model={{DEVICE_MODEL}}. The device make and device model macros – along with the did, app_name, and app_bundle – will automatically be included in the export tag when in-app or CTV is selected as the environment. Including these macros on the export tag allows the information to be passed to the demand stack.
We have also updated our suggested macros feature for a managed demand tags. Based on the selected environment, we will show additional macros that may be required to get a non-empty VAST response from your demand partner. In the example below, In-App is selected as the environment and the endpoint url does not include a number of relevant macros, these query string parameters and macros are appended to the endpoint URL in the Suggested Macros box.
Smart Selection of Frequency Capping Method
Frequency capping is available for supply and demand objects in SpringServe. The appropriate frequency capping method varies with environment. You no longer have to worry about setting the correct method because we have taken the guesswork out of the equation. Based on the environment of the inventory, SpringServe will know whether to use cookies (desktop and mobile web) or device ID (in-app and CTV). If cookies or device id is not available, IP address will be used as a fallback.
Expanded Open RTB Support
OpenRTB demand can now be included in your in-app and CTV demand stacks. If you are interested in connecting with OpenRTB partners, contact your account manager.
Feature Additions
Account Blacklists
We have expanded account targeting support for your SpringServe account. On the Basic Settings page, you can now apply domain, app name, and app bundle blacklists on the account level.
All desktop and mobile web requests must pass the account domain blacklist targeting. All in-app and CTV requests must pass the account app name and/or bundle blacklist targeting. Account blacklists can be created like any other domain or app list by going to the appropriate page under the Targeting menu.
Optional Header Bidding Parameters
Some header bidding platforms may have optional parameters that will improve performance if passed. You now have the ability to add optional parameters to your header bidding demand. Clicking the +New Optional Parameter button will reveal a dropdown with platform-specific optional parameters.
Supply Tag Budgets and Frequency Caps
You now have the ability to add budgets and frequency caps to your supply tags.
UI Improvements
Range Compare and Quickstats Graphs Updates
You can now see Range Compare in the Account Activity summary tiles. These figures show the percent change from yesterday at this time to today at this time. Positive changes are shown in green and negative changes are shown in red.
Quickstats Graphs now update with the time range selected. In the example below, the first graph appears when Today is selected and the second graph appears when Last 24 Hours is selected.
Changelog flags also now show the user who made the change. These flags are shown on the minute quickstats graphs. The flag now shows either the user’s initials or the first letter of their email address, so you can get a quick picture of who has been making changes and what the impact has been.
Editing Domain and App Lists
Domain and App Lists can now be edited more easily. You no longer need to upload a csv to remove domains/app names/app bundles from a list. The Manual text box can be used to remove entries from a list. In the example below, 411.com will be removed from the list.
This update is especially useful for removing a few domains that are not visible in the Included Domains box because there are over 500 entries on the list. There is no need to create a csv with a couple lines in order to remove them, or to download the current list, edit it, and replace it.
Demand Index Improvements
Opportunities and Opportunity Fill Rates are now shown on the Demand Partner and Campaign index pages. Toggle to the Full view of the table to see these metrics.
Demand Class has also been added as a filter to all demand tables. This filter helps you quickly find specific demand.
Targeting icons show you object targeting at-a-glance when looking at index pages. The most used targeting icons (IVT, lists, geo, size, budget) are now shown in the light view, while you are always able to see all targeting icons in the full view. This change allows you to analyze more metrics without scrolling when looking at the lite view.
Reporting Improvements
Time Intervals
By popular request, we have added two options to the time intervals: last 24 hours and last 30 days. These options allow you to better track the impact of recent changes made by your ad ops team and general trends in performance. Reports can also now be run using a quarterly interval.
Dimensions & Filters
You now have the ability to use a partial search for domain and app reports; feature is available for declared domain, detected domain, app name, and app bundle filters.
Unchecking the Exact Match box allows for fuzzy search. This is especially useful when running app reports. For example, filtering app name for soccer and unchecking Exact Match will run a report for any app that has soccer in the name, so you do not need to know the exact name of an app to get useful data.
This partial search goes hand in hand with Match logic on App Name and Bundle lists. When setting up an app list, you can specify whether to use exact or partial match on the settings tab of the list.
We have also added dimensions and filters for Supply Tag CPM and Demand Tag RPM. When adding the CPM or RPM to the dimensions of your report, the current rate will be shown. In the filters, you can select a minimum and maximum to search a range of CPM/RPMs.
Share Reports
Sharing Reports in SpringServe can be done in a number of ways:
- Download the report and send the downloaded csv
- Copy/paste the reporting page url and hit Run Report
- Schedule a report to be emailed to other SpringServe clients
- Use the Share Report Link.
The Share Report icon is found to the right of the schedule report button.
Clicking this button will open a modal containing a link that can be copied and sent out. This link is valid for 7 days and allows you to share a report with a non-SpringServe user, or someone who is not logged into their SpringServe account. The report will be saved on the Download Reports page, so add a name to the report to make it easy to find in the future.
Always use care when sharing reports, as anyone with the link may access the report without signing into SpringServe.
Alerts
GDPR
SpringServe is preparing for the GDPR deadline of May 25th, 2018. If you are a client or partner please be sure that you have filled out our consent form HERE in regards to the European Unions General Data Protection Regulation (GDPR)
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
Resellers
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
Comments are closed.