Raking it in with SpringServe

In our latest release, we discuss the addition of Forensiq as a verification vendor in SpringServe. We also discuss additions to targeting options, including boolean user segment targeting. We have also updated key-value reporting to make it easier to filter specific values for a given key.

Core Improvements

Forensiq

We have added integration with Forensiq as another tool to combat IVT. With this integration, users have access to IVT detection for in-app inventory. Find Forensiq in post-imp IVT components on both supply and demand, along with WhiteOps, Moat, and IAS. To include Foresiq on new tags by default, specify the sampling rate for IAS on the Default Settings tab of your SpringServe settings .

Forensiq reporting data is available in the IVT Metrics section of the reporting UI. Select from the following metrics: Forensiq Imps, Forensiq IVT Imps, and Forensiq IVT %.

User Timezone Dayparting

You can now opt to use the end user’s timezone for daypart targeting. In the Daypart Logic modal, select User or Eastern Timezone. Note that the user timezone is based on the declared IP address location. This option would prove useful if you want to target business hours.

Feature Additions

User Segment Targeting

SpringServe users can now implement boolean User Segment targeting by using device ID lists. On the targeting tab of your SpringServe objects, User Segment targeting can be found in the third column. Like key values and custom tag health, user segment targeting uses groups. Within a group, all criteria must be met. In the example below, a request would pass targeting if it is from a rock climbing soccer dad who is not a college graduate.

Note that the device ID must be on all whitelists (both the Soccer Dads and Rock Climbing list), and must not by on any of the blacklists (not from the college graduates list).

If you add a User Segment Group, a request will pass targeting if it passes for either the group 1 criteria, or the group 2 criteria. In the example below, a request would pass targeting if it is from a rock climbing soccer dad who is not a college graduate, or if it is from a florist.

Frequency Capping

You now have more flexibility when specifying frequency caps. For example, you can now specify 1 impression per user per 12 hours. Changing the numbers in the frequency cap section of the targeting tab will update the description.

Header Bidding Tier

Previously, Header Bidding tags would always be placed in tier 1L by default. You now have the option to have Header Bidding tags respect the default tier of their partner. In the Waterfall Options section of the Settings tab of a demand partner, you can set Header Bidding Default Tier to either First Look or the Partner Default.

Note that DC supply only allows Header Bidding tags in the first look tier.

IAS KPI Targeting metrics

IAS metrics have been added to KPI targeting. IAS metrics include IAS MRC Viewability Rate, IAS GroupM Viewability Rate, and IAS IVT rate.

UI Improvements

Quickstats Graphs

The graph view of quickstats summaries show a visual representation of performance, financial, and quality metrics for your SpringServe objects. In each section, a sunburst graph is displayed for given metrics. Sunburst graphs give you a hierarchical view of data.

graph view showing sunburst charts for requests, revenue, and viewability

When hovering over a segment you will see a label with the metric and corresponding rate. For example, hovering over the impressions segment shows the number of impressions, the request fill, and the opportunity fill, along with their respective range comparisons. Clicking a segment in the graph allows you to drill down to that level; clicking the backwards arrow button to move up a level.

For further details about the quickstats graph view, please see our wiki.

Changelogs

We have made various updates to the changelogs, including displaying changes in user timezone. As a reminder, you can change your timezone by going to Edit Profile under the user icon.

Targeting List Search

You can now search targeting lists for a specific item. For example, if you want to see the sites containing “times” on a domain list, you can use the search bar below the Included Domains box.

On the index page for targeting lists, you can filter by a list entry and see all lists that contain the entry.

List search is available on domain, app name and app bundle lists. Entries/lists will be displayed if the list has been active in the last 24 hours.

Export tag

Brightcove has been added to the options for tag export.

You can now choose from the following options:

  • SpringServe
  • Third-Party
  • Vidible
  • One by AOL
  • SpotX
  • LKQD
  • JW Player
  • Brid
  • Roku
  • Brightcove

Reporting Improvements

Key-Value Reporting

Dimensions

Key-value reporting is now broken out in a more granular manner. Previously, a key dimension would show a column for each key. Now, selecting Key from the dimensions will show a line for each declared key in your account. Note that the total for this report may not equal the total for a supply tag report. Running a Key-Values report will display columns for each key in your account. To run a report for a specific key, select that key from the dimensions dropdown, which appears in the format Key: key name.

Filters

Selecting the Key filter behaves in the same way as selecting a key (Key: key name) from the dimensions dropdown. Filtering for a specific value for a specified key can be achieved by selecting the desired key from the filters dropdown, and entering or selecting the desired value(s) for filtering.

Continent Reporting

You can now run a non-domain/app report with continent filters. The same options that you have for domain/app reports are available for supply and demand reports.

Bug Fixes

Various bug fixes and performance improvements

 

Leave a Reply

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