Ad quality improvements, audited creative targeting, min and max duration targeting in pods, forecasting, and much more!
We continue to improve our ad quality features in SpringServe by increasing feature parity between managed and DC tags and improving the Ad Quality UI.
You can now apply competitive exclusions for advertiser domains and IAB categories on DC demand. Previously, these features were only available on managed demand tags. Likewise, brand-safe and objectionable overrides are now available on SpotX Connect. With these updates, you can now apply any inventory quality or competitive exclusion targeting on any class of demand in SpringServe.
Note that the Inventory Quality targeting icon now denotes advertiser domain list targeting. Previously, you would find this targeting on the list icon.
Audited Creative Targeting
Setting the Audit Status
If your account is enabled for the creative review, you may access audit status targeting. When BingeWatcher first scans creatives, it sets the audit status to Pending. In the Ad Quality UI, you can flag scanned creatives as Approved or Rejected. Set the status on the scanned creatives index table by clicking the icon in the Status column, or by using bulk actions.
You can also set the status on the Settings tab of the scanned creative.
Targeting Audited Creatives
On Supply Partners, Routers, and Tags, you can set Audited Creative Targeting in the Inventory Quality section of the Targeting tab. By selecting Custom Audited Creative Targeting, you can reveal a checkbox list of Allowed Audited Creative Statuses.
Check the boxes of statuses you want to allow to serve on this supply. If you have very sensitive supply, you may want to only allow approved scanned creatives. For less sensitive supply it may be appropriate to allow both pending and approved scanned creatives.
Let your account manager know if you are interested in Audited Creative targeting.
Ad Quality UI
We have made updates to improve the usability of the Ad Quality UI. Primarily, these changes are behind the scenes and allow increased performance of the UI. The Scanned Creatives table now displays creatives have been seen in the last 24 hours rather than the last 30 days, as previously. This change allows for an improvement in load time. Creatives that have not been seen in the last 24 hours will not appear in the table but the Scanned Creative page is accessible if you had bookmarked the page or load it directly by entering the scanned creative id in the url console.springserve.com/ad_quality/scanned_creatives/<scanned_creative_id>
We have removed the scanned assets tab of the Ad Quality page to speed up performance. However, you can now filter on the scanned creative table for attributes of the underlying assets such as duration, bitrate, volume, height, width, and media container type.
These filters are also available on the Assets tab of the creative and all asset metadata is still visible there. Additionally, when previewing a creative you can select the asset you would like to load in the player.
We have updated our COPPA targeting to permit users to either allow or block COPPA supply. This update allows more flexibility for various use cases. Checking coppa Param Required will allow any request that includes a value in the “coppa” parameter to pass targeting. To allow only specific COPPA values, use the checkbox group.
All objects that were using the deprecated Block COPPA Supply targeting have been updated with the appropriate Allowed COPPA Values so there is no need to make manual updates.
Min and Max Duration Targeting
You can now target the minimum and maximum duration of ads within a pod by passing the min_dur and max_dur parameters on the pod request. Previously, SpringServe would pass these values in the bid request for header bidding demand in the imp.video.minduration and maxduration parameters and it was up to the bidder to respect them. We now internally filter ads from all demand classes based on these parameters, so you have more control over the demand that serves within your ad pods.
Additional User Agent Targeting
When targeting operating systems in SpringServe, you can now select the LG TV operating system, webOS TV. The addition of this operating system is also reflected in reporting.
SpringServe is excited to announce our initial forecasting offering. Currently, we give you a high level forecast across your entire account on the homepage on the Account Activity dashboard.
To display forecast data, select a value from the crystal ball dropdown that appears to the right of the historical period dropdown. You can run forecasts for the rest of today (T), the next 7 days (7), the rest of this week (W), the next 30 days (30), and the rest of the month (M). When 0 is selected, no forecast is shown.
Note that forecasting is disabled when historical periods of yesterday, last hour, last 15 minutes are selected.
When displaying a forecast, all panels on the dashboard are updated. The Metric Cards display the historical and forecasted values below the total.
The Performance and Financial graphs display forecasted series in dashed lines and diagonal filled bars or splines. Hourly and daily intervals are supported.
Independent of the time periods selected, we display forecast data on the Performance (Comparison) graph. The Today Forecast is displayed in diagnoal fill and the forecast for Seven Days From Now in dashed line.
Data displayed in the Top 10 Supply and Demand tables reflects the total for the historical and forecasted periods.
Forecasting data is also reflected on the Supply and Demand dashboards. You can look forward to seeing these types of data visualizations throughout the platform as we continue to build out forecasting in the coming months. If you are interested in forecasting in SpringServe, let your account manager know.
Since clicks are a highly relevant metric to tiles, we now include them in object quickstats. Both clicks and CTR now appear on object quickstats panels and index tables. Additionally, clicks now replace completes in sunburst graphs on tile objects.
We continue to grow the number of integrated platforms for header bidding demand. New adapters added recently include: Magnite CTV, Stroeer, Teads, and Videobyte. Our IronSource adapter has been updated for client side support, and we’ve updated Equative (Legacy Smart Ad Server) and Index to support multi-imp.
When applying audience targeting, the search now remains open after selection of a segment. This change should make it easier to apply segments when targeting a large number of them.
On the Segment and Partner Segment tabs of the Targeting page, you can now see the number of objects that are targeting a given segment when looking at the full view of the table.
Click on the number in the demand tags column, for example, and you will be redirected to the demand tags tab of the segment. Here, you will see all the demand tags using that segment in audience targeting.
Last 72 Hour Reporting
Since we have Last 72 Hours available as a time period for quickstats, we have added it as a preset on ad hoc reports. Additionally, you can now pass additional values for “date_range” in the API: “Last 72 Hours”, “Month to Date” , “Last 30 Days”, “Quarter to Date”, “Last Month”.
Log Level Data
We have made a number of additions to available columns in log level data: pod_id (int), schain_present(bool), gdpr_consent_present (bool), bidder_account_id (int), device_id_syn (bool). For a full list of available columns, please see our wiki.
In an effort to consolidate the number of events SpringServe fires, we have made an update that will have an impact on Log Level Data. Specifically, any ssb_demand_errors that have a VAST Error Code of 1604 or 1624 will now be combined with ssb_demand_requests in a new event called “ssb_demand_request_error”. Overall reporting will not change, however when querying specific event types in Log Level Data, you may need to consider this change in queries pulling demand requests and/or errors. Please reach out to your account manager with any questions.
If your account is enabled for Multi-currency, supply and demand clients can now run reports in global currencies.
Various bug fixes and performance improvements.
Comments are closed.