Category Filtering beta now available for AdSense for feeds English-language ads

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.

AdSense for feeds now available directly in Blogger

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

14 comments
A small yet noteworthy change to our item stats link serving

Tuesday, September 29, 2009 | 9:09 AM

Labels: Announcements, Feed Optimization, Important Updates, Technical Issues

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.

Adsence for feeds

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

18 comments
AdSense policy clarification on using AdSense for feeds and AdSense for content

Monday, November 9, 2009 | 8:05 AM

Labels: Policy Issues

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.

Better contextual matching

As an AdSense partner, you know that Google is continually making improvements to the way we match ads to your content so that users see even more relevant ads, which should help you make more money over time.

A "referral URL" is one of many signals we use to deliver contextually relevant ads on your website. The referral URL contains information about the link a user followed to arrive at your website, whether from a search engine or another site on the Internet. Any webmaster for any site can look at referral URLs to see how users arrive at their site.

Let's see how this works today when a user arrives at your golfing advice website from a search engine results page. Imagine that someone searches on Google for [golf shop atlanta] and clicks on a search result that takes them to your site. The referral URL that is passed to your site may look something like this: http://www.google.com/search?q=golf+shop+atlanta. I'm using Google as an example here, but the same type of information is transmitted if a user arrives at your website from another search engine.

To deliver the most relevant ad, we treat the query words [golf shop atlanta] in the referral URL as if they're part of the content of your webpage. We can then better tailor the ad we deliver on your site. In this example, we could use the additional information from the query words to show an ad for a golf shop in Atlanta rather than for one in Chicago (depending on the other words in the page).

We've recently started to expand the use of the query words in referral URLs to a few hours so we can so we can continue to deliver more relevant ads. The technical way that we're doing this is by associating the relevant query words in the referral URL with the existing advertising cookie on the user's browser. After a short period of time (a few hours) the query words are no longer used for the purposes of matching ads. Of course, users can continue to opt out of our advertising cookie at any time here.

This allows us to deliver more relevant ads on a wider range of AdSense partner sites that a user may browse over the course of a few hours. Let's assume the user in our example leaves your golf website and browses through to a news website that is also an AdSense partner. Since [golf shop atlanta] is in a referral URL that was visited in the past few hours, we may use those query words, along with the content of the news webpage itself, to determine the most relevant ad to show the user on the news website.

Using signals from the referral URL is just one part of our teams' continuing efforts to deliver even better contextually matched ads on your website.