What to ask before applying a block list to your ad space

Posted by Fraudlogix on Jun 6, 2016 12:00:00 PM

In the battle against ad fraud, some of the basic recommendations to protect ad dollars within the programmatic space is to employ a block list so that ads don’t get served on domains or to IP addresses associated with fraudulent activity. This recommendation has been stressed to both the demand and supply sides of the programmatic ecosystem. And while using a block list can be an important first step to weed out fake traffic, users should not be lulled into a sense of security just because they have one. Here are five questions to ask about a block list before applying it to your space:

How often is the list updated?

A static list, no matter how good its creator is, will become more and more obsolete as time rolls on. Yes, a set block list may provide protection against historically bad actors, but the keyword here is “historic”. Ad fraudsters are not able to skim billions from the digital advertising industry by standing still. Ad fraud moves and morphs constantly and when one domain can no longer swindle advertisers out of ad dollars, another is quickly created. The same thing goes for IP addresses - a few extra script details added to a bot can easily change or mask an IP address. A block list can be rendered out-of-date in just days, if not hours. Without constant upkeep and maintenance block lists can become obsolete, and companies that rely solely on a static list are leaving themselves open to fraud.

What is the list blocking?

Users of a block list should be aware of what the list includes and why. How does a domain make it on to the list? I.e., what is the logic that deems a domain fraudulent? Does it have to contain over a certain percentage of fake traffic? If so, what percentage? And are you OK with those metrics?  What does the list protect against? Are IP addresses or domains associated with bots, non-human traffic, user-generated fraud, automated scripts, and malware included? With the use of any block list, you know should what can and cannot get through.

How big of a pool is the list being pulled from?

How big of a picture does the block list’s creator see of the digital ecosystem? If data is pulled from just a small fraction of the proverbial pie, fraudulent domains and IP addresses outside the scope of the creator can easily be missed.

How easy is it to update the block list?

If you are applying a third-party block list to your environment, you should consider whether automated access (e.g., API access) is available, or if you have to manually request the list or download it on your own. Having an automated process saves time and ensures the most up-to-date list is being used.

Can you host the block list within your space?

Having to connect to a block list hosted by a third party can add latency to your bidding process. You should be able to integrate a list directly into your environment.

Block lists can be a tremendous help in filtering out fraudulent domains and fake traffic, especially within environments that see a lot of traffic (e.g., a DSP or SSP), but users should do their homework and ask questions because not all lists are created equal.


Topics: IP Block List, Ad Fraud, Fake traffic

Fraudlogix Blog

Fraudlogix was founded in 2010 by industry veterans with a deep understanding of the digital ad ecosystem. We cater to the unique challenges faced by the supply side and DSPs within the programmatic marketplace and deal with ad fraud and brand security on a daily basis. Within the Fraudlogix Blog we share our expert insight, specifically for the supply side and DSPs.


RTB Corner

With the "wholesalers" of the programmatic industry in mind, we created the RTB Corner - a round up of the latest news and views of interest to the supply side and DSP community sent every other week.

Subscribe to the RTB Corner Newsletter