Qumana is an excellent wysiwyg online/offline tool for editing blogs. We’ve written about Qumana before and described their service, which is completely free.
Yesterday Qumana launched v 2.0 of their product. The primary feature addition is the ability to easily, very easily, add pay-per-click ads directly into blog posts.
Ads can be positioned anywhere, and there are a couple of formatting options to choose from (see arrows in screen shot below). Revenues are split 50/50 between Qumana and the publisher.
Ads are keyword driven based on tags you set for the post, and flow into RSS without any problems. Each Ad is tracked by keyword and clicks. Ads can also be previewed before final posting. The publisher has the flexibility to add as many or as few ads as he or she desires.
There are additional new features as well, including improved old post edits, better drag and drop tools, and better integration with wordpress and blogger.
This is the best tool I’ve seen for small (and large) bloggers to easily include ads in posts.








Michael, thank you for the review.
And in case people are wondering … Qumana is free and using the ad insertion is completely optional. Ads, no ads … still free all the features.
-T
Yep, and to say there are a “couple” of formatting options is quite the understatement. I’m sure people will come up with dozens, if not hundreds, of color combos
Windows only.
I click the download link and they give me an “qumanasetup.exe” to run on Linux. Nice. (sarcasm)
Problems for users in India – AdGenta ads are not served here.
Still no Macintosh Version.
It seems to me that the 50/50 split would make this unattractive to most small publishers. Putting it at 10/90 would encourage a lot more growth and bigger revenues down the road, I would think.
Thanks Ted, we have thoughts in that direction but want to make sure we can get everything rolling first.
Re: versions. Mac & Linux are coming, mid-development.
Re: India. There is filtering happening that we are trying to track down. It’s not from our side, but somewhere in the chain. We intend to strongly advocate for no blocking at all. This didn’t come up in our testing, so we’ll just have to deal with it now
If any more feedback comes in, or if anyone has comments/criticism, we really appreciate it so we can built in improvements. You can reach us all by email. Cheers!