The 300 x 250 ad is the IAB medium rectangle that is available for both phones and tablets. While all AdMob/AdSense policies and the information on banner ad guidance still apply, we want to share specific guidance regarding this ad size due to its unique size and shape. For more information on banner ads, please visit the Google Developers site.
Below, you'll find some implementation guidelines and best practices. The examples will help to clarify some of the most frequently used 300 x 250 ad implementations and whether they are aligned with our policies in providing a good user experience.
While some of the implementations that we discourage may not specifically be against our policies, we may still take appropriate action on any invalid activity that they may cause. Not following these guidelines may lead to invalid activity and/or may result in Google disabling ad serving to your app. Please visit our Ad Traffic Quality Resource Centre for more information.
Discouraged
Ads mimicking app content (against policy)
Ads should not mimic app content. They must be clearly distinguishable from the app content. For example, in galleries, ads must be clearly delineated so that they are not a feature image in the gallery themselves.
Ads overlapping app content (against policy)
Ads should not float or hover over app content. This includes placing the ad over a background that covers app content. Ads should not unexpectedly appear and cover app content.
Ads on screens with no content (against policy)
Ads should not be placed on a 'dead end' screen. There must be a way to exit a screen without clicking the ad (for example, a "back" or "menu" button). Otherwise, the user should be notified that the home button will exit the app.
Click to view an exampleAds adjacent to interactive elements
The close proximity of ads to other elements within an app is one of the biggest causes of accidental clicks. To avoid accidental clicks, banner ads should not be placed immediately next to interactive elements and app content, which can include (but is not limited to):
- Navigational buttons, such as a "next" button.
- Interactive content such as a text chat box or an image in an image gallery.
- On a game play screen where users are continuously interacting with the app.
- A "close" button or something equivalent on an app exit confirmation screen.
Custom close or dismiss methods
Custom close or dismiss methods include but are not limited to, a custom X button, a custom close button, or text that indicates the user should click it to close the ad. These buttons or text should not overlap or be adjacent to the ad since such placements may cause a high volume of accidental clicks.
Click to view an exampleOverlapping close button
Other implementations and best practices
Pause or level complete screen
Placing a 300 x 250 ad on a pause or level complete screen may be compliant as long as you take care that users are not encouraged to click or tricked into clicking the ad to resume the app. The ad should also be distinguishable from other interactive elements on the screen.
Clear representation of ads
Ads should be distinguishable from app content. It is recommended that you label, position or represent ads in a way that lets users know that they're sponsored ads and not part of the app content. However, don't label ads with any messaging that encourages users to click or view ads.