Wrong way to advertise in a feed

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

The entire Hack-a-Day feed just showed up as new in my aggregator. Every single item in the feed was sitting there, appearing as unread, waiting for me to read them. I’d already given them my attention once, but now there were thirty feed items stretching back to November 12, begging for my attention again.

Feed readers often work using change detection. When the list of items in a feed changes, anything that wasn’t there before is considered new content. When the contents of an item change, the reader marks it as changed, or depending on what changed, perhaps even determines the item is new. By default, new and changed items show up in your reading list in most readers.

The most common cause of an existing item changing is the author updating it, perhaps to correct a typo or to add more information. Sometimes I see entire feeds show up as changed when the publisher of the feed changes their feed’s format, going from partial items to complete item bodies. Feeds that switch to a feed management service like FeedBurner or Pheedo or that add tracking information to their feeds will usually end up with a whole slew of repeated feed items. And when someone adds AdSense for Feeds image tags into their feed for the first time, everything in that feed shows up again in my reader.

Hack-a-Day added an advertisement to their feed. Every single item now contains a short paragraph at the end about plasma TVs. The ad was inserted as plain text, and because it went on every item, it caused every item to re-appear in my reader. Most likely what they did was edited the system that generates their feed and told it to stick this text ad at the bottom of every item. Later, when they have a new sponsor, they’ll change the ad text, causing everything to show up as new yet again.

This is obviously the wrong way to do things. If you’re going to have a regularly changing sponsor for your feed, there’s a couple of ways to do it without alienating your readers.

Put your ads in an item by themselves. Instead of attaching the ad to an existing item, create a new item that contains nothing but the ad. Then when you change the ad, only the ad item will appear as new in the reader. The remaining items will remain unchanged. See any of the Lockergnome feeds for an example of this.

Put the ads only on new items. When you publish a new item, attach the ad to the item body instead of appending it to your feed item template. Since the ad appears only as items are published, previously published items are unaffected. If you do this, never remove an ad that’s already been attached to an item. Removing the ad will cause the items to reappear in a reader.

Typeset the ad in an image. By setting the ad in an image, you can change the text inside the ad without the contents of the feed changing. Use a static image source like ad.jpg and just change the contents of the image. Since the HTML never changes, feed readers won’t ever notice the ad has changed, so existing items won’t show up again.


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.