How can you cover your tracks when driving blackhat traffic to offers if someone knowledgeable about CPA reports your site to the network?
That's brilliant, to say the least. If you drive thousands of hits to a blackhat page like I do, one of them is bound to be someone who knows a thing or two about CPA, and will report the page because I spammed one of their favorite forums/sites. Of course this isn't fool proof, but it would throw these people off.
^^^ That's what I was going to say. Once in with networks where you can put everything out on the table you're good to go.
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: 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> 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. 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.
that's a really nice method (multiple aff. links), I heard about it before, but never used it. thanks for reminding
Crazyflx, that's genius. I just wish I employed that technique before I got reported and lost a few week's worth of earnings. I have a few CPA Networks under my belt (one of them being really small and private), so I should be able to get away with it now.
@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?
No, I don't load them in an iFrame at all. In fact, they don't "actually" load at all. However, it is enough to send & receive the post requests. Here is how I do it: Code: <img border="0" src="http://youraffiliatelink.com" width="1" height="1"> I post all of these beneath ALL of the content on my page, just above the closing <body> tag. I do this with all the fake aff. links AS WELL as the my real one. So I've got 21 1px "images" at the bottom of my content. Now, they can't see that because I've encrypted my pages content. However, the requests are still sent/received and still show in the status bar. So, it doesn't slow page load time & still completely throws any "snoopers" completely off track.
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).
Yes you are right. IMO, its still better to avoid Iframe at all but like you said, some networks might accept it!
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.
What I'm asking though is why the talk of network compliance? Is there no way to hide an iframed offer from the network? For Example, Let's Say I'm Using Incentive Offers: Traffic --- > My Content Locked Porn Site ---> My Network Compliant Site Blog (CPA Redirector 2) ---> Iframed Offer But when the network looks at the network compliant site blog, all of the offer links will take you to the offer directly - and not the iframed version of the offers. Or is it impossible to hide the fact your iframing the offer from the network? Will the page with the iframe show up as the referral URL?
