How Yahoo's RSS Advertising works

Freshness Warning
This article is over 13 years old. It's possible that the information you read below isn't current.

Here’s a look at how Yahoo’s RSS ads work and a comparison to the ad insertion techniques of some of the other players — Google, Pheedo, and FeedBurner. Feedster wasn’t able to get me a publisher account in time for this article.

Disclaimer, I was a founder of Pheedo and although I no longer work there, I still own stock.

If you’ve got a Yahoo Publisher Network beta account, then you’ve got access to Yahoo’s RSS ad server under your “Ad Setup” tab. The setup is nearly identical to Google’s implementation of RSS advertising, so I’ll make some comparisons as I describe Yahoo’s service. Yahoo asks you to select your publishing platform, giving you a choice of Wordpress or Movable Type and then generates some HTML that you insert into your feed items. Like Google, the HTML code is a link and an image, both with query strings containing embedded MT or WP tags. The query strings assign a unique ID to image and link and tells Yahoo your item permalink URL so it can be used contextual matching. The only real difference between Yahoo and Google is what they use for a unique ID; Google uses the entry date and time and Yahoo uses the numeric entry ID.

Both Google and Yahoo (as well as Pheedo and FeedBurner) serve text ads typeset as an image. The user has an image file delivered to their reader, but that image contains only text and looks to the end user like a simple text ad. The reason for delivering text ads as images is to be able to rotate ads. Without using an image, once a bit of text is inserted into a feed, there’s no way to change it without changing the feed’s source.

With Yahoo, the entire ad unit links to the advertiser site, but Google uses image maps to link a portion of the ad to the advertiser and a portion to Google. With either company, if you can’t handle cookies, clicks on ads fail. This is because Yahoo and Google change the ad each time you load it and track which ad you saw through a cookie. Don’t have cookies? Then they don’t know which ad you just saw and redirect your click to a non-advertiser page (Yahoo sends you to their Publisher Network signup page). This is a bigger problem than you might expect. Many desktop readers send clicks to an external browser. What this means is that when the ad server delivers the “you saw this ad” cookie to the feed reader, that cookie isn’t available to the external browser. When I see an ad in NetNewsWire and click it, Firefox opens up. Firefox doesn’t know about the cookies NNW has seen, so I get the error page instead of the advertiser page.

Pheedo has solved the problem with readers that don’t accept cookies by having a default ad that rotates very infrequently. Users not accepting cookies see this default ad and clicks without cookies go to that advertiser. But they’re still susceptible to the external browser problem. In a way they have a larger problem, since the ad server thinks that cookies are accepted and serves an ad, but then can’t find the cookie on the click and charges the click to the default advertiser.

Google, Pheedo, and Feedburner all serve text-based ads exclusively, but I’ve seen a couple of graphic ads on Yahoo — mainly as the default ad that gets shown if you aren’t accepting cookies.

Although Google and Yahoo only offer ad code for a limited number of blogging platforms, anyone can easily look at the sample ad code and deduce a recipe for plugging it into alternate content management systems. All you need to do is stuff a unique ID and the URL of your entry into the proper places in their code.

Both Yahoo and Google insert an ad inside every RSS item you publish. Adding their RSS ad code to your feed will mean that every item will contain advertising and that some items you’ve previously published will re-appear in your reader’s feed readers.

Pheedo and Feedburner each require that they host your feed in order to insert advertising. They monitor your feed for changes and then republish your feed content with advertising added. Each also offers feed analytics alongside their advertising services, providing information about feed reach, item popularity, and your feed readership in addition to the standard advertising reports. Each of their ad servers inserts ads in a similar manner to that of Google and Yahoo, only in an automated way. This means that if they chose to, they would be able to offer their publishers the same sort of copy and paste ad insertion as Google and Yahoo. Doing so would hamper their ability to provide you with feed analytics services, however.

harry
November 17, 2005 7:57 AM

adding some ads like google adsense on the webpage is ok, but insert those things in an Rss feed is abusolutly annoying.this is especially true when you booked heaps of RSS feeds

Your comments:

Text only, no HTML. URLs will automatically be converted to links. Your email address is required, but it will not be displayed on the site.

Name:

Not your company or your SEO link. Comments without a real name will be deleted as spam.

Email: (not displayed)

If you don't feel comfortable giving me your real email address, don't expect me to feel comfortable publishing your comment.

Website (optional):

Follow me on Twitter

Best Of

  • How not to apply for a job Applying for a job isn't that hard, but it does take some minimal effort and common sense.
  • Movie marketing on a budget Mark Cuban's looking for more cost effective ways to market movies.
  • California State Fair The California State Fair lets you buy tickets in advance from their Web site. That's good. But the site is a horror house of usability problems.
  • Customer reference questions. Sample questions to ask customer references when choosing a software vendor.
  • Comment Spam Manifesto Spammers are hereby put on notice. Your comments are not welcome. If the purpose behind your comment is to advertise yourself, your Web site, or a product that you are affiliated with, that comment is spam and will not be tolerated. We will hit you where it hurts by attacking your source of income.
  • More of the best »

Recently Read

Get More

Subscribe | Archives

Recently

Assumptions and project planning (Feb 18)
When your assumptions change, it's reasonable that your project plans and needs change as well. But too many managers are afraid to go back and re-work a plan that they've already agreed to.
Feature voting is harmful to your product (Feb 7)
There's a lot of problems with using feature voting to drive your product.
Encouraging 1:1s from other managers in your organization (Jan 4)
If you’re managing other managers, encourage them to hold their own 1:1s. It’s such an important tool for managing and leading that everyone needs to be holding them.
One on One Meetings - a collection of posts about 1:1s (Jan 2)
A collection of all my writing on 1:1s
Are 1:1s confidential? (Jan 2)
Is the discussion that occurs in a 1:1 confidential, even if no agreed in the meeting to keep it so?
Skip-level 1:1s are your hidden superpower (Jan 1)
Holding 1:1s with peers and with people far below you on the reporting chain will open your eyes up to what’s really going on in your business.
Do you need a 1:1 if you’re regularly communicating with your team? (Dec 28)
You’re simply not having deep meaningful conversation about the process of work in hallway conversations or in your chat apps.
What agenda items should a manager bring to a 1:1? (Dec 23)
At least 80% of a 1:1 agenda should be driven by your report, but if you also to use this time to work on things with them, then you’ll have better meetings.

Subscribe to this site's feed.

Contact

Adam Kalsey

Mobile: 916.600.2497

Email: adam AT kalsey.com

Twitter, etc: akalsey

Resume

PGP Key

©1999-2019 Adam Kalsey.