Sephrata
Elite Member
- Mar 25, 2017
- 2,722
- 4,086
So my thought was to use a third party tracker to eliminate the bot traffic or at least detect them as I am bleeding money away. Below is the reply of their customer support when I asked how can I setup the tracker to identify bot traffic.
Quote"
We are one of the leaders in the market for popunder traffic volumes, we got a strong anti-bot, anti-cheat system in place some of our publishers can try to cheat. We do not provide such fraud traffic.
Kind regards,
William Carrington
PA Support Team
"UnQuote
Not very impressive as it seems they are reluctant to allow third party tracking bot traffic in my personal point of view.
Popunder traffic is notoriously bad for the amount of bot traffic, especially in Tier 1 geos. Some networks are better than others, however you need to go through the traffic with a fine tooth comb and aggressively cut bad placements. It is essential to do this otherwise you just end up throwing money away.
The issue I have with Propeller is their 'response' when you identify bot traffic. Now this is a network I was doing a lot of business with (at the peak, buying 5 figures a week of traffic) and they were one of my main traffic sources for non-adult.
In the middle of last year, I saw quite a big drop off in the profitability in a number of campaigns I was running with Propeller. When I looked through some of the data with deep analysis (as low as IP level), I found there was large amounts of traffic originating out of data centres around the world. At first thought, I assumed this might be VPN traffic however further analysis showed that the user agents were being spoofed (I figured this out by correlating the screen size x user agent).
I reported this to my AM at Propeller and the response I received was that, if I don't like the traffic, I should block the site ID. I immediately reacted and told him that his response was ridiculous because I was reporting a sophisticated fraudulent traffic setup. He then said he would refer it to his technical team for further investigation.
The technical team contacted me to let me know that they found nothing suspicious with the traffic I had flagged. There was no explanation, no detail, nothing more than a single line answer. I provided a in-depth 2 page report, with the help of a security specialist, about why this traffic was fraudulent. One of the most obvious signs was that I had bought more than a million popunders which originated from a data centre literally located in the middle of a field (the closest village had a population of less than 200 people).
I eventually got a response which was a copy/paste of the previous email from the technical team. So I pulled the plug on them. They never responded to me after that and even when they were in Prague in the Autumn, no one made any attempt to meet with me.
I was seriously considering suing them, however I had so many projects going on at the time and I've already had too many legal battles already in my life. Anyway, I decided to leave them to it. A lot of big guys stopped running with Propeller and I knew that with the Google Chrome changes, they would end up screwed anyway.
Now whether the traffic was orchestrated by Propeller or they just turned a blind eye to it, I'm not sure. But their reaction to customers reporting fraudulent traffic is farcical, to say the least.