FeedBurner Rick Klau interview Part 2
Rick and I will be doing a podcast answering any remaining questions. Keep ‘em coming!
Why isn’t the blog used more to educate people? It seems like it’s mainly used for announcements.
It’s true that we use our blog mainly for announcements that are applicable across FeedBurner’s wide audience. But your point is well taken and there is a lot more we are doing on that front, and will continue to do. Check out recent posts from Dick, me, last fall’s look inside TechCrunch’s numbers, Brent’s bylined articles in Adotas, the hundreds of interviews we’ve done over the past few years with media publications as well as independent publishers, our Publishers Tips site, or last spring’s podcast market overview as a few examples of educational posts. In addition to our own blog, the publisher team (that’s my team) typically leaves 30-50 comments per week on _other_ blogs so that we’re answering questions people ask in near real time. That way, we don’t force people to come to us to get educated about how we work… if they ask, we’ll answer.
I want to know what happened with the Pageflakes thing. How was it resolved? What measures were put in place to stop it from happening again?
This question is referring to a bug where, in certain cases, they were over-reporting the number of Pageflakes subscribers to a given feed. In that case, we contacted Pageflakes, they acknowledged the bug, let us know when it was fixed, and we resumed reporting the Pageflakes data. While we obviously have no control over how web-based aggregators collect and/or report their data, our algorithms are often able to detect anomalies in the data we receive that allows us to proactively reach out to those services to verify the information we’re seeing. When we establish that things are out of whack, we disclose the issue (e.g. this example) and wait until things are resolved before resuming inclusion of their data in the overall reports.
Is it possible to export data and if not will it ever be?
Yes, click “export” from the “Analyze” tab. Data’s available in Excel or CSV format.
What are their privacy policies? The company I work for is starting a blog in Feb. The very first thing they would question is who has access to the stats and what precautions can be made to ensure privacy. I read on a blog that by not checking one thing stats could be pulled through the API.
I thought FeedBurner had a content network? Can’t find it from the front page.
Since different people mean different things by “content network”, I’m not sure how to answer this. We have FeedBurner networks available to publishers who want to aggregate their content – currently in beta, details are here.
As a blogger am I able to opt out of my site’s data being used for advertising purposes? Data collection?
By default, FeedBurner users are *not* in the ad network, so their data is not used for any advertising purposes. Since the primary reason bloggers use FeedBurner is to collect data about their feeds and sites, I’m not sure how to address a desire to opt out of data collection, so perhaps we need to do some follow-up on this.
How secure is the FeedBurner service for bloggers?
For commercial use if we decide we do not want to use the service any longer what happens with the data collected from our visitors?
You may export your statistics (via the export feature described above) and delete your account. We do not keep any data once an account is removed from the service. Let me take a minute to address another aspect of leaving FeedBurner that wasn’t asked here but is often asked: specifically, what happens to your subscribers once you choose to leave FeedBurner. They’re your subscribers, we don’t want them after you leave. So we’ve gone to great lengths to ensure that your subscribers will follow you after you decide to leave (visit the link for more details).
Will performance be an issue if my site receives a large spike in traffic like Digg?
One of the many reasons publishers choose to use FeedBurner is to offload all bandwidth relating to their feed traffic to us. We manage more than 500,000 feeds, including thousands of feeds for 7 of the 10 top newspapers in the country, 3/4 of the Technorati 100 most popular blogs, and many thousands of high-traffic feeds. With more than a quarter billion feed requests per day, we maintain a high availability server infrastructure, and MySQL has used us as a case study (see this to show how MySQL can be used to power high demand environments like ours). We consistently keep our server farms at fractions of their total capacity, and our connectivity is structured in a way that were we ever to need to spike well above the hundreds of megabits of sustained connectivity we currently use, we could do so without any impact on overall performance.
Which is a long way of saying, “No.”
Why does the FeedBurner count increase dramatically after I am Dugg, then goes down a couple of days later? Did I lose all those visitors?
This is primarily an artefact of prior versions of Firefox (1.5.x and prior), where requests to the feed are labeled the same whether coming from the browser or the feedreader (LiveBookmarks). As a result, we would have to infer from the traffic patterns (i.e., polling intervals, IP addresses, identical user agents) to determine whether the access to the feed was a one-off (i.e., browser) or a repetitive request (i.e., the feed reader). Because of the high concentration of traffic that a site receives when Dugg, those inferences are often impossible to get 100% correct – so some one-off accesses end up looking like repeated requests, and our algorithms count them as subscribers instead of browser views. Recently, the Mozilla team added a unique user agent for the feed reader in Firefox 2.0 (per FeedBurner’s request), which means that these anomalies should be far fewer from now on.
What do they think needs improvement? Can they talk about future plans? They also seem like they are all over the place. What do they DO? Is it feeds, advertising, what is it?
Wow. Let’s see: what needs improvement? Everything. We want the web audience at large to be more comfortable with the notion of subscribing to media feeds. We want publishers to get more value from their feed content by adding more functionality. We want to see creative developers build more cool stuff using our open APIs. We want to sell more ads, so our publishers can make more money. The radiators in our office are maddeningly spotty, so we never know when to dress warm, so that’d be good to fix while we’re improving things.
As far as futures, we’d like to see the Bears win the Super Bowl. A Cubs/Sox World Series would be totally cool, too. On a more serious note, we’ve recently stated that further integration between our feed and site stats is in the near future, as well as a platform for measuring all aspects of content consumption: in a feed, on a site, in a widget, or via some new thing that doesn’t have a buzzword attached to it. However content is consumed, we’ll measure (and monetize) it. Expect to see a lot from us on this in 2007.
Regarding the ‘all over the place’ comment, our goal is simply this: FeedBurner aims to be the world’s foremost provider of online media distribution and audience engagement services. We want to help content publishers, be they independent bloggers or podcasters, blog networks, or commercial publishers – to distribute their media further, engage and build their audience and ultimately, make money. We think we’re in the best position to understand, measure and enhance the distribution of content – via feeds, resyndication, widgets, and who knows what comes next – and then, for publishers who want to capitalize on that understanding, we offer a monetization platform with our advertising network.