diff --git a/docs/html/distribute/googleplay/policies/ads.jd b/docs/html/distribute/googleplay/policies/ads.jd index 892049918aac1..815dd081e62fd 100644 --- a/docs/html/distribute/googleplay/policies/ads.jd +++ b/docs/html/distribute/googleplay/policies/ads.jd @@ -9,8 +9,8 @@ page.title=Ads
  • Context and Behavior
  • Disclosure
  • Impersonation of System UI
    • -
  • Adwalls
    • -
  • Interference with Ads and Websites
    • +
  • Adwalls and Interstitial Ads
    • +
  • Interference with Apps and Third-Party Ads

    • More Resources

    @@ -129,23 +129,21 @@ page.title=Ads experience and helps avoid policy violations -
  • - Make sure app origin is clear—When you display an - ad, it must be clear to the user that the ad has originated from your app. - If you show the ad in your app's UI while your app has focus, the user - understands the ad origin without explicit attribution. However, if you - display the ad outside of your app, such as in a notification, you must - explicitly indicate the origin. -
    • -
  • Don't make changes outside of the app without consent —Ads must not make changes outside of the app without the user's - full knowledge and consent. For example, ads should not install shortcuts, - bookmarks, or icons, or change default settings without user consent. + full knowledge and consent.
  • +
    +
    Ads through system-level notifications
    + +
    +
    +
    Notification that's part of the app's feature set
    + +
    Changes outside the app must be reversible—If an ad makes changes outside the app as described above, the changes (and origin app) must be evident and easily reversible. For example, the user @@ -154,51 +152,31 @@ page.title=Ads
  • - Notification ads require user opt-in—Your app - should not create Notification ads are prohibited—Your app + should not create system-level notifications - containing ads unless the user has specifically opted-in to this behavior - and is able to easily opt-out. + containing ads unless the notifications are part of the explicit + feature set of the app.
  • - Use low priority for notification ads—Always - assign your notification ads low - priority (for API level 16 and above). + Don't add shortcuts, bookmarks, or icons—Your app + and its ads must not add homescreen shortcuts, browser bookmarks, or icons + on the user's device as a service to third parties or for advertising + purposes.
    • -
    -
    Does not fully indicate origin app
    - -
    -
    -
    Indicates origin app by name and icon
    - -
    -

    - In particular, note that notification ads must clearly identify your app as - the ad origin. If your app sends notification ads that do not sufficiently - identify your app as the origin, the app will be in violation of policy. + Above right is an example notification ad that violates ad policy by + providing ads through system level notification.

    -

    - To identify your app as the origin, you should display the app's full - name and and icon in the notification to provide the clearest - identification and best policy compliance. Displaying a partial app name can - also be sufficient, provided the name unambiguously identifies your app. + Below right, the notification ad complies with policy because the + nature of the notification is part of the explicit feature set of the app, + and it also provides attribution of the origin app.

    -

    - Above right is an example notification ad that violates ad policy by not - providing attribution of the origin app. Below right, the notification ads - comply with policy by providing both the app icon and full app name (in this - case, "Turtle Test"). -

    - -

    Disclosure of Ads to Users

    @@ -218,6 +196,14 @@ page.title=Ads

  • +
    +
    Disclosure in Terms
    + +
    +
    +
    Disclosure is hidden
    + +
    Make sure users know—Present your ads disclosure is an easy-to-see location, rather than hiding it where users are not likely to find it. @@ -240,53 +226,40 @@ page.title=Ads

    - If your app adds homescreen icons and/or browser bookmarks, an acceptable - practice for revealing that behavior is to provide a disclosure in both the - app description and an opt-in EULA on app launch. This ensures that the - behaviors are clearly explained to the user up-front and requires the user’s - consent in a pop-up EULA to continue using the app. -

    - -
    -
    Disclosure in Terms
    - -
    - -
    -
    Disclosure in EULA
    - -
    - -
    -
    Disclosure is hidden
    - -
    - -

    Above left is an example of ads disclosure that is hidden in a long EULA. The disclosure information itself is not clearly indicated in the document text and it's not visible unless the user happens to scroll down far enough in the - EULA. Above middle and right show two alternative approaches that - present the disclosure in an obvious and clear manner at the top of a - EULA and in a dedicated Terms agreement. + EULA. +

    +

    + Above right shows an approach that presents the disclosure in an obvious + and clear manner in a EULA and a dedicated Terms agreement.

    Impersonation of System UI

    -
    -
    Ad impersonates system dialog
    - -
    + + + + + +

    - Your app must not display any ad that attempts to impersonate or represent a + Ads must not simulate or impersonate the user interface of any app, or + notification and warning elements of an operating system. Your app must not + display any ad that attempts to impersonate or represent a system function or UI component. If such an ad is displayed in your app, your app will be in violation of policy and subject to suspension. Here are some guidelines:

    -