Global postal code targeting, global currencies, new budget metrics, detected advertiser domain targeting, and more!
Global Postal Code Targeting
SpringServe has expanded our postal code targeting to include support for all countries. Previously, postal code targeting was only applicable to US, Canada, and Great Britain.
To specify that your postal code is in a different country, include the 2-letter country code separated by a colon in the targeted postal codes. For example, the targeting shown below would allow the postal code 10117 in Germany by entering the value DE:10117.
We support this functionality on postal code values or postal code lists.
When targeting US, CA, and GB postal codes, it is not required to include the country code. Previously implemented tags will continue to target postal codes in these three countries without the country code.
Global Currencies on Object Pages
If your account is enabled for global currency support, you can now select the currency throughout the UI. Previously only available on the dashboard and reporting pages, the currency dropdown now appears on all SpringServe pages. Updating the currency selection will update the financial metrics in quickstats panels and graphs, as well as the index tables.
If your tags have rates in non-USD currencies, SpringServe will load them in the rate currency. Otherwise, we load the object pages in your account’s default currency. Discuss with your account manager if you would like to change your default currency.
IP + User Agent Segment Type
If you need to target on IP address and user agent string, you can now create Segment lists for this purpose. Items on this type of list should contain the IP address and user agent string separated by a pipe (|). For example: 184.108.40.206|roku/dvp-11.0 (220.127.116.1180-cw).
Target these segments in the Audiences section of the targeting tab and select your list.
New Budget Metrics
You can now set budgets based on clicks and completed views.
With this addition, we have changed the order of the metric options in the budget section to be Revenue, Requests, Impressions, Completes, Clicks.
Brand-Safe and Restricted Audience Overrides
SpringServe scans creatives running through your account and gathers data about the advertiser domains. These advertiser domains sometimes are flagged as not brand safe or not safe for all audiences. For example, budweiser.com is appropriate for mature audiences because it is an alcohol brand and should not be targeted to end-users under the age of 21. Since fanduel.com promotes gambling, it is not brand-safe.
By default, SpringServe blocks advertiser domains that are not brand-safe and/or not safe for all audiences. We now offer you control over these settings on supply tags and demand tags. If, for example, you wanted to run an ad with the advertiser domain budweiser.com, you would set Allow Restricted Audience Ads to enabled on the supply tag and the demand tag with the Budweiser ad.
Likewise, if you wanted to allow a gambling ad on your supply, you would enable the Brand-Safe Block Override on the supply tag and demand tag.
You can set these overrides in the Inventory Quality section of the Targeting tab of a supply or demand tag.
Dashboard Format Filter
If you run tiles in SpringServe, you can now separate your video and tiles traffic on the dashboard. The dashboard loads a summary of activity for all formats by default.
To see stats for only your video activity, click the video camera icon.
To see stats for only your tiles activity, click the tile icon.
The metric cards and the graphs will update according to the format filter. Note that the metric cards display Clicks in place of Pod Time Request Fill % when filtering for tiles.
We continue to improve our support for header bidding demand in SpringServe.
Detected Advertiser Domain Reporting
You can now run reports for detected advertiser domain as well as declared advertiser domain. Select these as dimensions or apply filters.
In API reports, request “adomain” and “detected_adomain” as dimensions.
This data is available from October 26.
Note that we currently do not report the detected advertiser domain if the declared advertiser domain is not unknown. Therefore, you will always see one or the other advertiser domain reported as unknown; it is also possible for both to be unknown. In future we will be adding reporting for detected advertiser domain when the declared advertiser domain is not unknown.
In addition to the reporting update, we now include the detected advertiser domain in the VAST extension if no advertiser domain is declared, when applicable.
Frequency Cap Maximum
We now implement a maximum of 10 requests or bid requests per minute.
Various bug fixes and performance improvements.