Logs clicks about AdSense or other iframe adverts and buttons.
|Author:||reviewmylife (profile at wordpress.org)|
|WordPress version required:||3.0.0|
|WordPress version tested:||3.2.1|
|Added to WordPress repository:||28-09-2011|
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|Total downloads:||7 063|
Click to start download
Ad Logger from advancedhtml logs data about iframe clicks – it can log clicks from Google AdSense, Amazon Affiliates, Facebook Likes, Twitter Tweet button, and Google’s +1 button. It does this without modifying your ad code – it uses other accessible events to estimate when the ad has been clicked. This method is about 80% accurate.
It logs the page, IP, browser, referrer, and dimensions of the clicked iframe to your MySQL database. You can then get reports showing which pages generated the most clicks, where clicking visitors came from, and who is clicking your ads the most. The data and reports are loaded using AJAX so you can browse the data without refreshing the UI.
Logs clicks without modifying the iframe
No modifications are made to your adverts/iframes which should (hopefully) enable you to use Ad Logger without breaking any TOS from your ad provider.
AJAX table reports
You can view the raw log information in a table, and also view summary reports showing which pages were most clicked, which IPs did the most clicking, what types of ads were most clicked and more.
You can also filter the results. e.g. you can click on the arrow next to an IP address and you’ll see all the clicks that came from that IP address.
Block AdSense ads if too many clicks appear – basic click bombing protection
If you insert your AdSense ads using Ad Injection 18.104.22.168+ you can configure Ad Logger to block these ads if too many clicks come from the same person within a set time frame.
Dynamically remove ads – basic click bombing protection
Ad Logger can dynamically hide a named div after the click count is reached (i.e. the ads would dissapear from the current page without the page having to be re-loaded). These divs will stay hidden on subsequent page loads for the click detection expiry time.
If you do get any errors please use the ‘Report a bug or give feedback’ link on the plugin to send me the error details. If things go so badly wrong that you can’t even get to the settings page please send me an email via this contact form.
The Ad Logger UI showing the data table, options to select which iframes to log, the AdSense click blocking options, and options that allow you to set which fields of data to store and to show on screen.
Why don’t the number of reported clicks match my ad providers reported clicks?
Because they measure different things. This plugin measures ‘raw’ clicks. You ad provider will show you ‘valid’ clicks.
Additionally because this plugin doesn’t modify your ad code it can never be 100% accurate. It may log clicks which didn’t activate the ad link (e.g. if the user clicked on a non-linked part of the ad), and it may fail to log clicks if the browser moves to the new page before the log notification is sent.
From my testing I believe that this plugin’s logged data will be 80-90% correct, but it may vary for you.
How do I use the div hiding feature?
You need to put your ad code in a div whose class name is the same as the one configured in the UI. e.g. if you keep the default div name of ‘adlog-advert’ you would need code like this.
<div class="adlog-advert"> Your AdSense, or other ad code goes here </div>
Can you guarantee me that this plugin is allowed by my ad provider?
Is this plugin allowed by my ad provider?
I’m not going to give you a ‘yes’ – but I think the tracking methods I’m using should be ok. You have to make the decision whether to use it yourself.
Can you make the click tracking 100% accurate?
No. There is no way to do this without modifying your ad codes, and I don’t want to do this as modifying the ad code is not allowed in the TOS of many ad providers.
Can this plugin protect me from click bombing?
Yes it can to an extent, but it won’t stop a determined click bomber.
If a certain number of AdSense clicks has been registered it can prevent ads which are inserted via the Ad Injection plugin from appearing when the page is next loaded. And it can dynamically hide a named div after the click count is reached (i.e. the ads would dissapear from the current page without the page having to be re-loaded).
Will you be adding new features?
Yes – I have lots of plans for new features. You can pass your ideas to me using the feedback link in the plugin.
Some technical details
- Plugin stores all its settings in a single option (adlog_options).
- Logging data is stored in a new table.
- Uninstall support is provided to delete the settings option and logging table if you uninstall the plugin.
- Admin code is separated into a separate file so it is not loaded when your visitors view your pages.
Has anyone written code to do this before?
Yes there are similar commercial projects that do a similar job, but I didn’t look at those because they cost money!
There are public domain projects, and information about how to do something similar. I looked at the following public domain projects, and sites, to get ideas:
No one has put these features into a WordPress plugin until now.
- Better debug screen.
- Fix an incorrect message.
- Validate subquery param.
- If too many clicks are registered a named div class can be hidden dynamically.
- Add a loading circle to the UI.
- Tweaks to prev/next links.
You can now click on the down arrow to filter the tables according to specific matches (IP, type, page, etc).
Fix missing parameter PHP error.
Update messages about click blocking support as Ad Injection 22.214.171.124 is now released.
First public release.