Burning Questions - The FeedBurner Weblog

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:

• Added reliability and delivery scale, thanks to Google infrastructure. The same systems that handle Gmail and other, large-scale public email communications traffic now deliver FeedBurner email subscriptions, too.
  


• Robust subscriber list search and pagination. Instead of loading your entire subscriber list, which is too much for some browsers to handle if that list is really big, the new service displays just the 150 most recent subscribers. You can search for specific addresses or general domains (e.g., "hotmail.com" will return a list and total count of your subscribers with "hotmail.com" in their addresses.) This list is now paginated to allow you to scroll through its contents easily.
  


• Complete subscriber list export. Want to view the whole shebang offline? Download a CSV-formatted text file of your entire subscriber list.

These new features are in addition to FeedBurner's classic email capabilities. As always, you may:

• Customize delivery time frame and time zone
• Write your own welcome/activation email text
• Choose from multiple custom font, size, and color combinations
  
• Incorporate a custom graphic logo in your HTML message header
  

Also, new subscribers are still required to confirm their requests (to minimize potential abuse).

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.)

Posted by Matt Shobe, User Experience Designer, AdSense for Feeds

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.

Interesting Fact: this is the 210th time we've posted to this blog. Bittersweet Reality: it will be the last.

Our team has used Burning Questions to provide FeedBurner product announcements and stories about the publishers who use FeedBurner since February of 2004. We've laughed, we've cried, we've hackathoned. Above all, we've tried to give you a running play-by-play of the service's evolution from a green page with eight checkboxes to a central hub for publicizing, optimizing, analyzing, and, of course, monetizing all manner of blog, podcast, and commercial content in syndication. (We sheepishly admit a good number of you have spent more time than you'd like troubleshootizing, too. Feeds can be ornery.)

Today we're formally signing off Burning Questions, but not before we direct you to the new, official site for all future updates: the AdSense for Feeds blog. This blog will contain all future updates related to all FeedBurner services. We will soon redirect the Burning Questions feed itself to point to the new blog, so you don't need to update any existing feed (or email) subscriptions. Our first post discusses how you can start managing your feeds from a Google account, rather than from your old feedburner.com account. This is mondo important, as all future feed services, both AdSense-provided and otherwise, will eventually require use of a Google account.

FeedBurner would be just another digging construction guy graphic without your active use of, and involvement in, all aspects of it through the years. As we start tying more closely into other Google products that you may already use, we are eager to give you much more of the get-out-of-the-way, it-just-works joy, simplicity and reliability you deserve from web service like ours with all the benefits that Google's platform provides.

Finally, we must relent and reveal: here is the inspiration for a certain error page. With this last post, you finally have all of our secrets. Good luck, and avoid routines like "20 goto 10." That one required the air brakes.

If you've been following some recent posts at the venerable Burning Questions, you'll be happy to know that we are now starting the next phase of FeedBurner integration into Google, right here in our swanky new digs on the Adsense for feeds blog. AdSense for feeds isn't just about earning revenue for your feeds; it's also the starting point for managing syndication and tracking feed analytics. We hope to give you some tips to how to earn the most revenue from your syndicated content, but we'll also be offering tips to help ensure your feeds remain in tip-top shape.


A few months ago, we announced that we would be moving all FeedBurner accounts to Google accounts and we have been steadily doing just that ever since. However, as many of you know, this has been a manual process and has taken some time to smooth out.


Now, we're happy to announce that if you have a valid AdSense account and a FeedBurner account, you should now be able to initiate this account move directly from within your AdSense account. (Moving accounts starting from within FeedBurner.com and FeedBurner.jp to Google will be available soon. We're grinding away on this feature right now.)


Why move? That's the easy part. Moving to a Google account means:


* We can tie your FeedBurner feeds to other Google products and services easily as you see fit
* You can participate in AdSense for feeds
* You will get access to all the new services and publisher tools for syndication we are developing in the future


We will still be contacting FeedBurner publishers by email, based on previous account information you provided that matches information in Google accounts. But if we are not getting to you fast enough, please use the self-serve form to initiate your account move, even if you requested a move at a prior time. This helps us reach as many of you as possible, as there may have been a typo in your request that prevented us from successfully moving your account previously.


We know there are a lot of questions around this process, so we have created a FeedBurner to Google Account Transfer FAQ. We look forward to helping you earn more money from your syndicated content and streamlining your feeds in the New Year!

We've been hinting at this for awhile, but it's finally time to spill the beans: Starting next week, we'll be rolling out AdSense for feeds to a small group of publishers, in anticipation of a full launch to all FeedBurner and AdSense publishers "coming soon". If you start seeing "Ads by Google" on an ad in a feed somewhere, that'd be us.

So what will this mean for you? Well, publishers already in the FeedBurner Ad Network will continue to see premium CPM ads directly sold onto their content, but with the added bonus of contextually targeted ads that will fill up the remainder of their inventory. That means you get the best of both worlds: a dedicated Google sales force that knows how and why to sell onto your content, with the added revenue that full back-fill coverage provides. And with AdSense, you'll know that your back-filled ads are using the strongest contextual ad engine, ensuring the most relevant and profitable ads are delivered to your subscribers. And yes, ads are also sold via Google's AdWords program.

For publishers who are not yet placing ads in their feeds, any publisher who meets the requirements to join the AdSense program will also be able to use AdSense for feeds. You will be able to manage your feed ad units directly from AdSense Setup tab, and track performance right on the AdSense Report tab. You can slice, dice, mix, or mash your tracking across feed units and content units, or keep them totally separate. You're in control. You can still control the frequency and rules around when ads appear in your feeds, without having to mess with templates on your content management system.

You might be wondering what you'll need to do to use AdSense for feeds. You'll learn more about the details when we fully launch, but here are the basics: you will need to sign up for AdSense if you haven't already, and you will want to set up your AdSense channels for "placement targeting" in order to make sure that advertisers can target your syndicated content specifically. As a publisher, you will remain be in control of the campaigns that are targeted at your feed by harnessing the power of Ad Review Center.

And, this is just the beginning of the chocolaty goodness that will come from ongoing integration effort with Google - there are many more "things" and "stuff" yet to come, as we mentioned a few weeks back.

We'll give you the full details on AdSense for feeds, including supported formats, how to sign up, etc., etc. when we're ready for the full launch to all publishers. In the meantime, FeedBurner feeds will continue to be fed as usual, and we'll be reaching out to select publishers individually to try out AdSense for feeds.

There are strange things afoot! (Well, perhaps not "strange," and certainly not just at the Circle K.) In the coming weeks, upon visiting www.feedburner.com, selected publishers will have the opportunity to sign in using their Google Account and experience FeedBurner, now as part of the Google.

If you are among these merry few who migrate early you won't see many changes at first. In fact, you might find yourself saying, "my, it's awfully quiet in here. Almost…too quiet." (But it may look a bit Googlier around the edges.) Your feeds should continue to hum along as they did before, and all of your settings will be yours to manage through your new or existing Google account. This is the same shiny Google account you use to sign into other services at Google.

Following on the footsteps of this account migration, FeedBurner will start to look and feel more like a set of Google services, and we will be completing much tighter integration into other Google services such as Google AdSense. (If you are a feed advertiser, don't worry: we have some happy surprises coming for you as well, and if you are an advertiser who is not yet a feed advertiser, you too shall be blessed with good fortune.)

As part of this Google Account migration, we will need to make a few process changes for our API partners. Effective immediately, the FeedBurner Management API will only be available for existing FeedBurner partners and those Google partners who currently have access to other Google AdSense APIs. The Awareness API will continue to work exactly as it did before, noting that once you migrate to a Google account, you will have to use your Google account credentials IF you use the authenticated API.

If, going forward, you do not want to sign in with a Google account, you can always take your feeds with you by redirecting your subscribers back to your source. Migration will ultimately be here for everybody, including all you MyBrand folks who are master of your domain.

Alright, so we're a little behind on announcing this feature as well. It's been live for weeks and is a real time-saver for everyone involved: the new, self-service Feed Transfer capability. As more and more people build blogs and burn feeds, changes in content ownership and control lead to the desire to move a FeedBurner feed from one account to another. In ye goode olde days, someone who wanted to transfer a feed to another account used to a submit a request to us, and then a staffer in our own Central Planning and Command-Line Voodoo department would verify the accounts and then complete the actual feed transfer. Reliable, but time-consuming and tedious for all parties involved.

Away with workaday drudgery! If you own a feed, you may now transfer it to anyone you like simply by using the Transfer Feed… link, which is listed on your feed's details page and is handily pictured below:

Just provide the email address of the person you wish to transfer this feed to and FeedBurner will send them a transfer request email. The recipient clicks a link in the email and then creates or signs into a FeedBurner account and accepts the transfer on-the-spot. The transfer itself will be completed immediately, moving the feed from your account to theirs. (Please note that only feed owners may initiate transfers from their own accounts to others. Additional how-to info about Feed Transfer is in our Help Center topic.)

We hope this update makes the process of moving feeds around much simpler for all of you. Thanks for letting us know just how popular (and necessary) this feature is!

As we recently posted, FeedBurner's integration into Google is moving along. We've got our coding hats on and are hard at work to get the essential product pieces where they need to be.

However, one somewhat-below-the-radar part of FeedBurner's integration that is already showing up as part of google.com is our new Help Center. (Well, "new" as of late 2007. We admit to being a touch slow on the draw with the PR on this one.) We point this out to show that migrating to a Googley-er tomorrow isn't strictly tied to FeedBurner charts 'n graphs 'n numbers. It used be difficult to find answers; a popup window here, a Forums post there, a blog post over yonder. The Help Center brings sorely needed structure (and searchability) to a bunch of resources that were largely scattered about before. You can now find topics like "What is a Subscriber? How does FeedBurner tally them?", and "Is there a feed file size limit?" in just one place. (We've still got nothing for you on "How can I avoid jury duty selection?") The Help Center will soon introduce new troubleshooting topics and contact options as well.

Speaking of the Forums: they are overdue for the Google treatment, too. We've provided them since shortly after FeedBurner launched as an essential, community-powered companion to the service itself. In the next few weeks, the Forums will move to a new Google Group, with the following benefits:

• Much less spam
• Improved [BUY CH3AP STUFF ONL1NE] search for old topics and conversations
• New email notification options when new topics are posted
• Much, much [FREE V!AGRA NOW] less spam

We also want to point out that FeedBurner Japan is also going to benefit from these Help Center and Groups changes, too. But what about the many other languages FeedBurner publishers use? Google strongly believes in making products accessible to the widest global audience; efforts to formally localize FeedBurner for the most popular and requested languages are under way, going well beyond the options we currently offer.

And, finally: Leap Year post!

Hi there. You may be looking in your feed reader every day and thinking "Another no-news-'bout-FeedBurner day." You may be starting to think, "Are they still in there? In the FeedBurner bubble, burning the feeds? Did somebody maybe shut off their connection to the Tubes?" You may be thinking that or worse. We have some good news, and some just newsy news.

First, the good news. We are totally still here, burning the feeds, writing the checks (that's some sweet cursive Giuliana's wielding), and analyzing the analytics.

Next, the newsy news, aka "what we did over summer and winter and spring vacation." If you are looking for juicy announcements, this section is NOT for you. This is more like the academic paper section of the post, except for the fact it lacks erudition and other big vocabulary words. We have been and are busy integrating FeedBurner into a more Googley way of life. This Googley way of life is very different on the backend architecture side, so the team has been busy both scaling and maintaining the existing environment, while simultaneously rewriting the system to act like one of the cool kids in the more Googley (Googly? Can we get a ruling on this one?) architecture world.

So, if you're a publisher, a good next question is "Um, why are you doing this again?" The answers are numerous, so let's itemize a few of them:

• Full integration with Google. Integration makes it possible to connect with other Google offerings. For example, only a fraction of our publishers have had the opportunity to participate in the FeedBurner Ad Network to date. We would like to offer this capability to an order of magnitude more publishers, and full integration into Google architecture will make this not just a possibility but a likelihood (more on this in the next couple months).
• More and better services. As any Mies Van der Rohe fan will tell you, "more is more." By getting our systems fully integrated into a Google architecture, it will be easier for us to provide some services we've long envisioned but have never really been able to provide because of scale challenges. These include but are not limited to parameterized feeds (e.g., think feeds of query results), a wider variety of email services (those of you wishing to import legitimate-yet-massive email lists know what we mean), and other stuff. And by "stuff," we mean "things."
• Easier to scale as load on the system increases. As more feeds are burned and are hit by more kinds of feed reading bots and readers and API's and crawlers, even feeds that don't have new subscribers see increased activity. Full integration into Google will mean an easier time working through performance and scalability bottlenecks, which means the engineering resources now hard at work on scaling can move on to enhancing services.

Why not build new services and integrate at the same time? There are lots of opinions about the best way to go through integrations. Our perspective is that the time you lose trying to continuously merge an updated legacy codebase with a new rewrite causes you be in a world of never actually getting the integration done because you're constantly working on merge problems, which gives you less time to add new features OR get the new backend integration done, and eventually you kind of grind to a halt, much like Achilles trying to catch the Tortoise in Zeno's paradox. We're confident, in fact, that Zeno would have used software integration to illustrate his paradox had he lived in less pre-Socratic times. Anyhoo, we decided to bite the bullet and go full-on integration (while maintaining the existing environment) as much as possible, knowing that it would mean few new features or capabilities while we went on our backend integration journey. So, while we have continued to add hundreds of thousands of new publishers and feeds, you haven't heard a lot from us despite a lot of hard work. It's not really that exciting to post "Soon, you will have everything you used to have, only it will look different to the people working on it here!"

There are lots of lots of product integration points that we know people would like to see, and we are looking forward to those as well. These opportunities are not lost on some of the brighter students at Google, and believe me, there are some real brainiacs around here. We keep whispering to each other in the hallways "What if they find out we're stupid?"

On the customer side, we have been signing up new publishers right and left (or left and right, depending on whether you live in the northern or southern hemisphere), and in fact, our publisher services team is busier than ever. We used to announce all of these new publishers, but it's a bit less exciting to announce customers that are already customers of other parts of the company without feeling like the kids in school who are the last ones to do everything. (Simulated conversation. FeedBurner: "Hey, we just burned our millionth feed!" Search: "It's cute how they still get excited about numbers in the millions.")

If you saw your subscriber count drop precipitously in your Saturday, November 3rd summary from FeedBurner, the reason is that specific subscriber stats from Google Feedfetcher were offline because this service was apparently out late with friends on Friday night, and well, it completely slept through Saturday. It appears to have rallied, however, and amid firm declarations of "I'm never doing that again", Feedfetcher has started diligently reporting subscriber numbers to us, early this morning Pacific Time. FeedBurner publishers' subscriber counts should be closer to what you'd normally expect starting with reports that will be available on Monday morning.

There's really nothing spookier than hollow, empty ad spaces rattling around your blog and/or web site, putting no cash in your pocket nor any extra hob- in your goblin. Before you banish these underperforming idlers to some distant house upon a lonely hill, we recommend redeeming them with a chance to boost your earning potential. This Halloween, the FeedBurner development team is asking those of us who do the announcing around here to make note of the now-available integration of FeedBurner site ads and AdSense.

This newly integrated capability — designed just for FeedBurner-powered content like yours — puts relevant AdSense content ads to work on your blog and/or website. (Note: AdSense options for feeds not available at this time.) If you choose to activate this service, you can run a 300x250 or 468x60 text or image AdSense ad on your blog. The ad will appear below the first item on your site and archive pages once you have installed the necessary code. Ad content is automatically targeted to complement your site and you will earn revenue each time visitors click on ads. You can even customize the colors (or use a saved color palette from your AdSense account) so the ad unit fits your site's look and feel. Check out these 300x250 examples below.

You don't have to be part of FeedBurner's ad network to put these ads on your site, but be sure to review Google's policies for participating to make sure your site's content is eligible, as these ads are subject to AdSense terms and conditions. Once you're signed up for AdSense, you can check out all the other ways you can monetize your site with ads near your non-feed-powered content. If you are currently part of the FeedBurner Ad Network (FAN), and you've configured your site to run ads, AdSense ads will be inserted on your web site only when there are no FeedBurner Ad Network ads available for those placements (if you choose).

Get Started
To activate the service, sign in to your FeedBurner account, select your feed and go to the Monetize tab where you can connect this service to your AdSense account (if you already have one), or create a new AdSense account (if you don't). This service is currently available to members of FAN and all manner of FeedBurner publishers who go >bumpFeedFlare for your site, you've already added the magic code that makes these ads go where they need to go, so connect your account to AdSense on the Monetize tab and you're ready to earn!)

Earning additional revenue doesn't scare me, I t-tell you what. Where can I learn more?
Additional FAQs have been asked and answered over by here.

Happy HallowEARN feed publishers!

Earlier today, the Google Reader team described the new subscriber stats feature now available in Reader's search results. We'll go grab a donut while you take a moment to read the thorough post.

As the Reader team discusses at the bottom of their post, it's important to remember that FeedBurner is aggregating your Google Reader (and Newsgator and Bloglines and...) statistics across all feeds that you may be redirecting through FeedBurner either via your own http configuration wizardliness or through plugins like FeedSmith or maybe even through simple and direct integrations like those in Typepad and Blogger.

We've consolidated subscriber stats from most of the far corners of the feed subscription universe (yes, we are going on record and saying the universe has corners and is a simple geometric shape - we are not yet committing to whether it's 3D/4D/5D, but we are saying it has corners), in order to give you the most complete picture of your audience. There are thousands of feed-reading services with even more services jumping into the distributed media hottub every day (yes, we are going on record as saying it's a hottub, not an ecosystem), so checking your detailed subscriber analytics page within FeedBurner is always a good place to find out where there are new services that are incorporated into your statistics.

Please pay special attention to the information that may be revealed in the new Google Reader subscriber stats as it may point out instances where you have inadvertently fragmented your audience by offering more than one flavor of your feed to the public. No worries, as this is easily remedied. Again, you can redirect any outliers to your FeedBurner feed and instructions for Blogger, TypePad and Wordpress are available.

Can you imagine adding fun, targeted video content to your site, while earning revenue at the same time? No, really. Picture the majesty, the drama, the undeniable spectacle of it all. Video. Your site. Total togetherness. It's a dreamlike state.

Whoa, snap out of it! This video-makes-money-on-your-site thing is now a solid reality. Google AdSense announced today a new offering called video units. Video units let website publishers choose relevant content from select YouTube partners and have it streamed to their sites within a highly customizable video player. The videos are supported with user-friendly, targeted advertising, both above the video content and within the bottom 20% of the viewing area. Video units are now available in the U.S. for English language websites that are signed up for an AdSense account.

If you want to learn more and see a sample video unit, you can check out the AdSense blog. If you're ready to get started, sign in to your AdSense account. You'll need to sign up for AdSense to take advantage of this new service.

Happy viewing!

This post has been brought to you by Ryan Hayward, aspiring blogger and Product Marketing Manager for Google AdSense.

This post is a quick note from the foreman down at the FeedBurner ironworks and custom tools depot. If you're a new or longtime user of FeedBurner FeedSmith — our plugin for WordPress that helps ensure you count all of your blog's feed traffic through FeedBurner — there is a recommended security-related update to this plugin for you to download. Here are the details:

Potential security vulnerability
Some WordPress plugins that permit the entry of user-entered values, such as older versions of FeedSmith, can be vulnerable to what is called a "cross-site request forgery." Without getting overly technical, this permits someone to change WordPress plugin settings on your system without you noticing during the time you are signed into your WordPress control panel. And no one wants that.

How to protect your feed
Protect your feed by downloading FeedSmith v2.3, available; download it now. This newest release ensures that the only person who may change FeedSmith settings is the administrative account that is signed into your WordPress control panel. If you are following our WordPress QuickStart guide to get started with FeedBurner, the link to download FeedSmith provided in that QuickStart has already been updated to point to v2.3. To verify the version of the plugin you have, you can visit the "Plugins" tab within the WordPress control panel and look for FeedSmith's entry; the version number is displayed in that entry.

If you currently use FeedSmith on your WordPress-powered site, follow these instructions to update this plugin.Download version 2.3 of the plugin.Sign in to your WordPress admin control panel.Under Plugins, locate the current FeedSmith plugin, and click "Deactivate."Copy the plugin file, FeedBurner_FeedSmith_Plugin.php into your default WordPress plugin directory, wp-content/plugins/Reactivate the plugin by logging in to your WordPress administration area, clicking Plugins, then clicking Activate at the end of the "FeedBurner FeedSmith" row.

At the end of this process, v2.3 will be active and will use your existing feed redirection settings; there is no need to re-enter them. You will also be protected against any potential request forgery attack.

We'd like to thank Blog Security for their recent writeup of this potential exploit. Software is fun!

They laughed at us in Geneva when we presented our new word to the scientific community, but it's the surest way to describe our latest enhancement to Headline Animator. Publish + Advertise, all in one place (and let's not kid ourselves, "adverblish" isn't going anywhere).

Headline Animator - through its many transformations - is morphing into quite the marketing tool. Why do we continue to call it a Headline Animator when others refer to these things as widgets? Because we are a stubborn people, some would say an ornery people, raised on the hardscrabble plains east of Medicine Hat, eking out meals of corn with more corn, and we say it's a Headline Animator…where were we? Oh yes. For those of you tracking the Headline Animator's evolution via ham radio or this blog, you already know that it helps build your audience by enabling feed promotion on MySpace, other blogs, in forums, even at the bottom of your emails. Or, you can just grab code and put it wherever you think it should go. Leveraging Headline Animator to advertise your content in other feeds is the next step.

How it works
By connecting the simple-to-use Headline Animator service to our world-class feed advertising network we can give content publishers the ability to create their very own dynamic, feed-powered ad units and place them in the feed ad network (all by themselves). No sales folks, no ad trafficking to ensure the creative is current. No speed bumps. Just you and your content, going more places. This is the fast-track method for putting dynamic content in front of an audience subscribed to the most popular feeds on the series of tubes. If the world's top blue-chip advertisers can advertise in feeds, why not you too?

Sample ads
Feed-powered ads reflect the most current headlines from your feed and they can be designed to suit your marketing needs. Create an ad encouraging feed subscription using one of our standard template designs. Or, paint your own canvas by linking to a background image you host. Check out these sample ads below:

Quality and reach of the ad network
Rarely has the almighty dollar gone so far. Place your ad in a target channel (e.g. Business, Arts & Entertainment, Travel) and it will run on established brand sites like the leading newspapers and media properties (e.g. USA Today, Wired, Newsweek), top blog networks (e.g. Gawker Media, B5 Media, Gothamist LLC) and independent sites across a diverse range of topics. This type of ad buy gives you scale and access to an audience consuming content away from traditional Web sites.

Getting Started
The process for creating and placing a Headline Animator ad is simple. Sign in to your FeedBurner account, select the feed you want to promote, navigate to the "Publicize" tab and look for the Headline Animator service listed in the left-hand column. From there, you can create your ad. (View a sample configuration screen) For more information, additional FAQs are included at the end of this post. If you publish regularly updated content and you want to put that content in front of more eyeballs, this service is for you.

Follow the story link to read more...