We’ve delivered improved reporting for Magnite Streaming deals, updates to advertiser domain targeting, a new look and added definitions for calculations in reporting, and more. Read on below to learn more about key updates from our efforts this summer.
Reporting improved for Magnite Streaming deals, making it easier to surface more information within the SpringServe platform
To make it easier for clients to surface key information about Magnite Streaming deals within the SpringServe UI, we’ve made a number of improvements, including the ability to select dimensions and filters for Magnite deals in both the reporting page as well as in the demand and waterfall table of supply tags.
Deal reporting allows clients to report on Magnite deal IDs, codes, and name dimensions but also enables the ability to surface information in the UI without having to run a report, making it easier to navigate between platforms and consolidate workflows.
Mangite deal quickstats:
Now available both in the supply tab of demand tags and the waterfall tab of supply tags, an icon will appear opening a view that displays the deals data for Magnite header bidding demand tags. In addition to the quickstats summaries, graph view visualizations are now also available in that modal. Magnite metrics that are currently available include programmatic bids, wins, and imps along with revenue and RPM.
Magnite Streaming tiering is now supported in SpringServe across programmatic guaranteed deals for clients using BidLink
Prior to this release, our tier competition work supported tier prioritization for SpringServe VAST tags. We have now added support for tier prioritization for BidLink as well.
With the deprecation of SpotX, XConnect functionality will be pared down
As a result of the SpotX deprecation on 7/31/2020, clients will no longer be able to make bulk action changes to SpotX Connect, create new SpotX credentials, create new XConnects, or duplicate existing XConnects. Moving forward, clients will also no longer be able to add XConnect to targeting lists.
Ad Quality UI
Updates to BingeWatcher make it possible to target detected adomains, fallback to a declared adomain when none is detected, or override and correct adomains
This Ad Quality UI improvement allows clients to override and correct detected adomains. For example, if SpringServe detects the adomain “springserve.com” but the correct adomain is “magnite.com”, the client can input the correct adomain. Once an adomain override has been applied, SpringServe will use the override setting for targeting.
Add IAB category codes on any creative
This release makes it possible to add multiple IAB Tier 1 and 2 category codes to any creative. To add creative codes, navigate to the bottom of the first column of the settings tab on creatives.
Upload tag creatives in bulk through CSV uploads
This feature enables clients to bulk upload tag creatives into SpringServe to reduce manual efforts. Clients can now upload a CSV with VAST URLs, advertiser domains, landing page URL, creative code, and geo targeting.
Usability improvement now allows clients to check or uncheck all boxes in targeting
Prior to this release, clients had to manually check or uncheck boxes within targeting options. This update improves usability by allowing clients to “add all” or “remove all” options within targeting checkboxes then additionally uncheck or check additional boxes as needed.
Usability improvements allow clients to bulk upload up to 1,000 postal codes
For clients seeking to upload large postal code lists without the use of DMA targeting, we now support the ability to upload a maximum of 1,000 entries. For entries larger than 1,000, a CSV upload is still required.
Option to default to inactive status for new and duplicated campaigns is now available in SpringServe
This usability improvement makes it possible to default to “inactive” as a campaign status upon creation. While “inactive” is a new status option, the default behavior within SpringServe will remain “active” at the time of campaign creation.
New visual indicator lets clients know when a graph is still loading
Depending on the data being queried, graphs can take some time to load. Prior to this release, there was no indicator that response time graphs were in process of refreshing. These graphs can be found on the waterfall tab of a supply tag or the supply tab of a demand tag or campaign. We’ve improved that experience with this release by adding a visual that lets clients know when a graph is still in the process of “refreshing.”
- Rich Audience Header Bidder integration is now available
- YieldOne header bidding adapter added
- Applovin Header Bidder integration is now available
- Media.Net Header Bidder integration is now available
- Origin Media Header Bidder now supports multi and max impressions
- For Teads’ Header Bidder adapter, maximum impressions are set to 8
- SpringServe no longer calls SpotX Connect or SpotX Header Bidding tags
Reporting has a new look and added definitions to improve usability and understanding
Improvements have been made to reporting, including the addition of a tooltip showing the calculation that appears when hovering over applicable metrics. Now, clients can see a metric’s formula when it is derived by using a calculation. In addition to this new functionality, metrics within reporting have also been regrouped and have received styling updates for enhanced usability.
Run advertiser domain reports to gain visibility into which advertiser domain was used in targeting
This work accompanies the advertiser domain override release, which allows clients to block or allow specified advertiser domains. Alongside that release, reporting has been updated to offer clients a view into which category of advertiser domain values was used in targeting.