Forum Moderators: martinibuster
What *is* it?
company can get our information like password, etc?
Does anyone know G's stand on this type of software?
[webmasterworld.com...]
[webmasterworld.com...]
It is fine with Google as it does not modify any Adsense code. And man is it good for tracking pages and clicks!
Security wise no tracker can get your Adsense password because their code doesn't use require it.
Copy to your home directory.
CHMOD 666 three files.
Create an empty database with name of your choice.
Run the installer from the yoursitedotcom/adlogger directory
Fill in the details to connect to the database
That's it.
There are two trackers. One is a page/click tracker that is pasted at the bottom of your pages or footer include.
The other is some code that goes before and after your Adsense unit. This code tracks IP addresses, sets cookies, and can set limits on how many times a visitor can click on your ads within a time period you can define.
Warning: mysql_connect(): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) in /usr/www/users/greatstart/adlogger/config_database.php on line 18
Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
Does anyone know what to do for correcting this problem?
remember that the database and user name is not just the part after the underscore.
And don't forget to CHMOD 666 the correct files.
I saw you post on Adloggers forum. How come you didnt get the answer yet?
I've just been looking through the Adlogger forum, and found quite a few others having the same problems.
If Google aren't gonna give us this information, and they are cool with us using tracking scripts, then I think it has a great deal of potential, just maybe not quite yet.
Overall, I ended up removing it because of the following reasons
1) Made management of my pages even harder
2) Another piece of software means another possible exploit vector
3) Depends on the client browser to make additional URL requests, hence causing my log files to grow at a much faster rate and uses up more bandwidth.
I think the software is a great idea, it's just that -for me- it's too much of a burden to take on. For now I'll learn to spend my time writing more good articles and let google watch over my stats.
So far no security problems, couple of minor issues, sometimes it say a user clicked 2-3 times on the ads while after Adsense update I see just one click counted, while couple of times Adsense showed me a click that Adlogger didn’t!
Here is their response. I get the feeling the don't want me to use it.
<paraphrase>they don't endorse any 3rd party products and it is my responsibility to verify any I choose to use</paraphrase>
[edited by: jatar_k at 3:17 am (utc) on June 20, 2006]
[edit reason] no email quotes as per TOS [/edit]
I suggest you pay a few bucks and get Asrep or RevenueMonitor. These both allow you to track everything you need. The Clicks are very close to what Google comes up with too. With RevenueMonitor You also can download all ip's of clickers and how many times they have clicked. This is great for click fraud protection.
That's disappointing, sorry to hear it. The more I think about this, the more I don't get why there isn't some way publishers can configure their accounts in AdSense to do precisely what Adlogger is doing. Has ASA ever commented on this? If so, what did he say?
Thanks Hubbard
If I was making my living from Adsense, I was for sure going to do something like that....
I have previously asked Google if they could block my IP from any accidental clicking and also block any IP from clicks more that once a day. Google sent a generic response about how seriously they take click fraud. They didn't answer properly.
I asked them the same question; I was told that they couldn't allow it because I might accidentally block out some valid clicks.
I'm so stupid that way, and Google knows it.
Let me see if I understand this: Google won't provide publishers the ability to be able to protect their sites from click attacks by offering the same thing Adlogger does because in doing so they "might accidentally block out some valid clicks?" That just does not make sense, sorry. Shouldn't publishers be able to set some kind of threshold - whether that's 5, 10 or 20 clicks per day per IP/computer - to disable AdSense click attacks BEFORE they become a problem? Why should publishers have to resort to third party software like Adlogger to get this kind of protection? Anybody?