New AdSphere Build – 11-28-2019

Happy Thanksgiving!

DRMetrix pushed a new AdSphere build today which mainly focuses on system stability and bug fixes. We have also changed how we refer to DPI ad breaks in AdSphere. In many places, we previously referred to DPI ad breaks as “local DPI” or just “local” throughout the system and in various excel reports. In this new build, you will only see the term “DPI” which refers to airings detected in the DPI ad breaks on the networks. We have removed the term “local” as it has created too much confusion over the years.

If you are not familiar with DPI ad breaks, we encourage you to click on this link to learn more. You will discover that DRMetrix is the first television research provider that monitors commercial grade network feeds in a DPI compliant manner and what this means.

Previous to this change, DRMetrix found that many users were confusing “local breaks” and “local” to mean local market MVPD airings. Although we would try to explain that these terms refer to “local DPI ad breaks” on the networks, confusion remained. In an attempt to communicate more clearly, DRMetrix will standardize on the term “DPI” or “DPI ad break”. You will notice in all excel outputs where the term “local” was used previously, that the column headers will now simply read “DPI”. Also, instead of denoting DPI breaks with “L” in our excel outputs, we will pass the value “D” short for DPI. National ad breaks will continue to use “N”.