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.
April 30th was my birthday and I took the day off. It was supposed to be a relaxing day. It began by making pancakes with my wife, then playing video games for a while. Soon after I went to get a massage followed by some lunch. Lunch threw my day off. We went to a new-to-the-neighborhood, upscale, sit-down sandwich place called Jerry’s. Their menu is gigantic. I figured that deciding what to eat would be the biggest problem I’d have there. I was wrong.
After we ordered, we noticed three new tables of people seated at various times. We also noticed that about 20 minutes had passed without food. Again, we’re talking sandwiches, not exactly the type of food you’d expect to wait a long time for. A little more time passes and our waiter comes out to tell us that he’s sorry, but our order was “stuck behind a giant take-out order”. This changed my mood from anxious to frustrated …
… and now a tangent on how my mind works:
If someone walks into a sandwich shop to place a giant take-out order, they can safely assume they’ll be waiting a for awhile. If my wife and I sit down in a sandwich shop and order two sandwiches, we assume it won’t take very long. If the kitchen would have understood these common assumptions, they would have realized that the length of time added for the person waiting for the take-out order by having two additional sandwiches made (ours), would have been minimal compared to their overall wait time for their “giant order”. In reality, the take-out customer would likely not even notice the extra time. Instead, the restaurant left two different sets of customers waiting for the same amount of time for two drastically different-sized orders.
My point? Scientific thinking in the kitchen doesn’t always have to yield foam and/or crunchy, flavored air — it can lead to a better experience for the customer.
Back to the story. To make matters worse, after waiting for almost 45 minutes, the three other tables that were seated after us got their food before we did! Once our food finally did arrive, something interesting happened: my sandwich was so good that the frustration I felt for having to wait 45 minutes for it was calmed significantly. Significantly, but not completely … hence this article. If the food wouldn’t have been worth the wait, then this would be an entirely different story. At the very least, their food was great, and that’s a start. However, like in many businesses, the product is only part of the experience.
Before I continue, I’d like to point out that I’m well aware that this restaurant may not have any ongoing problems with their customer service. Our bad experience could easily be, and most likely should be chalked up to “sometimes, shit happens”. I’m an eternal benefit-of-the-doubt giver, but the experience did get me thinking about how this relates to the type of business I’m in.
Remember our server who apologized for the tremendous wait? He didn’t make sure the customers waiting the longest got their food first. The lesson here is to back up your apologies with actions; don’t just apologize to your customers because you think you should, or worse … to make yourself feel better.
In his book “The Last Lecture”, Randy Pausch points out that “a good apology has three parts: ‘1. I’m sorry’; 2. ‘It was my fault’ and 3. ‘How do I make it right’. The last part tells about your sincerity.” Consolation is a vastly overlooked area of customer service, which is essentially Randy’s third part of a good apology.
At Threadless, if something goes wrong that’s our fault, you’ll get a coupon code for money off your next purchase. It’s a great way to say to your customer, “We’re human and we’re sorry but sometimes these things happen. So, here’s something we hope will help soften the blow”.
Consolation could be your only chance at a do over with a customer. Take that chance.
What else could anyone who handles a product-driven, customer-service-related company learn from my experience? First, know that simply having good products won’t retain your customers (but it does certainly help). At Threadless, we’re well aware that the impression between product and customer is fleeting, while the impression between company and customer is long-lasting.
Next, recognizing an issue or problem on the approach is almost always better than reacting to it at the intersection. At the point of intersection, the damage has already been done and the only thing left to do is play damage control. In most businesses, it’s usually two different teams of people who handle the “approach” (strategy/planning) and the “intersection” (customer service). A huge part of being on the “approach” team is understanding, and more importantly — caring, that every approach you miss, the “intersection” team has to clean up for you.
So, as a customer, does this mean that I’ll go back to Jerry’s? Sure I will. Their “product” is great. Only next time, I’ll probably just get it to go.
Read more of this story at Slashdot.
Hack-a-day's new contributor Jason Rollette has a nice overview for the why-and-how on using lead free solder. I certainly learned a thing or two!
[Read this article] [Comment on this article]
Read more of this story at Slashdot.
Read more of this story at Slashdot.
From the MAKE Flickr photo pool
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Among the minor tweaks we introduced with the new Basecamp project switcher are some larger link targets at the top of the screen. Since then I’ve been paying extra attention to link target size. Here are a couple examples of generous link targets for inspiration.
Threadless has featured large link targets on its main navigation for a long time. Here’s what the nav looks like:
As a user, when you glance at this nav, you might imagine the specific pixel areas that you need to target like this:
But when you move your mouse toward the nav, you’ll be pleased to discover the actual link targets are much larger:
The end result is a feeling of comfort. It’s just really easy to click the links. It feels like the links are working with you instead of against you.
Flor does the same thing with their links. Here’s the navigation:
Here are the targets you might aim for:
And here are the actual targets:
You might have noticed both of these sites use images for their navigation links. The same effect is easy to achieve with HTML links. Just use padding where you might have had whitespace.
Normally you might have white space between your links like this:
<div class="nav"> <a href="">First link</a> <a href="">Second link</a> </div>
Instead, use clickable padding on the anchors to create space between them:
<style>
div.nav a { padding: 5px; }
</style>
<div class="nav">
<a href="">First link</a><a href="">Second link</a>
</div>
Note how the anchors touch each other with no white space in the second example.
We do this in quite a few places in our apps and think it’s one of those small things that makes a big difference.
Here are some of my favorite posts from the CRAFT blog this week:
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.