1 page.title=Ads 2 @jd:body 3 4 <div id="qv-wrapper"> 5 <div id="qv"> 6 <h2>In This Document</h2> 7 <ol> 8 <li><a href="#content-maturity">Content and Maturity</a></li> 9 <li><a href="#context">Context and Behavior</a></li> 10 <li><a href="#disclosure" style="clear:right">Disclosure</a></li> 11 <li><a href="#impersonation">Impersonation of System UI</a></li> 12 <li><a href="#adwalls">Adwalls and Interstitial Ads</a></li> 13 <li><a href="#interfering" style="clear:right;">Interference with Apps and Third-Party Ads</a></li> 14 </ol> 15 16 <h2>More Resources</h2> 17 <ol> 18 <li><a href="http://play.google.com/about/developer-content-policy.html" target="_policies">Developer Program Policies</a></li> 19 <li><a href="http://www.android.com/us/developer-distribution-agreement.html#showlanguages" target="_policies">Developer Distribution Agreement</a></li> 20 <li><a href="http://support.google.com/googleplay/android-developer/answer/188189" target="_policies">Maturity Ratings</a></p> 21 </ol> 22 </div> 23 </div> 24 25 <p> 26 Google Play policies guide how you can use ads in your apps, to help ensure 27 the best experience for users visiting and downloading apps from the store. 28 </p> 29 30 <p> 31 In general, for the purposes of policy, the content of ads displayed by your 32 app is considered part of your app. As an app developer, it is your 33 responsibility to ensure that the content, context, and behavior of ads in 34 your apps conforms to Google Play policies. 35 </p> 36 37 <p> 38 Before you publish, make sure you understand Google Play ad policies and how 39 to display ads in conformance with those policies. The sections below 40 highlight best practices and common examples to help you avoid the most 41 common types of policy violations. 42 </p> 43 44 <p> 45 For more information about Google Play policies that apply to your apps and 46 content, please see the <a href= 47 "http://play.google.com/about/developer-content-policy.html" target= 48 "_policies">Developer Program Policies</a> and <a href= 49 "http://play.google.com/about/developer-distribution-agreement.html" target= 50 "_policies">Developer Distribution Agreement</a>. 51 </p> 52 53 54 <h2 id="content-maturity">Content and Maturity</h2> 55 56 <div class="example-block bad"> 57 <div class="heading">Ad maturity exceeds app</div> 58 <img src="{@docRoot}images/gp-policy-ads-maturity-violation.png"> 59 </div> 60 61 <p> 62 From a policy perspective, ads shown in your app are part of your content 63 and your app is responsible for any violations. If an ad shown in your app 64 violates Google Play policies, your app may be suspended or your developer 65 account terminated. 66 </p> 67 68 <p> 69 For this reason, it's important for you to be be aware of what ads will be 70 displayed in your app and to manage the ads content according to Google Play 71 policies. Here are some guidelines: 72 </p> 73 74 <ul> 75 <li> 76 <strong>Ads must not violate Content Policy</strong>—Ads in 77 your app must not violate the terms of Google Plays Content Policy, 78 including those concerning illegal activities, violence, sexually 79 explicit content, or privacy violations. 80 </li> 81 <li> 82 <strong>Ads maturity must be consistent with your app's 83 maturity</strong>—Content shown in your ads must be consistent 84 with the apps maturity rating in Google Play. Especially, ads content 85 should never exceed your app's maturity rating, even if the ads content 86 by itself complies with general policies. 87 </li> 88 </ul> 89 90 <p> 91 In the example at right, the app's maturity rating is set to 92 "Everyone", which is the lowest maturity level on Google Play. By choosing 93 the "Everyone" maturity level, the developer is declaring that all of the 94 content in the app, <em>including ads</em>, is suitable for all users 95 regardless of age. 96 </p> 97 98 <p> 99 The example app violates Google Play policies by displaying ad content with a 100 higher maturity level—ad content showing gambling, profanity, user 101 location, suggestive content, or content from another app with higher 102 maturity exceeds the "Everyone" maturity rating. Because the ad's 103 maturity is higher than the app's maturity level, the app itself is in 104 violation of policy. To correct the problem, the developer must either 105 restrict ads content to "Everyone" level or raise the app's maturity rating. 106 </p> 107 108 <p> 109 For detailed information about how to choose the appropriate maturity level 110 for your app, or to assess the maturity requirement of ads in your app, see 111 <a href= 112 "http://support.google.com/googleplay/android-developer/answer/188189" 113 target="_policies">Rating your application content for Google Play</a>. 114 </p> 115 116 117 <h2 id="context">Context and Behavior</h2> 118 119 <p> 120 If your app displays ads, it should do so in ways that do not interrupt users, 121 mislead them into clicking on ads, or make changes outside the app without 122 the user's knowledge or consent. Here are some guidelines: 123 </p> 124 125 <ul> 126 <li> 127 <strong>Display your ads within your UI</strong>—If possible, 128 display ads only within your app's UI. This leads to a better user 129 experience and helps avoid policy violations 130 </li> 131 132 <li> 133 <strong>Don't make changes outside of the app without consent</strong> 134 —Ads must not make changes outside of the app without the user's 135 full knowledge and consent. 136 </li> 137 138 <li> 139 <div class="example-block bad" style="width:360px;margin:1em 0 0 2em;"> 140 <div class="heading">Ads through system-level notifications</div> 141 <img src="{@docRoot}images/gp-policy-ads-notif-attr-violation.png"> 142 </div> 143 <div class="example-block good" style="width:360px;margin:.5em 0 0 2em;"> 144 <div class="heading">Notification that's part of the app's feature set</div> 145 <img src="{@docRoot}images/gp-policy-ads-notif-attr.png"> 146 </div> 147 <strong>Changes outside the app must be reversible</strong>—If an 148 ad makes changes outside the app as described above, the changes (and 149 origin app) must be evident and easily reversible. For example, the user 150 must be able to locate and reverse the changes by adjusting settings, 151 changing ad preferences in the app, or uninstalling the app altogether. 152 </li> 153 154 <li> 155 <strong>Notification ads are prohibited</strong>—Your app 156 should not create system-level <a href= 157 "{@docRoot}design/patterns/notifications.html">notifications</a> 158 containing ads unless the notifications are part of the explicit 159 feature set of the app. 160 </li> 161 162 <li> 163 <strong>Don't add shortcuts, bookmarks, or icons</strong>—Your app 164 and its ads must not add homescreen shortcuts, browser bookmarks, or icons 165 on the user's device as a service to third parties or for advertising 166 purposes. 167 </li> 168 </ul> 169 170 <p> 171 Above right is an example notification ad that violates ad policy by 172 providing ads through system level notification. 173 </p> 174 <p> 175 Below right, the notification ad complies with policy because the 176 nature of the notification is part of the explicit feature set of the app, 177 and it also provides attribution of the origin app. 178 </p> 179 180 <h2 id="disclosure" style="clear:right">Disclosure of Ads to Users</h2> 181 182 <p> 183 It's important to sufficiently disclose to users how your app will use ads. 184 You must make it easy for users to understand what ads will be shown in your 185 app, where they will be shown, and what the associated behaviors are, if any. 186 Further, you should ask for user consent and provide options for managing ads 187 or opt-out. Here are some guidelines: 188 </p> 189 190 <ul> 191 <li> 192 <strong>Tell users about your ads</strong>—Create a simple, 193 complete disclosure that tells users how your app uses ads, where the ads 194 are shown, and how they can manage ad options. Take common-sense steps to 195 make the disclosure as clear as possible. 196 </li> 197 198 <li> 199 <div class="example-block good" style="width:213px;margin-left:.5em;"> 200 <div class="heading">Disclosure in Terms</div> 201 <img src="{@docRoot}images/gp-policy-ads-terms.png"> 202 </div> 203 <div class="example-block bad" style="width:213px;"> 204 <div class="heading">Disclosure is hidden</div> 205 <img src="{@docRoot}images/gp-policy-ads-eula-violation.png"> 206 </div> 207 <strong>Make sure users know</strong>—Present your ads disclosure 208 is an easy-to-see location, rather than hiding it where users are not 209 likely to find it. 210 </li> 211 212 <li> 213 <strong>Ask for consent (opt-in) at launch</strong>—Where possible, 214 include your ads disclosure in the app description as well as in an Ads 215 Terms, End User License Agreement (EULA), or similar document. Display the 216 terms at first launch and ask for the user's consent before continuing to 217 the app. 218 </li> 219 </ul> 220 221 <p> 222 A recommended approach is to provide an ads disclosure in an End-User License 223 Agreement (EULA). The disclosure should be clear and succinct and displayed 224 in a modal dialog that asks the user to agree to the terms before using the 225 app. 226 </p> 227 228 <p> 229 Above left is an example of ads disclosure that is hidden in a long EULA. The 230 disclosure information itself is not clearly indicated in the document text 231 and it's not visible unless the user happens to scroll down far enough in the 232 EULA. 233 </p> 234 <p> 235 Above right shows an approach that presents the disclosure in an obvious 236 and clear manner in a EULA and a dedicated Terms agreement. 237 </p> 238 239 240 <h2 id="impersonation">Impersonation of System UI</h2> 241 242 243 244 245 246 247 248 249 <p> 250 Ads must not simulate or impersonate the user interface of any app, or 251 notification and warning elements of an operating system. Your app must not 252 display any ad that attempts to impersonate or represent a 253 system function or UI component. If such an ad is displayed in your app, your 254 app will be in violation of policy and subject to suspension. Here are some 255 guidelines: 256 </p> 257 258 <ul> 259 <li> 260 <strong>No fake app UI notifications</strong>—Ads should not impersonate 261 the interface of an application for advertising purposes. 262 </li> 263 <li> 264 <strong>No fake system dialogs or warnings</strong>—Any ad that 265 presents itself as a system dialog or warning and asks for user input is in 266 violation of Google Play policies. 267 </li> 268 269 <li> 270 <strong>No fake app updates</strong>—Ads should not impersonate 271 system UI for app updates. 272 </li> 273 </ul> 274 275 <div class="example-block bad" style="width:213px;"> 276 <div class="heading">Ad impersonates app UI</div> 277 <img src="{@docRoot}images/gp-policy-ads-impersonate-violation-app-ui.png"> 278 </div> 279 <div class="example-block bad" style="width:213px;"> 280 <div class="heading">Ad impersonates system warning</div> 281 <img src="{@docRoot}images/gp-policy-ads-impersonate-violation-sys-warning.png"> 282 </div> 283 <div class="example-block bad" style="width:213px;"> 284 <div class="heading">Ad impersonates system dialog</div> 285 <img src="{@docRoot}images/gp-policy-ads-impersonate-violation.png"> 286 </div> 287 <p style="clear:both"> 288 Above are examples of impersonations — a pop-up ad that impersonates a 289 system dialog, an ad that impersonates a system warning, and an ad that impersonates 290 an application UI. All of these are in violation of policy. 291 </p> 292 293 294 <h2 id="adwalls">Adwalls and Interstitial Ads</h2> 295 296 <p> 297 If your app uses adwalls to drive affiliate traffic, those adwalls must not 298 force the user to click on ads or submit personal information for advertising 299 purposes before using the app. 300 </p> 301 302 <p> 303 Forcing a user action in an adwall is not only a poor user experience, it is 304 a violation of Google Play policies. 305 </p> 306 307 <p> 308 For this reason, <strong>all adwalls must give the user the option to 309 cancel</strong> or otherwise dismiss the ad without penalty. Interstitial ads 310 may only be displayed inside of the app they came with. Forcing the user to 311 click on ads or submit personal information for advertising purposes in order 312 to fully use an app is prohibited. 313 </p> 314 315 <div class="example-block bad" style="width:213px;"> 316 <div class="heading">Interstitial, modal ad</div> 317 <img src="{@docRoot}images/gp-policy-ads-interstitial-violation.png"> 318 </div> 319 320 <div class="example-block good" style="width:213px;"> 321 <div class="heading">Adwall lets user cancel</div> 322 <img src="{@docRoot}images/gp-policy-ads-paywall.png"> 323 </div> 324 325 <div class="example-block bad" style="width:213px;"> 326 <div class="heading">Adwall forces user action</div> 327 <img src="{@docRoot}images/gp-policy-ads-paywall-violation.png"> 328 </div> 329 330 <p style="clear:both"> 331 At left is an example of an app that requires the user to click through the 332 ad to fully use the app. This is a violation of policy. 333 </p> 334 335 <p> 336 The center example demonstrates an adequate option to let the user dismiss 337 the ad wall easily by cancelling. This is not a violation of policy. 338 </p> 339 340 <p> 341 At right is an example of an interstitial, modal ad that is displayed outside 342 of the app. This is a violation of policy. 343 </p> 344 345 <h2 id="interfering" style="clear:right;">Interfering with Apps and Third-Party Ads</h2> 346 347 <p> 348 Ads associated with your app <strong>must not interfere</strong> with other 349 apps or their ads. 350 </p>