Lawlerskates
Junior Member
- Nov 29, 2009
- 197
- 71
How can you cover your tracks when driving blackhat traffic to offers if someone knowledgeable about CPA reports your site to the network?
add fake contacts on the page with the iframed offer, so they think that they report to a network
<Script Language='Javascript'>
<!-- HTML Encryption provided by iWEBTOOL.com -->
<!--
document.write(unescape('%3C%2F%64%69%76%3E%0A%3C%73%63%72%69%70%74%20%6C%61%6E%67%75%61%67%65%3D%22%6A%61%76%61%73%63%72%69%70%74%22%3E%64%6F%63%75%6D%65%6E%74%2E%77%72%69%74%65%28%61%64%29%3B%3C%2F%73%63%72%69%70%74%3E%0A%0A%3C%2F%62%6F%64%79%3E%0A%3C%2F%68%74%6D%6C%3E'));
//-->
</Script>
I'm making about $150 to $160 a day now using a blackhat method on a couple of CPA networks (not fraud). It's just about a guarantee that somebody that knows about them has landed on my page and attempted to report me...and here are the steps that I've taken to prevent reporting:
First, my source code is completely encrypted. I use this tool to do it: http://www.iwebtool.com/html_encrypter
This is what it makes a pages source code look like:
Now, if the visitor pays REALLY close attention to their status bar, they'll still see the offers URL as it loads in the iFrame. There is also the possibility that they're using HttpFox (or a similar tool that tracks all requests sent & received & what pages & URLs have loaded). So, to throw them off there, I've added in 20 fake affiliate offer links with bogus affiliate numbers that also load on my page. The real one is obviously in there, but they would have to find all 21 companies and report all 21 different affiliate numbers.Code:<Script Language='Javascript'> <!-- HTML Encryption provided by iWEBTOOL.com --> <!-- document.write(unescape('%3C%2F%64%69%76%3E%0A%3C%73%63%72%69%70%74%20%6C%61%6E%67%75%61%67%65%3D%22%6A%61%76%61%73%63%72%69%70%74%22%3E%64%6F%63%75%6D%65%6E%74%2E%77%72%69%74%65%28%61%64%29%3B%3C%2F%73%63%72%69%70%74%3E%0A%0A%3C%2F%62%6F%64%79%3E%0A%3C%2F%68%74%6D%6C%3E')); //--> </Script>
Add all the above in with a fake contact "report spam here" button, and I think you'd be golden.
As of now, just using what I mentioned alone, I haven't gotten busted yet.
@Crazyflx: Do you load the 20 fake aff links in the iframe before the good one? I mean 20 links is freaking long to load, no?
<img border="0" src="http://youraffiliatelink.com" width="1" height="1">
Oh alright, I get it! Pretty interesting method you got there!
Thanks for sharing this mate!
This method works if you iframe an offer but this wont work if you simply redirect to the offer without iframe, since the offer will load like a normal webpage.
No problem at all man, happy to help.
And yes, you're right. If you're redirecting to the offer, it won't work.
What you could do, is redirect to a full page iFrame (which most networks are actually okay with. I mean, a literal full page iFrame where the page looks EXACTLY like it would if you just visited the URL directly).
Then, since it'll still be on your domain, you could put the fake 1X1 images beneath the iframe & still encrypt your source code & still be in compliance with the CPA companys policies (for the most part).
IMO, its still better to avoid Iframe at all
I'm a little confused. If you're trying to make it impossible for you to get reported, wouldn't you just have the traffic source appear to be a non-iframed version of the offer using something like CPA Redirect?
Even is using something like CPA redirect, the person who hits the lander will still see the offer page URL in their status bar (bottom left hand corner of their browser).
Also, if they are using a software like HTTPFox, they can watch/monitor ALL urls loaded and all requests sent & received. It stores them so the user can go and look over them later.
Hence all the precautions above.