How to hide referral info?

Rumpelstiltskin

New member
Feb 28, 2010
91
1
0
I picked an offer, created a website and LP, set up ads on a traffic source and am doing a final check before I launch my campaign.

How do I hide my referral info? Can I just route the offer url through prosper202?
 


Thanks, but that requires me to set up a separate domain and pass the urls through it. Since I already have prosper up, can I pass the urls through that instead?

yes. just remember to cloak your links and your referer will show as the domain that your prosper is installed on.
 
Something like this

redirect.php

<?php

//$url is your affiliate url link

$url = "http://www.loseweightworkingfromhomeeatingberries.com" . $_GET['SubID']
?>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="refresh" content="3;url=<?php echo $url; ?>"/>
</head>
<body>
<div style="height:300px;line-height:300px;text-align:center">
<center><a href="<?php echo $url; ?>">JavaScript is not enabled. Click here to continue to offer.</a></center>
</div>

<script type="text/javascript">
<!--
window.location = "<?php echo $url; ?>"
//-->
</script>
</body>
</html>
 
^ I missed him speak but apparently Wes at the A4D meetup said that your referrer can still leak using a double meta refresh. 202 can strip it by passing it through some sort of form submit. Also he suggested using https.

This information courtesy of Alex who shared his notes with me after I disappeared.
 
note: form submit fucks up if the network uses meta refresh to redirect the offer
 
You can make your second meta page redirect to a dummy page if the referrer wasn't cleared.

^this

Check the referrer on the second page. If it's null send to the offer, otherwise send to some bullshit page.

You will lose a tiny bit of traffic, but the referrer should never be passed.
 
^this

Check the referrer on the second page. If it's null send to the offer, otherwise send to some bullshit page.

You will lose a tiny bit of traffic, but the referrer should never be passed.

As long as you don't care about losing some visitors...

You can find additional info on: Referer.us Premium URL Redirection

Someone sent me this recently and it has some cool information regarding cloaking there.


----

1) This is the first redirect we use instead of "only just using an instant meta-refresh redirect," it's a javascript form post redirect.

2) We then would follow this with a javascript window.location redirect. We use backup meta-refreshes with a 1 second delay, if the user doesn't have javascript.

--


<html>

<!-- Replace Google with whatever url you like !-->

<head>
<title>Google</title>
<meta name="robots" content="noindex">
<meta http-equiv="refresh" content="1; url=http://google.com">
</head>
<body>

<form name="form1" id="form1" method="get" action="http://google.com"></form>
<script type="text/javascript">
document.form1.submit();
</script>

<div style="padding: 30px; text-align: center;">
You are being automatically redirected to Google.<br/><br/>
Page Stuck? <a href="http://google.com">Click Here</a>.
</div>

</body>
</html>


---

This is what referer.us uses, they won't send the visitor if it's not cloaked. But again you have to ask yourself if you really want to lose certain visitors. Their flash thing looks interesting.

This is what this service is all about, deliver absolutely any NO-HTTP-REFERER in any circumstance. DMR (Double Meta Refresh) is last year's technology, but we use quadplex referer removing tactics, which include Meta Refresh, Javascript Location Replace, iFrame Parent Post and Flash getURL Function. We will repeatedly check referer remover results and will only redirect a url after HTTP-REFERER got successfully removed.



If you use double-meta refresh you'll most likely lose alot of visitors because the cloaking will fail alot with that method. There are alot of browsers and many different versions of those browsers which all handle their referrers differently: http://referer.us/browser-platform-compatibility.html