Eight Out of 10 Premium Publishers Admit They Don’t Have Insight Into How Their Traffic Is Audited by Third-Party Measurement Companies

December 16, 2016

The burden of proof is on publishers to defend their web traffic, yet 80% admit they don’t have insight into how their traffic is audited, raising questions about which traffic is non-human traffic (NHT). At the same time, marketers are no longer willing to pay for NHT, with 74% of publishers reporting that traffic quality issues are part of pre-sales discussions, and 68% stating they have received requests for information (RFIs) with acceptable NHT thresholds. This disconnect is leading to lost money and frustration for both advertisers and publishers.

These statistics are included in a new report from The 614 Group titled, “2017 State of Digital Publishers’ Fight Against NHT: To Block NHT or Not to Block,” and sponsored by Distil Networks, Inc., a provider of bot detection and mitigation. The report includes a survey of 40 of the comScore 250 publishers, including AccuWeather, A&E Networks, Hulu, Thomson Reuters and Univision, about their attitudes and experiences with NHT, both as an internal issue and as a discussion point with clients considering direct buys of their inventory.

The report brings to the fore the lesser known cascading negative effect of even nominal amounts of NHT. That is, the impact of bots collecting cookies on legitimate publishers’ sites, only to lure those advertising dollars away to nefarious players.

Read the Article

Previous Article
Eight Out Of 10 Publishers Don't Know How Their Traffic Is Audited By Third Parties
Eight Out Of 10 Publishers Don't Know How Their Traffic Is Audited By Third Parties

A new survey out Thursday reveals that 80% of publishers concede they don’t have insight into how their tra...

Next Article
Preparing for PSD2 – How Banks and Retailers are Approaching the Five Big Issues Around APIs
Preparing for PSD2 – How Banks and Retailers are Approaching the Five Big Issues Around APIs

Stephen Signam of Distil Networks discusses 5 issues around API with the new Payment Services Directive ver...