<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=134132097137679&amp;ev=PageView&amp;noscript=1">

Pixalate Week in Review: January 8 - 12, 2018

This week's review of ad fraud and quality in the digital advertising space.

1. Most publishers don't 'name and shame' when it comes to ad fraud, but not everyone agrees with this approach

finger-pointing.png

Digiday reports that few publishers "feel empowered to publicly name any supply-side platform that lets in large volumes of fraudulent inventory to their platforms...." Digiday notes that lawsuit potenetial and confidentially clauses are primary factors, but adds, "Others don’t believe contractual agreements should be binding when it comes to an issue as great as fraud."

2. Android app built with Kotlin language perpetuating ad fraud

android-phone.png

"For the first time, a malicious Android application built with Kotlin has been discovered in the Google Play store," reported Tech Republic, citing Trend Micro research. "According to the Trend Micro blog post, the malicious app is masquerading as an Android device cleaning and optimization tool called Swift Cleaner," wrote Tech Republic. "Once downloaded, it can perform many nefarious activities, including sending SMS messages on behalf of the user, remotely executing code, stealing data, forwarding URLs, and click ad fraud," the article added.

3. 'Journey hijacking' ad fraud hits e-commerce sites

e-commerce-online-shopping-credit-card.png

AdExchanger reports on an ad fraud attack impacting e-commerce sites. AdExchanger explains it as a "devious form of ad injection only visible to infected site visitors," and calls it "journey hacking." The malware "entices users to click on unauthorized product ads and links that whisk them away from their original destination to other sites," per AdExchanger, and is only visible to visitors who have an infected device.

4. Ad fraud prevention best practices: X-forwarded-for (XFF) IP addresses

best-practices.png

A new blog post from Pixalate "explains X-Forwarded-For (XFF) and the best practices as it relates to detecting, targeting and even blocking the IP addresses associated with programmatic advertising transactions to reduce ad fraud and improve quality. This is a common issue digital marketers encounter, but it’s one that remains a mystery to many in the industry."

5. The top 5 reasons CMOs should support ads.txt

iab.jpg

A ClickZ article spells out five reasons CMOs should get behind ads.txt, noting that domain spoofing is a legitimate concern and that ads.txt is a simple solution. The article also cites Pixalate research which reveals that large publishers are embracing ads.txt, and contends that the initiative will "promote transparency in the digital ad ecosystem."

Sign up for our blog to stay updated with new stats, trends, and analysis on digital ad fraud.

Popular Posts

Pixalate unveils the list of sites secretly mining for cr...

MRC Viewability Standards: What It All Means

MRC Definitions for Invalid Traffic: SIVT and GIVT

Pixalate discovers sophisticated sites that hijack sessio...