Do you hate delays? Do you think being told to “Please wait…” by
websites, cash machines, call centers, and the doughnut stand
drive-thru guy in the year 2010 is a sure sign modern living isn’t
quite meeting our collective expectations as a planet?
Good news! Today, we will be rolling out a
new,
experimental interface for Google FeedBurner. The real story is
what’s new under the hood, however: the new interface provides real
time stats for clicks, views, and podcast downloads, which means
you can start seeing what content is drawing traffic from feed
readers, Twitter, and other syndicated sources as it happens.
Additionally, if you use the
FeedBurner Socialize service, and your platform
uses
PubSubHubbub or you
ping us
when you post, you can for the first time get stats on how much
traffic your feed items are receiving from Twitter, as well as feed
reading platforms like Google Reader in one place. Again, all
within seconds of posting your content. Ping? Pong! Yep. That
fast.
Your subscriber and reach numbers are still calculated based on a
whole day's worth of requests, and are based on the traffic you
received yesterday and before; but your item stats reflect the
traffic you are receiving right now.
You can access the new interface by visiting
http://feedburner.google.com/gfb/ or logging into
feedburner.google.com and then clicking on the "Try
out the NEW (beta) version!" link at the top.
The best way to see these real time features is to publish a new
post and then switch to the “Last two hours” view to begin seeing
updates.
To access feed management or previous analytics functionality, you
can continue using the original interface at
feedburner.google.com.
In the new interface, we are focusing on two things: our new
real-time stats presentation and getting messages about and issues
with your feed posted to the top-level dashboard, so that you can
better diagnose any issues that may prevent your feed from being
delivered in real time. If you have any comments or questions, look
for the “Send Feedback” link at the top of the page to tell us what
you think.
Posted by Dan Rodney, FeedBurner
Team

Date Published: Oct 25, 2010 - 1:54 pm
Feed content is being constantly distributed via new channels and
endpoints every day. More and more, these new channels
involve sharing your content in social networks and applications
such as Facebook, Twitter and Google Buzz.
Recently, we launched our
Socialize service to help you as the publisher
distribute your feed via social networks, with the first network
being Twitter. If you use Blogger, you can already connect
your feed to Buzz via the "connected sites" link in Buzz.
But it's equally important in the social world to make sure your
subscribers can also share your feed content easily on these social
networks. FeedFlare helps enable this by allowing you to
configure links in your feed that promote sharing. You can
do this by going to the Optimize tab
FeedBurner and
choosing FeedFlare, and then of course, adding some flare.
Now, we won't berate you for only doing the "bare minumum," nor do
we recommend having "37 pieces of flare" in your feed - but we do
think you should express yourself with at least a little flare that
helps your subscribers move your content around these social
networks a little easier.
To that end, just yesterday we enabled the official "Post to Google
Buzz" FeedFlare in our catalog, which easily allows users to repost
your content to Google Buzz, and then automatically updates the
label with the number of times it was posted.
These links appear as so in your feed (though the exact
presentation will vary depending on where your feed is being
displayed):
Also included in our official catalog are "Share on Facebook" and
others that may be relevant for your audience. If you are an
old time FeedBurner user, it may be time to revisit your FeedFlare
setup and add some of these new ones.
In addition, if you don't see the FeedFlare you need, you can
always develop one using the FeedFlare API which is documented in
our
FeedFlare Developer Guide.
Posted by Steve Olechowski, FeedBurner Team

Date Published: Apr 23, 2010 - 3:05 pm
Sometimes you reach across the hedgerow to share with your
nearby neighbors. Other times, members of the
household
move away and yet you can't keep from calling to
remind them to wear a hat and such because it's chilly out. Today,
we're celebrating acquaintances near-and-far by launching the
ability to send your feed to Twitter.
FeedBurner has always been about measuring, managing, and
monetizing syndicated content. Our hope is that by providing one
application in which you can direct your feed in real-time to a
number of endpoints, in this case Twitter in addition to the myriad
feed readers, aggregators, and search engines that we have always
supported, and then following on with providing analytics for
measuring exactly how and where your feed gets distributed across
social media, you can make better and more informed decisions about
how to monetize your content.
Many of our publishers who have tried our Google Analytics feed
item link integration have already noticed that their most popular
feed items have been shared many times on Twitter.
We're now taking our distribution and analytics a step further by
enabling the ability to automatically publish the feed items that
meet your criteria to Twitter, using the
Google URL shortener at goo.gl.
To get started, go to the Socialize service on FeedBurner's
Publicize tab and add the Twitter account to which you would like
to post items from your feed. You can take the default settings and
click [Save] to start socializing immediately, or use the options
we offer to customize exactly which feed items are sent to Twitter
and how exactly you would like them to look. The next time you post
a new item to your feed it will be sent to Twitter (as always, make
sure to
ping FeedBurner whenever you update your feed so
this process happens as near real-time as possible).
For full details on all Socialize options, see our
FeedBurner Help Center topic.
To see the results, take a look at the Twitter account in which you
are sending your updates. This blog post, for instance, as well as
select blog posts from this and the FeedBurner status blog, will
appear from now on at
http://twitter.com/feedburner. If Twitter is where
you are consuming most of the latest content these days, please
follow @feedburner to receive our updates in your favorite Twitter
client.
Posted by Steve Olechowski - Product Manager, on behalf of
the Google FeedBurner team

Date Published: Dec 14, 2009 - 1:40 pm
It's about time these two neighbors got to talking to each other.
Most Saturday afternoons you'd find them politely waving as they
passed at each other by with their push mowers, tending to their
neatly manicured tables, charts, and graphs. It just made sense
that the grounds would look that much more complete if they
removed a bit of fence between them. And so they've done just
that.
If you use either AdSense for feeds or Google FeedBurner to
track item clicks and also use Google Analytics, as of today, you
will automatically start to see your feed item click analytics show
up in Google Analytics with some additional information added to
help you understand how distributing your feed with FeedBurner
leads to traffic on your site.
Specifically, we will help you classify your links by tagging the
Source as "feedburner", the Medium as the channel in which we
sent out your feed such as "feed" or "email", and the Content as
the actual endpoint application in which the user viewed your
feed content such as "Google Reader" or "Yahoo! Mail". In
order to slice your traffic by these endpoints, in the All
Traffic Sources view in Google Analytics select the "Ad Content"
field in the second column.
In the coming weeks, you will start to see many more distribution
endpoints in your reports. The represent ongoing additions to our
database of applications that process feeds.
By default, these analytics will show up in the "All Traffic
Sources" and "Campaigns" views in Google Analytics. You can
filter the results just to only the traffic that comes from
Google FeedBurner by filtering on "feedburner" on the All Traffic
Sources page or "Feed:" on the campaigns view. You can also
use these sources in the Advanced Segments views.
In this view below, we actually have two separate feeds driving
traffic to this blog, and that can now be tracked easily in
one view.
If you have item click tracking enabled, we are now automatically
tagging your item URLs with Google Analytics parameters. If
you're not using Google Analytics, or for some other reason don't
want these parameters in the requests coming to your website, you
can turn off Google Analytics tracking on the "Configure Stats"
page on the Analyze tab at
http://feedburner.google.com. If you don't
have item click tracking enabled, this is also the perfect time
to turn it on, which can be done on this same page.
For instance, if you would rather see the detail of where your
feeds are read directly, you can add ${distributionEndpoint} as
the medium, and then you will get views that look something like
this.
Again this will happen automatically except in one specific case:
if you are already tagging your feed item URLs with Google
Analtyics tags such as "utm_source" and "utm_medium" - we have
disabled this feature and you will have to turn it on manually by
selecting "Track clicks as a traffic source in Google Analytics."
Note that if you do this, we will replace any existing
"utm_" tags that may be in your permalinks with the values
generated from FeedBurner.
In the coming weeks, we will be releasing more features in Google
FeedBurner that take advantage of this functionality, so we
highly recommend that you
register and set
up your site with Google Analytics if you haven't done
so already.
Posted by Steve Olechowski on behalf of the Google FeedBurner team

Date Published: Nov 13, 2009 - 7:56 am
This is just a quick clarification on AdSense for feeds as it
relates to the AdSense for Content specific
policy of only allowing three ad units and three
link units per page.
Many publishers have asked the question "Since feed items often
get displayed with many feed items on a single web page, can
using AdSense for feeds jeopardize the status of my AdSense
account?"
The answer is no. Having three ad units per page is a product
specific policy for AdSense for content. Product specific
policies can be read about
here.
In essence, the variable ways in which feed items are displayed
are controlled and optimized automatically by the AdSense for
feeds application and the choices you make as a publisher in your
AdSense account when configuring your AdSense for feeds ad units.
This means we may automatically suppress ad impressions when we
detect there are too many feed ad units being displayed, resize
ads based on the size and length of your content, and adjust the
ads that are displayed based on the device in which the feed is
being read.
Posted by Steve Olechowski - Product
Manager, AdSense for feeds

Date Published: Nov 09, 2009 - 9:20 am
One of the things our publishers have always asked for are ways
to make it even easer to configure their blogs to work with
FeedBurner and AdSense for Feeds. We're happy to announce that
Blogger users, with just a few clicks, are able to do both at the
same time.
Yes, this year for Halloween, AdSense for feeds is putting on a
Blogger costume and allowing all Blogger publishers to easily
monetize your RSS and Atom feeds directly from the Blogger
interface, in the same way you set up AdSense on your blog
beforehand.
To set this up, go to
Blogger and select the blog you wish to monetize on
your Blogger Dashboard, and select "Monetize." This will give you
some basic options for configuring ads, and if you already have
connected your Blogger feed to FeedBurner, will confirm that the
proper feed is being configured. AdSense for feeds will
automatically pick the right ad sizes for your users, content, and
end medium.

After setup, you will be able to view your AdSense reports
(including feed revenue) directly from the Blogger Dashboard, as
well as from your AdSense account. Additional feed management
options for your feed and feed analytics will be available from
http://feedburner.google.com.
Posted by Steve Olechowski on behalf of
the AdSense for feeds and Blogger teams

Date Published: Oct 30, 2009 - 11:45 am
FeedBurner has been busy analyzing, publicizing, optimizing and
monetizing your feeds since 2004, and in that time, we've seen
our fair share of feed traffic. In fact, we see billions of hits
from feed traffic per week, and we watch this data carefully for
trends and opportunities to improve what we do in making sure
your feed content is delivered as quickly as possible, as
accurately as possible, no matter what its destination might
be.
Today we are making an improvement that we think will serve our
publishers better by making our service more compatible with
search engines that crawl feeds.
When we started the service, one thing we were not sure of at the
time was how the feed reading ecosystem would treat the links we
rewrite in order to give you statistics on how many people click
on your feed items.
For instance, on the previous post in this blog, we change the
link in the feed item for "FeedBurner Terms of Service Update"
from
http://adsenseforfeeds.blogspot.com/2009/08/feedburner-terms-of-service-update.html
to
http://feedproxy.google.com/~r/blogspot/MQiv/~3/Z8Es5QuvgEI/feedburner-terms-of-service-update.html
which sends the browser to that original URL, but allows us to
first track the click.
As a technical detail, we rewrote these links with a code of "302
Temporary Redirect" which tells the browser or consuming service
that the redirect is not permanent, and thus it would need to be
read every time.
As of today we are changing this to be a "301 Permanent Redirect"
because we've looked at the traffic enough to tell that there
some benefit to changing this to a "301 Permanent Redirect" - in
that some search engines that index the feeds themselves will
consider these to be additional links that should be used in
determining the popularity of your site. This is the same way
that "URL shortener" services send traffic and get treated by
search engines, so we feel that this is consistent with the way
that content is distributed today. This update should not
change the number of clicks that come to your site from your feed
nor should it significantly affect the
number of clicks FeedBurner tracks for you.
What do you need to do? Nothin'. Nada. Just keep burning your
feeds from FeedBurner or your AdSense account in AdSense for
feeds, and we will keep working hard to ensure your content is as
accessible as possible – now, hopefully even more so.
Posted by Steve Olechowski - Product
Manager, AdSense for feeds and FeedBurner

Date Published: Sep 29, 2009 - 8:47 pm
As a natural conclusion to the process of migrating
feedburner.com
accounts to Google Accounts as previously described
here, we have decided to sunset the legacy
Feedburner Terms of Service. The
Google Terms of
Service will be the terms that apply to your use of Feedburner.
These Google Terms of Service are the same terms that apply to many
other Google products and services, including your Google Account.

Date Published: Aug 19, 2009 - 5:10 am
Like we
announced on the more general Inside AdSense
blog a couple weeks ago, we have extended our category filtering
beta to English-language ads on the AdSense network, which we are
happy to announce includes ads that appear in AdSense for
feeds.
This feature allows to you filter ads in up to five categories
such as Dating, Drugs and Supplements, Weight Loss, and Get Rich
Quick. Your filters will be applied to English-language ads, no
matter how they were targeted.
To have these settings take effect for your feeds, from Ad Review
Center, make sure you select a Client-ID that starts with
ca-feed-pub. Note that
this allows you to select different categories for your feed than
for your site, but also means you will need to select filters for
both your feed
and your
site in order for filters to be applied to both these content
types.
To see whether category filtering has been enabled for your
location, sign in and visit the
Ad Review Center, located under the 'AdSense
Setup' tab. We're working on expanding this beta to additional
languages and countries, and will be sure to announce any updates
here on the blog. If you'd like to learn more about category
filtering, please visit our
Help Center.
Posted by Steve Olechowski - Product
Manager, AdSense for feeds

Date Published: Aug 17, 2009 - 9:33 am
One of the questions we get from publishers most often is "How do I
make sure updates to my feed are delivered to feed readers as fast
as possible?" We know this is important to our publishers'
businesses and we are constantly making improvements to our
back-end systems to minimize the time from when you publish a post
to when it appears to subscribers in feed readers.
Recently there have been a lot of developments around the so-called
"real-time" web. The promise of the real-time web is distributing
new information as quickly as possible. This encourages users to
engage in more active participation online and makes the web more
dynamic than ever before. However, so far the real-time web has not
been easily accessible by feed publishers using their existing
infrastructure.
Today we're happy to announce initial support in FeedBurner for the
PubSubHubbub protocol. 'Hubbub is an open
specification in draft for web-scale publish and subscribe. The
protocol can be used to transform
any existing Atom and RSS
feed on the web into a real-time stream. Best of all, it's open,
free, and decentralized like the rest of what makes the web so
great: No single organization controls the protocol or how it's
used.
As of right now, burned feeds with the
PingShot service enabled are automatically
enhanced with the PubSubHubbub protocol. We'll add the required
discovery elements to these feeds and notify a
Google-run
Hub, running on
App Engine, of publish events. We also convert any
pings we receive into 'Hubbub events. That means for many of our
publishers out there, your existing feeds are available as
real-time streams right now. Like, immediately. This very
moment.
If you are a publisher and are not already using our PingShot
service, turning it on is easy. From
feedburner.google.com, visit the Publicize tab for
your feed, select PingShot, and click the [Activate] button at the
bottom of the page. From your AdSense account, go to Manage Ads,
then click View Feed Stats link, and do the same thing. That's
it.
If you manage a service that would like to receive updates to the
millions of FeedBurner feeds that use this service as soon as
possible, or just want to know more about the PubSubHubub protocol,
we encourage you to check out
our project on
Google Code. There are open-source clients for Python,
Perl, PHP, Ruby, and WordPress. We have an open-source reference
implementation of a Hub built on
Google App
Engine. And there are
other Hub implementations built and run by other
companies. Please let us know what you think in
the
PubSubHubub Google Group!
Posted by Steve Olechowski, on behalf of
the FeedBurner Team

Date Published: Jul 10, 2009 - 12:42 pm
If a certain lack of variety has weighed on the format of your
day-to-day, feed-to-email deliveries, things are looking up at
last. Recent advances in dollar-sign technology have brought some
strange and fascinating new capabilities to the Email Branding
section of FeedBurner's Email Subscriptions feature. Read on,
ostensibly for the many useful pictures and descriptions, but
really for the danger and excitement only a new checkbox can
bring.
First,
sign
in to your Google Account on FeedBurner and then click your
feed's title, then Publicize > Email Subscriptions > Email
Branding.
Always want to feature the title of the latest post in your subject
line? Just put ${latestItemTitle} in the Email Subject/Title
textbox:
Do you often have more than one post per day? You can help your
readers uncover exactly how many new missives you've got planned
for them in each update. Check the "Change Subject…" box and reveal
a secondary subject line to use when 2 or more feed posts are
delivered in a single email.
Remember, good subject lines command attention in crowded
inboxes.
Behold! The mythical "almost empty" inbox. But in this case, the
most recent post's subject line, thanks to ${latestItemTitle}, is
right in this FeedBurner-delivered email, shining through.
Have fun with this new feature, but please note that
${pithyRetort}, ${iambicPentameter}, and ${heartfeltApology} are
not yet supported.
Posted by Paul Darga and Matt Shobe,
FeedBurner Team

Date Published: Jul 02, 2009 - 12:06 pm
One of the most compelling reasons that publishers choose
FeedBurner is
that it gives them the tools to record and analyze how many users
are consuming their content. Late last week, we launched an
enhancement to our item statistics that enables publishers to get a
bit more information
about those users. Similar to the
feature by the same name in
Google
Analytics, the "Map Overlay" page provides a breakdown of the
previous day's item statistics from a geographic perspective.
For feeds with item stats enabled, clicking on the "Map Overlay"
item from
feedburner.google.com will bring you the page.
From your AdSense account, click on
Manage
Ads and then on "View Feed Stats" for the feed whose map you
wish to view.
At the top, you'll find a world map visualization that shows
countries with more item views as more intense shades of green.
Hovering over a country shows the name of the country and the
exact number of item views.
Below the map is a table, which lists the top 25 countries by
number of item views.
Hopefully, you will be able to use these data to better tailor
content to your readership, and target lackluster markets. If you
are one of our publishers who sells your own ads in feeds using
Google Ad Manager, this will help you better target your
subscribers. Or, just reveling in the world-wide reach of a feed
is pretty satisfying too.
And remember, it's important that you follow our instructions to
make sure you are directing all your traffic
to FeedBurner.
Posted by Greg Kick, FeedBurner Engineering Team

Date Published: Jun 14, 2009 - 7:51 pm
One of the most popular (and recurring) questions our publishers
ask is, "How do I maximize revenue for AdSense for feeds and ensure
my subscriber stats are as accurate as possible?" Some of you can
recite the answers to these questions backwards and forwards
(though we find typing it backwards is quite difficult, so we'll
leave you to say that aloud). But for our many new publishers that
are just tuning in, here's the recap.
Just setting up AdSense for feeds ad units in your AdSense account
is
not enough to start seeing traffic and revenue to your
feeds. It's critical that 100% of your feed traffic be directed to
the feed(s) you created in AdSense for feeds or your FeedBurner
account. Luckily, this is fairly easy to do via two standard
methods.
-
Redirect your original feed. This is the recommended
option for all publishers, but especially if you have an
already established blog or feed that already has subscribers.
This option ensures that all traffic gets funneled to the
version that has both advertising and subscriber tracking
enabled. We've detailed this process in this Help Center entry.

An added bonus: a plugin for self-hosted WordPress
installations and feed-specific features within Blogger and TypePad make redirection much easier on
these two publishing platforms.
-
Promote your feeds.feedburner.com feed. This is
recommended only in the cases where you are setting up a new
blog, or have an existing blog or feed that has no traffic. For
example, if your feed is found at
http://feeds.feedburner.com/toastforbreakfast, you would change
your blog template to link only to this version of the feed.
Note you have to make sure to change it not only where you
promote your feed directly, but also everywhere you have feed
autodiscovery links in your template. (One other place to keep
in mind: BrowserFriendly.)
Hopefully, this reminder will help everyone get on firm ground with
how to maximize traffic to their feed and revenue from it, too. In
future posts, we will be covering how to
increase traffic
and subscribers to your feed, so hang on to your hat!
Posted by Steve Olechowski - Product
Manager, AdSense for feeds

Date Published: May 19, 2009 - 1:56 pm
Along with the
clarification regarding the doubleclick.net
domain we posted a few weeks ago over at
Inside AdSense,
we thought we would mention that we have made similar changes to
the AdSense for feeds ad tags that are being placed in feeds. By
changing our ad serving to the doubleclick.net domain, we are now
allowing advertisers to more easily create campaigns that span
all media platform types on the Google Content Network, including
sites, feeds, and mobile.
By making it easier for advertisers to buy ads in your feeds, and
by supporting the exact same features and ad formats that are
accepted on websites, the competition for your ad space should
increase to help ensure that you're maximizing your earnings
potential.
Posted by Steve Olechowski - Product
Manager, AdSense for feeds

Date Published: May 05, 2009 - 2:42 pm
As feed consumption continues to grow, many or our publishers are
adding more and more feeds to their Google accounts, and wishing
to analyze, publicize, and monetize those feeds through the
combination of AdSense for feeds and FeedBurner. Because of this
trend, one of the most frequent questions we receive is "How do I
export stats for all my feeds at once?"
As of today, you can now export your subscriber, reach, hits,
item click-throughs, podcast downloads, and item views directly
from the FeedBurner application on the My Feeds page. You are
then at your leisure to slice, dice, add, subtract, and even
multiply and divide your stats however you may wish.
As always, aggregate revenue, impressions, and clicks, and eCPM
can be downloaded from your AdSense account or Google Ad Manager
account (if you have been enabled to sell your own direct ads in
feeds through Google Ad Manager) on the Reports tabs.
Also, as a reminder - if you wish to export feed subscriber
statistics in timeframes other than those provided, you can do
that through the FeedBurner
Awareness API.
Posted by Steve Olechowski, Google
Product Managment

Date Published: Apr 16, 2009 - 11:08 am