Tuesday, August 28, 2007

[Inside AdSense] Referrals reluctant to appear?

We've heard that many publishers are having trouble viewing referral 2.0 ads on their pages, and we'd like to explain some of the most common reasons why this might be.

First, keep in mind that not all referral ads are available in all sizes. For instance, most horizontal referral ad units smaller than 180x60, square referral ad units smaller than 125x125, and text links are only available at this time for Google products such as AdSense or AdWords. This means that if you generate code for referral ads in an unsupported size, you won't see any referrals shown on your webpages. To avoid this issue, we recommend first selecting categories or products for your referrals before selecting a size at this time.

Similarly, you may not see the referral ads you've selected on your pages if you've grouped a number of referral ads into your Ad Shopping Cart which are each available in different sizes. If this is the case, you may wish to try regenerating your referral code with a particular ad format in mind -- this way, you can be sure to select products available in that format.

Here are several other reasons your chosen referral ads may not show:
  1. The particular referral ad you've chosen is not available in your country. When generating your code, you can view the ads available for specific countries by clicking the 'change' link above the referrals wizard.

  2. You've unselected the 'Pick best performing ads' checkbox for a referral where the advertiser has run out of budget or ended the campaign. To take advantage of the available inventory of related products, we recommend leaving this box checked.

  3. You've added more than three referral units to your page. Our current policy allows a maximum of three referral ad units on any policy-compliant page.

  4. Our system has determined that your pages contain potentially mature or sensitive content. However, as your content changes, you may begin to see referral ads appearing.

  5. The referral ad code may have been modified. Be sure to copy the code exactly as it appears in your account and paste it directly onto your pages.
Please know that we're working as quickly as we can to fine-tune the process of generating referral code. Also, we appreciate all of your feedback on referrals 2.0 so far, and we encourage you to let us know how we can keep improving AdSense.



--
Posted By Inside AdSense Team to Inside AdSense at 8/28/2007 09:40:00 AM
--~--~---------~--~----~------------~-------~--~----~
Having trouble viewing the links or images in the message above? Visit http://adsense.blogspot.com/ .

You received this message because you are subscribed to the Google Groups "Inside AdSense" group.
To unsubscribe from this group, send email to Inside-AdSense-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Inside-AdSense
-~----------~----~----~----~------~----~------~--~---

1 comment:

FreddyWare said...

Another common reason for referral ads and other Google AdSense ads not showing is the use of document.write in its JavaScript, which is not permitted in strict XHTML. One of my sites, FreddyWare Web Services (including domain registrations, free hosting, and blogs), has the referral code implemented, but it does not show.

To clarify, let me tell you that this problem will not be evident in Internet Explorer, since I use server-side scripting to detect browsers that can handle the application/xhtml+xml MIME type. Firefox, for example, can, so my scripts automatically output the application/xhtml+xml MIME type header. Unfortunately, browsers like Firefox take this MIME type seriously and interpret the XHTML very strictly; therefore, the Google AdSense code does not show.

People like me could elect to use only the text/html MIME type, like I've done on other sites with AdSense (see the King Edward Digital Information Exchange or my blog), in which case browsers like Firefox will NOT render XHTML strictly and will permit document.write in JavaScript.

Please note that this problem won't show when validating FreddyWare.org with the W3C Validator, since my pages will deliver as text/html to the Validator.

Frederick