In our latest release, we discuss value lists for your custom key-values, reporting updates, account_id reporting in the API, and various UI improvements.
In SpringServe, you can define your own custom key-value targeting. For example, if you want to target on browser, you can define that as a key and add values for Chrome, Firefox, and Internet Explorer. Values can also be free; if you have created a Zone ID key, for example, you may want to use a free key since you will be dealing with a large number of unique values. Demand tags and connected demand can be targeted on your custom keys. For more information about custom Key-Value targeting, please see this release. We have now added value lists so you do not have to add a long list of values to target on a demand tag. These behave like domain lists as a utility for targeting.
Creating Value Lists
For each key, you can create value lists by going to the Value Lists tab of a Key and clicking the +Value List button.
From here, you will be taken to the settings tab of your value list. Here, you can set the name and description and add your values. Values can be entered manually as a comma separated list. You can also append values to your list by uploading a CSV file.
If your key is predefined, any values in the CSV that are not loaded as predefined values will be added to the key.
Targeting Value Lists
In the Key-Value section of the targeting tab of a demand tag, you will are able to set Key-Value targeting. If you would like to target a value list, toggle to Value Lists once you have selected the key to target. You can search in the text box for your existing value lists. Multiple value lists can be targeted on a single demand tag.
Declaring Your Keys
Keys can be declared on a supply tag. When you declare a key on a supply tag, you will be able to report on that key by selecting key-values as a dimension in reporting. On the Export Tag tab, you will see keys that have been declared on a supply tag.
These are checked by default and you should make sure to include them when exporting the tag to your supply partner. They will be able to replace the macro for your custom keys so the values are passed to SpringServe.
Other Demand Targeting Updates
You have the ability to set targeting on multiple levels of demand: partner, campaign, and tag. In order to pass to a demand tag, a request must pass targeting on all three levels. We have added targeting on DirectConnect demand partners; previously it was available on managed partners only. Specify partner targeting on the targeting tab.
You can now set weekly budgets on your demand tags, campaigns, and partners. The budget will be executed between Sunday and Saturday eastern time.
API & Reporting Improvements
Downloaded reports are now available as gzipped CSVs in the UI. Click on the zipped file icon to download the gzipped CSV.
This is useful for large reports like those which include domain data for a large number of tags because it avoids timeouts when downloading the report. Note that your reports may be very large and contain a large number of rows, so you will need to have a way to read these data once you have downloaded the report.
We have added dimensions and filters for VPAID Type and Campaign to quality reports.
Pre-bid blocked is now broken out into two columns – Blocked (WhiteOps) and Blocked % (WhiteOps). These columns will provide data about Pre-bid blocking from WhiteOps, a third party company that identifies IVT. There is a 72 hour delay on this data and this can lead to initial zeros in the this column. Blocked (Total), Blocked (Targeting), Blocked (Pre-Bid IVT), and the corresponding blocked rates will be updated as Blocked (WhiteOps) data becomes available.
This will not impact IVT Imps or the IVT % columns since those columns are based off of post-bid IVT detection.
You may have access to multiple accounts within SpringServe; for example, you may be an admin in your account and a supply client for a number of other accounts. When using the reporting API, you can now run your reports via the API for any of your accounts using the account_id parameter, regardless of which account you are logged into in the UI. For general API requests, you can use account_id in the body of your request. For the Python SDK, you can use account_id= argument. Please note that you can only use one account ID at a time; you cannot run a report by a list of accounts; account_id is not an available dimension.
You can now see the number of campaigns for each of your demand partners on the Demand Partners tab of your Demand page. Clicking on the number will bring you to the campaigns tab for that demand partner. For more information on campaigns, please see last month’s release.
On the Demand Tags tab of a demand partner, you will now see an +Demand button. Clicking this button takes you to the settings tab for a new demand tag that has pre-selected the partner.
Improvements to Summary Statistics
Range compare has been added to all summary stats in quickstats.
If the change was positive, it will be shown in green; if it was negative, it will be shown in red. Range compare is also shown for Requests, Opps, Opp Rate, Imps, Req Fill, and Opp Fill on the supply tags tab of a demand tag and on the demand tags tab of a supply tag. Another addition to this section is Partner filters. All your Supply / Demand partners will be shown in this filter.
You can now filter by rate on the demand tags tab of a demand parter; search for all your tags that are at a particular rate.
If a client user no longer works for your partner, you may want to delete that client user from your account. You can now do this on the user tab of supply and demand partners. You can also delete users from your account on the Users page by clicking the trash icon.
- Downloaded reports now include the names of inactive tags and do not show null impressions.
- You can now duplicate Direct MP4 Demand Tags.
- Targeting for partners and campaigns created in the API is now available in the UI.
- Connected Demand will not be marked as not new when deactivated on the supply side.