Tuesday, December 20, 2011

[G] Smarter default font settings

| More

Inside AdSense: Smarter default font settings


When it comes to customizing the appearance of AdSense text ads, we’ve heard from many publishers that they aren’t always sure what combinations to pick. As a starting point, we offer a set of default options for ad colors, font size and font face, which are based on positive performance across all publisher sites.



Today, we’re announcing an exciting improvement to our default font settings, which will optimize your ad units for your unique site and users. For each ad unit that’s set to show the default font face and font size, our system will now automatically select and show the best-performing option. This best-performing option will depend on a variety of factors, including the user’s viewing environment (operating system, browser) and the ad unit itself (language, size, number of ads, etc). We’ve tested the effects of these factors on our AdSense fonts and incorporated the best combinations into our default font settings. Our aim with this update is to help improve ad performance on your site by automatically applying optimal font settings to your ad units.



Please keep in mind that this change will only affect ad units which have “AdSense default font family” and “AdSense default font size” selected. You won’t be affected if you’ve previously set your ads to a specific font face or size, but we encourage you to give our new settings a try. To change the font settings of any existing ad unit, simply edit it under the My ads tab. If you’d like to change the preferences for future ad units you’ll create, visit the Account Settings page under the Home tab, and edit the “Default ad display preferences” section.



We hope you’re as excited about this development as we are -- we’ll continue to bring you the latest in our research around text ad options.



Posted by: Stephen Yuan, AdSense Engineering


URL: http://feedproxy.google.com/~r/blogspot/tuAm/~3/1zlqjHAK0zM/smarter-default-font-settings.html

No comments: