AdMob Publisher Guidelines and Policies.

 AdMob allows publishers to generate earnings from their apps using AdMob and Google ads. In addition to our onlineprogram policies, publishers who wish to participate in AdMob must also comply with the following policies and exceptions. If you fail to comply with these policies, we reserve the right to disable ad serving to your app and/or disable your AdMob account at any time.

Invalid clicks and impressions

Publishers may not click their own ads or use any means to inflate impressions and/or clicks artificially, including manual methods. Google treats the invalid click activity very seriously, analyzing all clicks and impressions to determine whether they fit a pattern of use that might artificially drive up an advertiser's costs or a publisher's earnings. If we determine that an AdMob account might pose a risk to our advertisers, we may disable that account to protect our advertisers' interests.

Please note that publishers disabled for invalid activity or violating our policies may not be allowed any further participation in other Google publisher monetization solutions. This means, for example, that if a publisher had an AdMob account disabled for invalid activity or policy violations, they may not be able to use AdSense to monetize, and vice versa. For this reason, these publishers may not open new accounts.

Ad placement

Publishers are encouraged to experiment with a variety of placements and ad formats. However, publishers must comply with the following ad placement guidelines.

Number of ads per page

The number of ads on a single screen should not exceed one if the ad is fixed to the screen top or screen bottom. If the page scrolls, only one ad should be visible on screen at a time.

Additional guidelines for applications

·         Ads should not be placed very close to or underneath buttons or any other object which users may accidentally click while interacting with your application.

·         Ads should not be placed in a location that covers up or hides any area that users have interest in viewing during typical interaction. Ads should not be placed in areas where users will randomly click or place their fingers on the screen.

·         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 application.

In-app ads

Apps should only use the SDK to request ads.

Exceptions to AdSense policies

In principle, all AdMob publishers must follow our online program policies, however there are certain policies that differ between AdSense and AdMob. Please see the exceptions below.

Ad placement

We no longer allow AdSense ads to appear in mobile applications. However, with AdMob, the SDK is designed for publishers to monetize their mobile applications. AdMob partners can use this SDK to place ads in their mobile applications.

Ad behavior

AdMob has an ad refresh function which can be used by mobile applications that use the AdMob SDK. The refresh rate may not be set to a value outside of the range specified in the SDK.

+1 button

·         Publishers may not sell or transmit to others any data related to their users' activity of the +1 (or similar) Google button (“+1 button”). This prohibition includes, but is not limited to, any use of pixels, cookies, or other methods to recognize such users’ clicks on the +1 button, the data of which is then disclosed, sold, or otherwise shared with other parties.

·         Publishers may not attempt to discover the identity of a +1 button user unless the publisher’s user has consented to share his or her identity with the publisher via an AdMob-approved authorization procedure. This prohibition includes identifying such users by correlating +1 button reporting data from AdMob with publisher’s data.

Sub-syndication and ad network mediation

No sub-syndication

Publishers may not enter into sub-syndication relationships (i.e., Google should have a direct relationship with the publisher, rather than through an intermediate party).

Restricted information sharing

·         Metrics: Publishers may not share access to the AdMob reporting console (unless with AdMob’s prior written consent on which metrics to share).

·         Code: Publishers may not share either source Google SDK code or uncompiled Google SDK code with any third party.

Mediation

AdMob’s network mediation service is intended to enable access to participating third party ad networks’ first party advertiser demand (as opposed to demand from exchanges, mediators or optimizers). Reporting in AdMob for ads served through AdMob's network mediation features may differ from reporting by third party ad networks. AdMob has no obligation or responsibility for discrepancies in reporting, or for the performance or results of third party ad networks or software. The following applies both to AdMob's network mediation features and any third party network mediation that publisher may use:

·         Publisher will adhere to any additional implementation and technical guidelines as may be provided by AdMob;

·         Once the AdMob ad call is initiated, third parties may not interfere with or change the delivery or display of the ad;

·         Revenue share will be paid only to the publisher; and

·         AdMob is not obligated to provide support to, guarantee compatibility with, or discuss discrepancy resolution with any third party.

Beta features

Some features may be identified as “beta” or otherwise unsupported (“beta features”). Publishers may not disclose to any third party any information from beta features, the existence of non-public beta features, or access to beta features.