We discuss updates to timeouts logging, additional reporting metrics, improvements to the realtime debugger, and more.
In August of 2021, SpringServe switched from http1 to http2 protocol. This switch led to a general improvement in stability of our platform. At that time, we saw a significant decrease in timeouts across the platform. However, over time we realized that many of these timeouts had shifted to 1606 errors in reporting because they were presenting themselves in a different form: http2 closed connections.
We have since updated these http2 closed connections to be classified not as VAST error code 1606 but rather as what they are: timeouts. Therefore, you may notice an increase in timeouts but a decrease in VAST errors in reporting.
Along with this reporting change we have made some performance improvements to our timeout logic that should particularly help partners with lower timeouts.
If you have any questions about this change, please reach out to your account manager.
SpringServe has added metrics describing the pod response for your supply tags, specifically regarding how many slots and how much time was returned or filled per pod response. These metrics can be found in the Calculations section:
- Avg Slots Returned = Pod Slots Avail / Opportunities: Average number of slots returned per pod response
- Avg Pod Time Returned = Pod Opp time / Opportunities: Average number of seconds returned per pod response
- Avg Pod Time Filled = Pod Fill Time / Opportunities: Average number of seconds filled per pod
- Avg Imp Time Filled = Pod Fill Time / Impressions: Average number of seconds filled per pod impression
In demand reports in SpringServe, we have added Use Rate as a Calculation. This metric is calculated as demand opportunities / ads.
For a full description of our reporting metrics, please see our reporting glossary.
In the coming weeks, we will be updating the naming convention for some of the existing pod metrics and demand so they more clearly describe the events. Release notes will be sent out at that time.
Content reporting is now faster and more robust. Available dimensions include:
- Channel Name
- Content Custom 1 Param
- Content Custom 2 Param
- Content Custom 3 Param
- Content Episode
- Content Genre
- Content ID
- Content Producer Name
- Content Season
- Content Series
- Content Title
- Network Name
- Production Quality
If you need to report on dimensions outside of our native content parameters, include the wildcard parameters content_custom_1/2/3_param in your exported tag and report on Content Custom Params 1/2/3.
Note that third party vendor metrics such as IVT impressions and viewability are not available on content reports
You can report on hourly content data for the last 48 hours, after which data is compressed into daily UTC intervals.
Tier Breakout Reporting
If you are trafficking demand through header bidding tags or SpotX Connect, you have the option to implement tier breakout. This feature allows bids to be placed in the first look tier if the bid exceeds the set value. SpringServe logs breakout impressions when an impression occurs at this higher breakout bid price.
Previously, you were able to report on these breakout impressions only by running bid density reports. We have simplified the reporting process by adding Breakout Imps to all supply and demand reports, including content and advertiser domain reports. This metric appears in the Numbers section.
Advertiser Domain Reports Metrics
Previously, quality and financial metrics were excluded from advertiser domain reports. These metrics are now available.
We have made a number of additions and improvements to the Realtime Debugger.
If a supply tag is called via a router request, we now display these requests in the Requesting Endpoints panel of the supply tag.
Various content attributes are now displayed in the Content Panel. Select from Episode, Title, ID, Series, Seasons, Genre, Channel, Network, Producer Name, Language, Rating, Production Value, and Livestream to see a visual representation of the passed attributes.
In the Privacy panel, you can select from GDP, COPPA, and DNT to see a donut graph of privacy attributes.
On the Outgoing Requests tab, you can see macro values of the parameters that SpringServe passes to your demand partners. This tab is now visible on demand partners and campaigns, as well as demand tags.
Nielsen Digital Ad Ratings is now available on both the supply and demand partner level. Enable this feature under Custom Integrations.
Targeting on geographic regions can now be done using lists. This feature makes it easier for you to implement the same geographical targeting across multiple objects. To create a geo list, go to the Geo Lists tab of the Targeting page. Select the type of list you want to create from the dropdown: Country, State, City, DMA, Postal Code.
On the new list page, you will be able to add your entries in the same manner as adding targeting on a tag, partner, router, or campaign.
Targeting Using Lists
When applying geo targeting to an object, select List as the Targeting Source and you can apply your existing geo lists.
Note that lists have the same restrictions as object targeting. However, we will be expanding our sub-country targeting to include more regions in the coming weeks.
SpringServe continues to expand support for our header bidding demand tags. Updates have been made to the following adapters: Unruly, The Media Grid, Verizon Media.
When activating your Partner Segments, note that TruOptik has been renamed to TruAudience.
Various Bug Fixes and Performance Improvements.