|Click Fraud Protection for Publishers|
Can they be stopped?
Certainly someone, somewhere has written software to monitor/prevent click fraud for the publisher. Most of what I find is for the advertiser to find out they've been robbed, after the fact.
But how about software that can:
1. Determine if an IP revisits a page within a number of seconds? Then when the same IP comes back, a script runs and disables the G ads temporarily, not by messing with G's code, but rather commenting it out for that IP.
2. Determines the origin of the IP address
3. If IP is Non-US, then permanently block ads from it.
4. If IP is rotating US, then block it for a number of hours/days.
Am I dreaming?
Be kind, now. I'm a visionary.
Hey, if one must dream always dream big!
It is possible to make, just use PHP to do the checks and if there an issue, don't echo out the adsense code, echo something else.
What about clickbots that use multiple IP addresses?
What do you mean by "fraud" exactly? Fraud in an AdSense context would be a publisher generating revenue by generating artificial clicks on ads, thereby defrauding the advertisers. This is easy to prevent (for the publisher at least) ;-)
If you want to prevent "click attacks" generated deliberately by a third party, the mechanism will not help, as anyone with malicious intent only needs to get hold of one page on your site with your AdSense code in it.
Otherwise you've just described an ad-rotation system which will reduce AdSense impressions, with the added side-effect of eliminating potential revenue from non-US markets, particuarly from the other industrialized, English-speaking countries (such as the nation on your northern border whose name begins with 'C').
If you can describe the problem you're trying to solve in more detail, I'm sure the combined brainpower of this forum can come up with solutions, even if only theoretical ones.
I had a few clicks I didn't get credit for because Google's click fraud software tagged them as fraud. Since I don't click on my own ads, and since I don't even tell people I know about my site, I can only assume it's someone that was messing with my page clicking ad after ad. This is the first time this has happened.
My account wasn't suspended, but the credit was removed nonetheless. I contacted Google to see (for sure) what the problem was. I wasn't sure if they were PSA's or CF. But they told me their fraud monitoring caught the clicks and pegged them as fraud.
I knew when I set up this site that I shouldn't bank on the AdSense income. (I have another plan for the long haul) There's a lot of competition in this market as it is a high dollar click through industry. After all the reading I've done, I figured I'd give it a try and just hope for the best.
I don't want to be a victim of sabotage, or even a nervous finger.
Just to clarify what I wrote:
|Fraud in an AdSense context would be a publisher generating revenue by generating artificial clicks on ads, thereby defrauding the advertisers. This is easy to prevent (for the publisher at least) ;-) |
This means the only actual "fraud" which is possible in the context of AdSense is the site publisher clicking on his or her ads, which is "easy" to stop in that you simply just don't click on your own ads ;-), even accidentally.
|I don't want to be a victim of sabotage, or even a nervous finger. |
Deliberate sabotage by a third-party is impossible to prevent. It's highly unlikely that some random person is going to launch a click-attack on your site. If there's someone out to damage you personally, they only need one block of your AdSense code... (In that case your best defense is a squeaky-clean site and knowing how to read your server logfiles.)
Also remember it's possible the "fraudulent" clicks (did Google actually lable them as "fraud"?) may have been a result of the clicker's activities on another website, and Google deciding to invalidate all clicks from that IP / browser.
Unless you have something specific to worry about though, I wouldn't worry too much, and concentrate on building your site, keeping an eye on the server logs and any other traffic information at your disposal.