No Country for Old Text Ads...

I don't know why this never sank in. I think it went in one brain cell and out the other. Last year, around November, Google changed the clicking behavior of their text ads for Adsense. It used to be that you could click on the title, link, or the description portion and it would click through. Now you can only click on the title portion.

The net effect of this, according to the pundits, is that clickthrough rates for text ads went down up to 60%. Clickthrough rates go down, revenue goes down.

However, image ads remain 100% clickable. The solution? Change your setup to serve only image ads. Now that the quality of google's image ads has generally improved, it should not be an issue.

If you are using their new Custom Channels, you can actually do this without having to change any of your ad code that's in your pages.

As a general rule, it's a good idea to watch your CTR and eCPM figures carefully after making such a change - it doesn't work the same for every implementation.

Jeesh!

Comments

  1. Dennis Gorelik10:08 PM

    Peter,
    1) May be this is the reason that change in click-through rates was not widely discussed:

    https://www.google.com/adsense/localized-terms
    =====
    You agree not to disclose ... (b) click-through rates or other statistics relating to Property performance in the Program provided to You by Google;
    =====

    2) What's your experience with image-only ads? Did it bring CTR and Page eCPM back to normal?

    3) I don't like image ads. They are annoying.

    4) There could be another reason why CTR dropped. With time users are getting used to ads, so they click less.
    You may consider changing ads positions a little, though it's tricky play.

    ReplyDelete
  2. peterbromberg7:05 AM

    Dennis,
    your comment in 1) seems a little hair-splitting. The discussion about click-through rates declining after a change by Google was quoted from others ("pundits") and is not specific to an individual account. Further, Googles "confidential information" states that it does not include info that has become publicly known, or independently developed.

    I don't particularly like image ads either, but they have improved in quality, so that's more of an individual choice.

    You should be able to get some people's opinions about CTR etc by searching around.

    ReplyDelete

Post a Comment

Popular posts from this blog

FIREFOX / IE Word-Wrap, Word-Break, TABLES FIX

One of the most annoying things a developer (who would normally delight in writing code, not futzing with markup) can have is getting rendering issues between different browsers. The two biggest players are of course Internet Exploder and Firefart (as I lovingly like to refer to each). In most cases that's going to take care of 98 percent of your total site traffic. IE has had a proprietary "word-break" style attribute for a long time, and this made it into the CSS 3.0 spec. But that doesn't necessarily help you with Firefox right now. Firefox literally - (and I consider this completely idiotic, since it's been in their bug database for FIVE YEARS) does not have a reliable CSS style element to force table cell content to break in the middle of a word in order to stop the content from expanding your table / div off the page or over other content on the page. Here's a partial fix, which will work for most tables and browsers. The style declaration (I call it m
Read more

Some observations on Script Callbacks, "AJAX", "ATLAS" "AHAB" and where it's all going.

I've taken a more than cursory interest in the whole Remote Scripting (.NET species) vs. AJAX and now ATLAS discussion, mostly because I started using Remote Scripting since Microsoft first released it, and because I continued to refine it after seeing Brent Ashley's excellent work with JSRS, which was one of the first "real" cross-browser solutions back in 2000 (that's the turn of the Century for you history buffs). Now Bertrand Leroy, a Microsoft guy whose work I like , has authored some very interesting ASP.NET 2.0 script callback stuff that he points to on his blog, and he is obviously (at least, to me he is) involved quite heavily in the development of this new ATLAS infrastructure that they'll preview at PDC. Leroy's most recent post brings to the surface what I agree are the major differences between the "AJAX a - la .NET" approach as popularized by Michael Swartz with his AJAX.NET library, and Leroy's RefreshPanel, the ASP.NET 2.0 b
Read more

FIX: Requested Registry Access is not allowed (Visual Studio 2008)

Symptom: in Visual Studio 2008, you attempt to add a new WebContentForm and associate it with a MasterPage. You receive an error dialog "Requested Reqistry Access is not allowed". Don't ask me what caused this; I'm guessing that the registry keys involved had their access denied due to removal of a previous version of Visual Studio, leaving the new guy (Visual Studio 2008) in the lurch. Here's the fix: Download "subinacl" here . This is a command-line tool that enables administrators to obtain security information about files, registry keys, and services, and transfer this information from user to user, from local or global group to group, and from domain to domain. After installing subinacl.exe (it will be in the C:\Program Files\Windows Resource Kits\Tools folder.), drop to a command prompt and run the following batch file, which you have saved in the same folder with the filename "FIX.bat": subinacl /subkeyreg HKEY_CLASSES_ROOT\VisualStudi
Read more