Back to Blog
Checklist

Google Play Ads Policy 2026: The Interstitial Ad Checklist

Google Play Ads Policy 2026: The Interstitial Ad Checklist

Every ad your app serves is treated as part of your app. That sentence sits at the top of Google's Ads policy, and it explains a failure mode that catches publishers every month: a build that passes review on its own merits gets pulled because an SDK, a mediation group or a waterfall partner decided to show something at the wrong moment. In 2026 the policy is enforced through five sections — Ad Content, Deceptive Ads, Disruptive Ads, the Better Ads Experiences guidelines, Made for Ads and Lockscreen Monetization — plus the terms attached to the Android Advertising ID. Here is the walkthrough, in the order a reviewer works through it.

The rule that catches the most apps: full-screen interstitial ads in every format that appear unexpectedly, or that cannot be closed within 15 seconds, are not allowed. Opt-in and rewarded formats are exempt, and so are interstitials that do not interrupt an action already in progress — the example Google gives is a screen shown after the score screen in a game.

The twelve-point checklist

  1. Does every ad fit your declared content rating? Ads and the offers they carry must be appropriate for your app's content rating even when the creative is compliant on its own. Google's own examples: a Teen-level ad inside an Everyone-rated app, or an ad offering a Mature app to an Everyone audience. Your rating comes from the IARC questionnaire (content rating), so a casually rated app monetised by an uncapped network carries a mismatch by design.
  2. Does the ad content stay inside Restricted Content policy? Ads and their associated offers inherit the same restrictions as the app itself, and gambling creatives carry extra requirements (Restricted Content).
  3. If children are in your target audience, are you using certified ad SDKs? Families apps may use only families self-certified ad SDKs, may not serve personalised advertising, and a mixed-audience app must add a neutral age screen so children only ever receive non-personalised ads (Families policy). This also interacts with mediation: bidding is not served to child-directed traffic at all.
  4. Do any ads imitate your interface or the system's? Ads must not simulate or impersonate app features such as notifications or operating-system warning elements, and it must be clear to the user which app is serving each ad (Deceptive Ads). Google's violation examples include a help “?” icon that is really an ad, and creatives dressed up as system notifications.
  5. Are the ads confined to the app that serves them? Ads may be displayed only inside the app serving them and must not interfere with other apps, the ads running there, or the device itself — that language covers overlays, companion functionality and widgetised ad units. An ad that survives into the home screen is a violation.
  6. Is anything triggered by the exit path? Ads fired by the home button, or by any control designed to leave the app, are named explicitly as disruptive, because the flow the user asked for is interrupted by an ad instead.
  7. Does every full-screen interstitial close within 15 seconds? This is the hard number in the Better Ads Experiences section: full-screen interstitials that are not closeable after 15 seconds are not allowed. Opt-in full-screen interstitials, rewarded ads a user chose to watch, and interstitials that do not interrupt an action may persist longer.
  8. Is an interstitial landing at the start of a level or a content segment? Ads at the beginning of game play, or at the beginning of a content segment — after a button tap but before the action that tap asked for takes effect — are not allowed.
  9. Is a video interstitial sitting in front of the splash screen? Full-screen video interstitials that appear before an app's loading screen are not allowed.
  10. Are you showing an interstitial after every single user action? Under Made for Ads, repeated interstitials that distract users from the app are banned; the published examples are two consecutive taps that each trigger an interstitial.
  11. Are you monetising the lock screen? Unless the exclusive purpose of the app is to be a lock screen, apps may not introduce ads or features that monetise the locked display of a device.
  12. Is location data or the advertising ID being used correctly? Ads cannot force a click or require personal information before the app can be fully used. Permission-based location used for ads must be disclosed in the app's privacy policy with links to the relevant ad network privacy policies, and location permission may never be requested solely to serve ads (Location Permissions). The advertising ID is for advertising and analytics only: verify the “Opt out of Ads Personalisation” setting on every access, never join it to a persistent identifier such as SSAID, MAC address or IMEI for advertising, and respect a reset or deletion.

Why the 15-second rule deserves its own test case

The guideline is narrower than most publishers assume. It is not “interstitials must always be skippable”: it is that a full-screen interstitial which interrupts an action must give the user a way out within 15 seconds. Three exemptions are written into the policy — ads the user explicitly opted into, rewarded ads watched in exchange for content or a feature, and full-screen interstitials that do not interrupt the user at all. Google credits the Coalition for Better Ads' mobile app experience standard as the source, which is why these clauses read like product-quality requirements rather than content rules. The practical consequence is that whichever network or adapter actually serves the creative does not change who is held responsible: the app is.

Where enforcement lands

Because ads are part of the app, an ads problem is handled as an app policy problem: rejection at review, or removal of an already published app. Ad fraud is treated separately, with its own consequences (Ad Fraud policy), and misleading ad promotion is handled under deceptive promotion practices. Two habits follow. First, keep a release-checklist line that names the SDK version and the ad formats enabled in each app, so a behaviour change is visible in a diff instead of in a rejection email. Second, remember that this policy applies per app and per account: an ads violation in one published app is also a signal about the account behind it.

Sources

Running developer accounts at scale? We handle the operational side.

Click to choose a file · right-click → Paste, or press Ctrl/⌘+V to paste a screenshot

You can also drag a file onto this box.

We reply to the email you provide. Your details stay with KappS.

✔ Submitted

We received your message and will reply within 24 hours.

Or email expert@kapps.store
← Back to edit