Does P202 ever leak referrers?
- Thread starter pmarshall76
- Start date
Actually, with cloaking turned on, P202 washes 99.8% of referrers. Yeah, I made that number up, but it is very effective. If you're paranoid, have your outbound link perform a javascript redirect (window.location='offerurl.php') to the prosper link, which then performs a double meta refresh. Hope that helps.
I don't think java redirects do anything. I use them for a lot of my offers (mainly for the frame break) and the referrer gets passed almost all the time.
Just do a double meta refresh where the last redirect checks to see if the referrer is leaked. If the referrer is leaked have the last meta refresh send it to a clean page which, when coming from the referring url that got leaked shows a button saying "click here to continue to your offer", or "before continuing click this button to prove you aren't a bot", and if there is a different (or no refer) it shows a clean page.
That way if the referrer doesn't get leaked they get redirected to the offer and the advertiser doesn't know anything. Then if it does leak it is sent to a page which filters the user right to the offer and looks clean if the advertiser/network looks at it.
That way if the referrer doesn't get leaked they get redirected to the offer and the advertiser doesn't know anything. Then if it does leak it is sent to a page which filters the user right to the offer and looks clean if the advertiser/network looks at it.
You could run people through a service like referrer.us if you're that paranoid about the referrer being leaked.
Do you still mask your referrers on offers that make you reveal them *cough* Flycell *cough*? I thought about it but I'm a little scared to try it incase they decide to cancel all the leads from sources they can't track.
Install a SSL Certificate on your p202 domain and it won't leak - it will never leak. Just make sure you are using the double refresh within p202 - that combined with the SSL cert is what you need to do. Period. End of story.
Brian
Brian
Yes, it does - usually about 10% and when it leaks, it leaks the P202 redirect URL. Very very rarely the landing page. I suggest to all my publishers to use cloaking because EWA simply does not want to see the information / landing pages / traffic sources.
I'm trying to use something like that so it's a double refresh along with a check at the end just to make sure. It works in Firefox but IE and Safari both start bugging out at the second php page.
