Quote:
Originally posted by NetRodent
100 whiney webmasters complaining about shaving.
Third party affiliate programs are NO PROTECTION against shaving. Consider the following two scenarios:
1). Your sponsor has two CCBill (or any third party system) accounts "A" and "B". The sponsor has an affiliate program on account "A". You send your clicks through CCBill's counter/cookie script using your affliate id from account "A". Your sponsor sends some of your traffic to account "A" and some to account "B". You get credit for only the signups on account "A". Anything that goes to account "B" you don't get credit for.
2). You send your clicks through CCBill's counter/cookie script, using your affiliate id. Then after your traffic hits your sponsor's site he redirects some of it back through the counter/cookie script under a different affiliate id before send it to his join page. You only get credited for all of your clicks but only some of your joins.
It took about two minutes to think up those two scenearios. There are probably several more, especially when you through multiple billing companies, payment methods, multiple sites, etc. into the mix. If a sponsor wants to shave you, you can't do anything to stop it. If you think third party is some magical solution you're an idiot.
The only way to limit your exposure to shaving is to shop your traffic around from one affiliate program to another until you find the one that pays you the most. Then continue shopping around
a portion of your traffic so you'll always know who will pay you the most at any given time.
|
mmm, shouldn't be to hard for a sponsor that uses CCBILL to cheat/shave, but on the other hand it would be easier to detect.
I guess an i-f-r-a-m-e on the tour with another ccbill affil code url would do the trick?
On the other hand its possible that CCBILL protects against this? (by not overwriting a cookie very recently set)
Anyone tested this?
And if its really detected, it would be black on white proof that this sponsor really shaves since the sponsor somehow needs to get another (read: his own) affilcode into that CCbill cookie before the surfer hits the CCBILL signup page.