Cloaking and Leaking Referrers

[aeisn]

Right now I'm using prosper202's built in cloaking to hide my referrers. As I understand it prosper202 just uses a javascript redirect followed by a meta refresh. From what I've read this will hide the referrer 99% of the time but you're still going to have some referrers leaking.

My question, is there a way to check if the referrer is being passed or not so I can just dump that 1% of the traffic where the referrer is leaking? In addition is a javascript redirect + a meta refresh the best/fastest way to be cloaking my traffic? Any input is appreciated.

 

[Garrett]

Don't worry about your landers getting leaked. Your Prosper domain will *possibly* leak 1% of the time since all the redirects pass through it, not your lander.

is there a way to check if the referrer is being passed or not so I can just dump that 1% of the traffic where the referrer is leaking?

Not sure, but Im gonna guess that is overkill.

In addition is a javascript redirect + a meta refresh the best/fastest way to be cloaking my traffic? Any input is appreciated.

Double Meta Refresh takes 20 seconds to setup.
or
Process your redirects through a tracking domain so THAT is what gets leaked




Im no expert though, this is all heresay

 

[dchuk]

use an ssl cert

 

[aeisn]

Thanks for the responses, I was just reading this thread: http://www.wickedfire.com/affiliate-marketing/90983-my-cloaking-isnt-cloaking.html and it seems like it is possible for prosper to leak my traffic source/lander, not just my tracking domain. From what I've read SSL is another layer of protection but still isn't foolproof for some browsers.

 

[kingscotty38]

Double Meta Refresh takes 20 seconds to setup.

I've tried all sorts of DMR scripts and even my own code, while it works perfectly for IE and Firefox it almost always leaks on Google Chrome. I don't know why this is the case but if anyone has a decent one that works on Chrome or any other of those weird browsers that some people use holla at cha boy