Using MyBlogLog could get you banned from Adsense?

Well, that is the opinion of Duncan Riley, Jennifer Slegg and Webomatica, after Shoemoney wrote about how MyBlogLog is specifically tracking clicks on Adsense ads and, the fact that the Google AdSense Terms of Service it states that we’re not supposed to disclose “click-through rates or other statistics relating to Site performance” to third-parties.

Yes, I can certainly see the logic in that and, knowing how sharp Google is on violations, I can certainly see why people would jump to be “on the safe side” and remove MyBlogLog code because an Adsense account is too valuable to risk. (I took the code off overnight - I like to sleep now and again - until I could research this more thoroughly today.)

On the other hand, I will say that this has always been the case: I have seen Adsense mentioned in the listed outgoing clicks ever since I first used MyBlogLog when it was new. I can also confirm that this is not just a Pro feature, because the information is listed in my free account and, there has never been anything hidden about this feature.

Whilst I suppose this may have not been generally known until Shoemoney pointed it out, I had a very hard time believing that Google’s engineers were not aware of this fact and, indeed MyBlogLog themselves state on their blog that, “Google has acknowledged this feature (without protest).”

MyBlogLog’s Eric Marcoullier points to the distinction being that the data collected independently by MyBlogLog is not subject to the confidentiality restriction that applies to the data collected by the Adsense program.

So, referring back to the Google AdSense Terms of Service, point 7. Confidentiality, yes it says that “You agree not to disclose Google Confidential Information without Google’s prior written consent.” Then it spells out what “Google Confidential Information” includes.

But later in the same paragraph, it goes on to: “Google Confidential Information does not include” […] “information that has been (i) independently developed without access to Google Confidential Information, as evidenced in writing; (ii) rightfully received by You from a third party”.

And my personal judgement (disclaimer: this is my opinion, please confirm yourself) is that either or both of those latter cases applies to the data obtained by MyBlogLog.

The possibly precipitous reactions on one side and the speculation on what might (or might not) have been anyone’s underlying motivation, is, to me, merely an amusement, but otherwise, Andy Beard sums it nicely saying, “OMG A Tracking Service is Tracking Clicks”. Quite, it should.

Sure, there’s an element of risk in MyBlogLog having this statistical data, but then (in my case and most sites will be similar) so does Google Adsense, Google Analytics, StatCounter, Site Meter, Quantcast, my web host and Uncle Tom Cobbley and all have at least some of this data too.

MyBlogLog data is very useful, because it helps me greatly to determine what content is popular on my sites, in order to provide people with more of what they want. Arguably, similar information can probably, mostly, be found using Google Analytics but the way MyBlogLog shows the information at a glance, plus the social aspects give it the edge for me.

Yet, if this proves to be wrong, the code can come off again.

For what it’s worth, my thoughts on the earlier exploits that Shoemoney uncovered were that they are things to be aware of, but I didn’t see them as being worrying, because we have a choice in this fast paced, constantly changing world. We can have innovation with bugs, or we could have perfection with stagnation. Google themselves are probably the best example that innovation in permanent BETA wins!

Using MyBlogLog could get you banned from Adsense

Posts that contain MyBlogLog per day for the last 30 days.