Gumux Ranger Other Side |
- Saying goodbye to the AdSense for Feeds blog
- Your stats, right away
- Enabling social sharing with FeedFlare
- Socializing your feed with Twitter
- "Afternoon, Frank." "Hey howdy, George."
- AdSense policy clarification on using AdSense for feeds and AdSense for content
- AdSense for feeds now available directly in Blogger
- A small yet noteworthy change to our item stats link serving
- FeedBurner Terms of Service Update
- Category Filtering beta now available for AdSense for feeds English-language ads
- What's all the hubbub about PubSubHubbub?
- Happiness is more subject in your subject line.
- Be it declared, a map for every feed!
- Redirecting your feed to maximize revenue potential
- New features for advertisers targeting feeds
- Universal Exports, at your service
- Feed Stats Processing Caught Up
- An important reminder for our MyBrand users
- Ad Review Center is now available for Feeds
- More details on moving to a Google Account
- Intro to Feed Placements
- The 411 on the 502
- Los colores bonitos, or how I learned to stop worrying and compare multiple feed metrics.
- Additions and Attractions for Our Feeds-by-Email Service
- Using the Competitive Ad Filter with AdSense for feeds
| Saying goodbye to the AdSense for Feeds blog Posted: 26 Jul 2012 11:15 AM PDT Thanks to everyone who has been a loyal reader of this blog over the years. After some consideration, we recognize that we're just not generating enough content here to warrant your time, so we won't be posting here any longer. Thanks again for being an enthusiastic FeedBurner user. |
| Posted: 25 Oct 2010 12:54 PM PDT 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 |
| Enabling social sharing with FeedFlare Posted: 23 Apr 2010 02:05 PM PDT 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 |
| Socializing your feed with Twitter Posted: 14 Dec 2009 12:40 PM PST 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 |
| "Afternoon, Frank." "Hey howdy, George." Posted: 13 Nov 2009 06:56 AM PST 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. 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 |
| AdSense policy clarification on using AdSense for feeds and AdSense for content Posted: 09 Nov 2009 08:20 AM PST 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. |
| AdSense for feeds now available directly in Blogger Posted: 30 Oct 2009 10:45 AM PDT 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. |
| A small yet noteworthy change to our item stats link serving Posted: 29 Sep 2009 07:47 PM PDT 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. |
| FeedBurner Terms of Service Update Posted: 19 Aug 2009 04:10 AM PDT 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. As a reminder, the advertising portions of the service are now covered by the AdSense Terms and Conditions and the accompanying Google AdSense Program Policies. |
| Category Filtering beta now available for AdSense for feeds English-language ads Posted: 17 Aug 2009 08:33 AM PDT 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. |
| What's all the hubbub about PubSubHubbub? Posted: 10 Jul 2009 11:42 AM PDT 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 |
| Happiness is more subject in your subject line. Posted: 02 Jul 2009 11:06 AM PDT 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.  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. |
| Be it declared, a map for every feed! Posted: 14 Jun 2009 06:51 PM PDT 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 |
| Redirecting your feed to maximize revenue potential Posted: 19 May 2009 12:56 PM PDT 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.
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! |
| New features for advertisers targeting feeds Posted: 05 May 2009 01:42 PM PDT 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. In addition to being able to target feeds with Placement Targeting and Contextual Targeting, which have always been supported, this change will soon allow advertisers to target feed users using Interest Based Advertising across both sites and feeds. 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. |
| Universal Exports, at your service Posted: 16 Apr 2009 10:08 AM PDT 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. |
| Feed Stats Processing Caught Up Posted: 13 Apr 2009 07:16 AM PDT Over the last week, and as reported in the FeedBurner status blog , we experienced a technical issue that caused us to report reduced subscribers from Google Feedfetcher in your feed analytics at FeedBurner and AdSense. Our engineers have resolved the issue, and been able to rebuild stats from our logs such that the totals should now be correct. Please note that in the past, we were not able to correct historical statistical anomalies, but are now able to do so, always using the actual traffic data. No data was lost during this process, nor were any subscribers actually unsubscribed from your feed. All feed content was delivered to all subscribers who wished to view the content, regardless of the numbers reported. Ad impression reporting and revenue were unaffected by these subscriber reporting issues. We apologize for the inconvenience and appreciate your patience as we continue to merge our systems with other Google systems behind the scenes. |
| An important reminder for our MyBrand users Posted: 09 Mar 2009 12:58 PM PDT As we detailed in our previous installment, More details on moving to a Google account, if you used the MyBrand service at feedburner.com — our service that allows you to use a custom domain with your feed — you must move to a Google account and update your DNS CNAME records by March 16, 2009, or else your MyBrand URLs will return a 404 "page not found" error. It's important to note that it is not enough to just sign in with a Google account and request to move your account if you use MyBrand. Even if your MyBrand-ed URLs have continued to work after you have completed your move, they will cease to work on March 16, 2009 if you have not changed your DNS CNAME. If you plan to continue to use MyBrand, you can find detailed instructions for changing your CNAME when you are signed into FeedBurner in the My Account > MyBrand section. If you haven't already moved from feedburner.com to a Google Account, please sign in to your account and follow the guided steps to complete this move. Here's a quick preview of those steps (click to zoom in):  (In the image above, you'll see the phrase {YOUR_CODE} in the instructions. This is replaced by an address that is specific to your Google Account available on the aforementioned MyBrand page; you need to use that address to update MyBrand correctly.)If you have any questions about this transfer process, please refer to the FeedBurner Help Center entry "Transferring FeedBurner Accounts to Google Accounts FAQ" for additional details. |
| Ad Review Center is now available for Feeds Posted: 04 Mar 2009 08:22 AM PST  The Ad Review Center (ARC) will give you more transparency and control by enabling you to approve or disapprove placement targeted ad creatives before they appear in your posts. To get started with this tool, please login to your AdSense account. You will find ARC in the 'Competitive Ad Filter' section located under the 'AdSense Setup' tab. If you are using your AdSense account for other products- content, mobile, or video- please make sure to select the Client-ID starting with ca-feed-pub. In order to maximize your revenue, we suggest that you keep the default setting to, 'Run ads immediately.' This will allow ads to run without delay while still allowing you to login and review the ads at a later time. By selecting the 'Hold ads' option, you could potentially decrease your revenue. This option will hold ads from displaying for 24 hours, thus limiting the number of advertisers' driving up your auction price. You will then have the ability to approve or block a specific ad or advertiser in general. These settings can be changed at any time. Please keep in mind that blocking ads will remove them from the auction and could impact your revenue. For more information about using the Ad Review Center, please visit our Help Center. |
| More details on moving to a Google Account Posted: 23 Feb 2009 08:22 AM PST Many of you have already moved from a feedburner.com account to a Google Account. For those who have not yet made the move, there seems to be some confusion on the process and exactly what will happen, or not happen, by certain dates. We want this post to help clear up any confusion.
From a features perspective, this means the work to transition publishers to Google will be complete, and we plan to focus all of our resources on building new and exciting publisher tools that are integrated with other Google products, and to continue improving the monetization potential of AdSense for feeds. We can't wait for you to see some of the things we have in store, but if for some reason you do not want to migrate to a Google account, you can still take your feeds with you. |
| Posted: 06 Feb 2009 12:07 PM PST In times like these, we know that generating as much revenue as possible is on many publishers' minds. This will be the first of many posts that will hope to explain how to better configure AdSense for feeds to help maximize revenue. Before going into specifics though, it's important to understand a couple important differences in how your subscribers are different from visitors on your website. If you use an analytics package for your site such as Google Analytics, most publishers will see that a large amount of their traffic comes from web searches. Many of these visitors may have been searching for a certain item, such as one of those blankets with sleeves and a hood - let's call it a shanket. You happen to have written about how much you love your shanket, and let's face it, you know how to write with the best of them, so your page ranks high in search results. That visitor may see an ad for a shanket next to your search result but wants to know more. So he or she clicks and reads your post, which seals the deal on this visitor needing a new shanket. You use AdSense for content, which includes ads for shankets that are matched contextually; the visitor clicks; a shanket is sold; and you earn revenue in the process. Your feed subscribers, however, very rarely, if at all, get to your content from a web search. On the contrary, they subscribe to your blog because you write entertaining musings about your family life, and occasionally also write about some of the wonderful products you have come across, such as your shanket. Because of this, the types of advertisers that run campaigns targeted at your feeds are not necessarily the same advertisers that are targeting search users. Instead of targeting keywords that match a search, advertisers wishing to use feed subscribers target placements in the Google Content Network. How do you ensure that your placements are exposed effectively in the Google Content Network? That's the easy part. When setting up new feeds on the AdSense Setup tab, make sure you leave the box that says "Create a channel that allows advertisers to target the selected feed." If you are creating a new channel that aggregates all of your feeds or subsets of your feeds that you would like to show to advertisers (highly recommended), make sure by selecting the "Show this channel to advertisers as an ad placement." In a week or so, these placements will show up in AdWords and some of the other tools used by Google advertisers to target the content network.  Stay tuned for the next installment on Advanced Feed Placement optimization. |
| Posted: 26 Jan 2009 09:44 AM PST As many of you know, since becoming a part of Google in June of 2007, the FeedBurner team has been hard at work transforming FeedBurner into a service that uses the same underlying architecture as many other Google applications, running in the same high-volume datacenters. As a team, we chose this path for one reason: our highest priority is making sure your feed is served as fast as possible after you update your content, and is as close as technically possible to being available 100% of the time. As many of you also know, a month ago we opened up ability for all AdSense publishers to move to this new platform, and just a few days ago made this move available to all FeedBurner publishers. What many of you do not know is that we have been carefully moving publishers for about six months now, looking hard at traffic patterns, debugging issues with these account transfers with publishers and their hosting and service providers, and working with many of our partners (including many other teams at Google) who run feed aggregation platforms to ensure feeds from this new platform are polled and distributed as fast and reliably as possible. (One example: we moved over 100 external Google blogs and their respective FeedBurner feeds over to the new platform as soon as we could; charity (and bug-fixing) begins at home!) We are very aware of our responsibility to the RSS ecosystem. We are aware we host and provide service to not only some of the largest publishers, but also the feed for your site, the feeds that you rely on for mission-critical news and information, and even some feeds government provides to distribute information on a timely basis to their citizens. We know that many of you run businesses that critically depend on your feed being delivered quickly and reliably, and thus have been working with many of you to ensure that these feeds are delivered in tandem with a monetization solution that allows you to continue business as we go through this transition. FeedBurner has the privilege of serving millions of feeds globally that represent an incredibly wide spectrum of content. It is this scale however, that makes our transition to Google's platform technically complex, and as we have started to open up account transfers to all users, it has also amplified the permutations of publisher web server configs, service providers, feed readers, search engines, and so on, and so on. We want to ensure that the time we spend tackling this technical complexity is not mistaken for lack of urgency, concern, or priority. Just as an example, we are aware and have been working on a known issue of returning a "502 Error" or "503 Error" when checking for updates after certain feeds are migrated. This is a very general error message, representing a number of underlying issues, but in many cases it is a service provider throttling or disallowing traffic from Google. Although we came across many of these issues during our testing phase, in reality we knew a lot of these challenges would not fully surface until we released at scale, which we now have and are dealing with as high priority issues within Google. To help communicate these issues and resolutions much more effectively, we have created a new blog and feed that you can subscribe to during this transition period. We plan to keep these around as long as necessary. We may also add features to the site that allow you to report your own feed issue details. The extended team — including both original team members of FeedBurner, newer team members that joined us since we've been at Google, and the rest of Google — is excited about our future on this new integrated-with-Google platform that all publishers will be on at the conclusion of this account transfer process. We are excited because we see the potential for scale and innovation on this platform that will make for a true next generation feed management solution. Most of all, however, we are excited about getting publishers excited for these possibilities as we reveal what we have in store. |
| Los colores bonitos, or how I learned to stop worrying and compare multiple feed metrics. Posted: 17 Jan 2009 05:45 AM PST If you've been knocking about within FeedBurner using your Google Account, you may have noticed that the original "french fry" chart from the Analyze tab of the original feedburner.com is no more. This venerable bar chart, with its green picket fence of subscriber trend results, has been the first stop for many publishers when checking their feed analytics for years. In its place is new green-ness (and blue-ness) that communicates three times as much information in the same space, and sets the stage for more interesting reporting in the future. Here's a snapshot:  This 30-day view now offers the following information:
The relationship between these numbers is the kicker:
 Comparing this chart, day by day, can help you spot where subscribers are coming from (and from what source they have gone missing, should there be a sudden drop). While we're on the topic: make sure you can actually get the reach statistic — meaning, make sure you turn on item-level stats for your feed! They're used to help calculate reach. Visit the Analyze tab, look for the "Configure Stats" option, and make sure the boxes shown below are checked:  (You can, of course, check "downloads," too, if you're a podcaster). As a reminder: to view all feed stats' reports and options, either click the "View Feed Stats" next to your feed's ad unit listing in the AdSense Manage Ads section, or sign into feedburner.google.com and click on your feed's title on My Feeds. |
| Additions and Attractions for Our Feeds-by-Email Service Posted: 06 Jan 2009 08:38 PM PST FeedBurner's email service began delivering updates in April, 2006. The launch was just weeks after scientists determined email and feeds could be safely combined in a laboratory setting. Our public service has since delivered millions of messages on behalf of thousands of publishers, making sure that publishers who want to get the word out can reach the broadest audience possible — including many site visitors who don't already embrace feeds (or feed readers, like Google Reader), but who trust their email inboxes to be the best way to have content that matters most delivered to them. As part of our move to Google infrastructure, FeedBurner has added some new features for email publishers. Most of these are of the under-the-hood variety, but a new set of subscriber list management features will be especially beneficial for publishers with dozens, hundreds, and even thousands of existing email subscribers. Here are features live today for all feeds managed through a Google account:
 These new features are in addition to FeedBurner's classic email capabilities. As always, you may:
Want to use the free email delivery service with your feed? Using the latest improvements to email requires moving your existing feedburner.com account to Google (if you haven't done so already). If you use AdSense, any feeds you set up to use AdSense for feeds will also include ads in emails delivered with this service. Sign in to your AdSense account, click AdSense Setup, then Manage Ads, and then locate an AdSense for feeds unit you have created. Click the "View Feed Stats" link next to this unit to reach your feed's Analyze page. Click the Publicize tab, then Email Subscriptions to view and set up service options. Email subscriptions will be delivered, using your settings, starting with your feed's next update. (If your Google account is already set up to use FeedBurner, you can also get to the "Email Subscriptions" service setup area by signing directly in to feedburner.google.com, clicking your feed's title on My Feeds, and then visiting Publicize > Email Subscriptions.) |
| Using the Competitive Ad Filter with AdSense for feeds Posted: 31 Dec 2008 10:32 AM PST First, Happy New Year to everyone from AdSense for feeds and FeedBurner teams here at Google. Second, this is a quick one - but we get asked this a lot, so we thought we'd cover it. If you currently use the Competitive Ad Filter with AdSense for content, you may also wish to use it with AdSense for feeds. In order to provide publishers with ultimate control, the filter for AdSense for feeds is separate from that of AdSense for content, but operates in the exact same manner. To block competitors ads from showing in AdSense for feeds, login to your AdSense account, go to the AdSense setup tab, and select Competitive Ad Filter. Then make sure you have selected the tab marked "AdSense for Feeds" and enter the domains or partial domains into the text box.  |
| You are subscribed to email updates from AdSense for Feeds and FeedBurner Blog To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google Inc., 20 West Kinzie, Chicago IL USA 60610 | |
0 comments:
Post a Comment