Feedburner, which I use to manage and follow my non-existant readership, has recently prompted me to convert to feedburner.google.com. Apparently though, I don't get to keep my per-page stats. And other users have been reporting their own issues.
So where I used to be able to use Feedburner to figure out what pages were getting hits, I am unable to see that kind of stat on the new feedburner.google.com.
Do I really need to run multiple stat engines, google peeps? What gives? For the moment, I'll have to look into my own aggregating and so-on. It could be that something django/rails-y could get whipped together to aggregate my own feeds and stat count. And there's always StatCounter.
So where I used to be able to use Feedburner to figure out what pages were getting hits, I am unable to see that kind of stat on the new feedburner.google.com.
Do I really need to run multiple stat engines, google peeps? What gives? For the moment, I'll have to look into my own aggregating and so-on. It could be that something django/rails-y could get whipped together to aggregate my own feeds and stat count. And there's always StatCounter.
Leave a comment