• Posted by Ehsan Mokhtari 11 Dec
  • 0 Comments

Invalid Traffic and Fraud Detection techniques explained

The Media Ratings Council has released their Invalid Traffic Detection and Filtration Guidelines and has put a 180-day deadline on planning and implementation for digital media metric providers.

With so many different schemes to get invalid traffic into the supply chain, it shouldn’t come as a surprise that there are many different ways to get it out of the supply chain as well. The MRC divides invalid traffic detection into two buckets, general and sophisticated. Think of the general as checking a list of previous offenders while the sophisticated is detective work over time.

General methods of examining traffic include the use of lists of known problems such as data center traffic, specific Spiders and Bots on industry lists, or Bot activities, which no human would do. This filtering occurs within ad servers, web analytics or any other ad tech that provides a counting service. It’s important to point out it’s all invalid traffic but not all of it is fraud, some of it could be just sloppy work. This points to the requirement for process audits to tighten up the work done on the supply side ensuring the list-based approach is applied throughout the supply chain.

The MRC’s other bucket is Sophisticated Invalid Traffic. Here fraudsters seek to install malware on people’s computers, steal ad tags, re-direct users away from their desired sites, stuff their cookies with fake data and much more. JICWEBS identifies 16 categories of malicious activity.

The General method is consistently applied however Sophisticated methods operate differently depending on where in the ecosystem they live. Sophisticated methods involve trying to block Bots before they generate pages sometimes called Reverse Proxy, presenting challenges such as Captcha, Pre-Load or Pre-bid for programmatic transaction environments, and serving third party pixels on ad creative. It’s important to underline that all methods are valuable to the overall ecosystem as long as their strengths and weaknesses are understood.

One of the most important distinctions about Sophisticated methods is whether they occur “in-line” or “in-parallel”. In-line is a sequential process, the browser makes a request, the traffic verification method has a very short period of time to determine human vs. Bot, then pages, ads etc. are delivered. In-parallel works by activating a script at certain point and then separating the delivery of ads and pages from the verification decision which can take as long as necessary.

In-line systems protect downstream users. No publisher wants to allow a malicious Bot access to scraping its pages for content or code. No programmatic buyer wants to obtain real-time ad placements only to find out later they weren’t valid even if they don’t get billed for them, they are lost opportunities. However the challenge is that user experience is determined by page load times and hence any in-line method must balance speed vs. the number of operations performed.

 

invalideTrafficIn-parallel methods excuse themselves of the user experience challenge and focus on accuracy and depth of operations performed. Some will take milliseconds and others will take considerably longer. Skip to page 8 of the MRC’s Invalid Traffic Detection Guidelines.

“… detection procedures for Sophisticated Invalid Traffic take time to execute and may not be feasible to apply to real-time processes. “

Fast-forward to page 25; “Requirement for Backward Looking Assessments and Correction”. The MRC mentions a 14-day window that can be extended longer depending on campaign duration or customer service requirements.

Clearly the in-parallel approach isn’t the one to apply to programmatic buying decisions however it is the one to apply to reporting and billing. No one really cares if their ads were shown to Bots but they sure as Hell don’t want to get a bill for it.

Another advantage of in-parallel methods is the feedback time lag to Bots. The MRC raises its concerns about reverse engineering invalid traffic detection secret sauce on page 8:

“Measurement organizations that apply Sophisticated Invalid Traffic techniques are likely to need to remove identified Sophisticated Invalid Traffic downstream from original detection at later times to protect detection procedures from reverse engineering.”

In-line processes with immediate feedback could be used to train better Bots as they trigger positive and false responses.

The point is success against fraudsters and the invalid traffic they generate is a multi-layered approach with specific defences for specific points. The system becomes more effective as it incorporates learning from one point to be applied somewhere else.

However detecting and filtering invalid traffic is only one part of the picture. Beyond lies the coming arrangements of tracking back to unscrupulous businesses, setting terms and conditions, standards of operations, reconciling billing workflow to provide advantages to audited media suppliers and benefits to advertisers focused on quality. Digital media, like any supply chain, is going through the growing pains of securing its marketplace.

Originally published in Media in Canada

This article was co-written by Ehsan Mokhtari of Sentrant Security and Chris Williams.