# Google Play ads declaration: check formats before submission

> Before submission, check ad formats, SDKs and cross-promotion to answer the Play Console ads declaration accurately.
> By Dave · 2026-10-11
> Source: https://otf-kit.dev/blog/google-play-contains-ads-declaration

A Google Play “Contains ads” declaration is a small release task with an app-wide answer. Before you submit, Play Console asks whether your app contains ads; that answer affects the label shown on the store listing. The right response depends on the experience in the build you distribute, including ad formats delivered through third-party SDKs and your own cross-promotion.

Treat the form as a factual inventory, not a guess based on the app’s business model. A paid app can still contain ads. A free app does not automatically contain them. And the presence of an upgrade offer is not, by itself, what Google means by the “Contains ads” label. Work through the actual screens, ad integrations, and release configuration before selecting Yes or No.

## Find the declaration in Play Console

Google puts this answer on the App content page in Play Console. Under Ads, select Start for a first declaration or Manage to change one already submitted. Review the Ads policy, choose Yes or No, and save the response. Play Console’s Needs attention tab shows policy declarations that need action; Google says declarations must be completed before the relevant deadlines.

Keep the answer connected to a specific app and release. If you maintain separate application IDs, regional variants, or build flavors, check which code and configuration reach each listing. A test build without ads does not prove that the production variant has none. Conversely, an ad SDK in a dependency list does not tell you, by itself, which formats the shipped app can display. Trace the integration and the release configuration together.

Record the Play Console app, the build or variant checked, the declaration choice, and the evidence behind it. That short record helps the next release owner understand whether a change in dependencies, remote configuration, or monetization requires another review.

## Decide from the formats people can see

Google says the declaration covers ads delivered through third-party ad SDKs, display ads, native ads, and banner ads. If your app contains ads, Play shows a “Contains ads” label to all Play Store users.

![Dex and Nova inspect banner, feed and full-screen app placements before deciding whether shipped ad content is present.](https://cdn.otf-kit.dev/blog/google-play-contains-ads-declaration/inbody-ad-placement-audit-20261011a.png)

The help page gives examples that should be answered Yes: an ad SDK integrated to show banner or interstitial ads, including formats used to monetize or promote your own apps; native ads presented within ordinary content; and house ads displayed as a banner, interstitial, ad wall, or widget. These examples make clear that the question is about what the app presents, not only whether an advertiser paid for a campaign.

Inspect the app’s real screens and the code paths that populate them. Look at onboarding, feeds, menus, gameplay, empty states, and screens shown only after an account action. Search the dependency and configuration inventory for ad integrations, then check their current vendor documentation and your own initialization and placement settings. Test the release variant with the same remote settings used for distribution. If ad requests or placements can be switched on remotely, include the active production configuration in the review.

Do not stop at a source-code search. A placement may be assembled from a shared component or controlled by configuration. Also do not infer that an SDK provides ads merely from its name. Determine whether your app integrates it to deliver an ad format, and save the evidence that answers that question. When facts remain unclear, resolve them with the SDK’s current documentation or your implementation owner before submitting the declaration.

## Separate ads from other commercial content

The “Contains ads” label is not a catch-all for commercial content. Google says it is not intended to cover paid product placement or offers to make in-app purchases or upgrades. Paid placement still needs to comply with local laws, but it is a separate question from this ads declaration.

That distinction matters for apps with subscriptions, paid features, or a checkout prompt. An offer to upgrade should not be marked as an ad solely because it asks for payment. At the same time, do not use the presence of a paid product to dismiss an actual banner, sponsored item, or interstitial elsewhere in the app. Inventory each format separately and answer based on the ad examples and policy page.

The advertising ID permission is another separate check. A permission declaration is not a substitute for deciding whether an ad format appears in the app, and the “Contains ads” answer does not settle which identifier permissions your build needs. Keep both questions on the release checklist; see our [Android advertising ID permission guide](/blog/android-advertising-id-ad-id-permission) for the distinct permission review.

## Check cross-promotion against Google’s example

Promotion of your own apps can count as ads. Google’s example says to answer Yes when an app uses an ad SDK for banners or interstitials to promote its own products or apps. The destination being another product you own does not turn that format into a plain navigation link.

Google describes a narrower More Apps-style case where the answer can be No: a section in the main menu leads users to your other apps, does not interfere with gameplay, and does not confuse users by embedding itself within gameplay. The help page says labels such as More Games, More to Explore, Full Version, More, About Us, or the developer icon may be acceptable substitutions for “More Apps.”

![Byte and Luna compare a menu navigation link with in-feed and full-screen house promotions.](https://cdn.otf-kit.dev/blog/google-play-contains-ads-declaration/inbody-house-promotion-context-20261011a.png)

Use the whole example, not just the menu label. A card that interrupts a task, appears between game rounds, or is blended into a content feed is not the same placement described by the main-menu example. Review where the promotion appears, how it behaves, and whether it is visually presented as an ad. If your layout differs from Google’s example, do not assume the example covers it; read the linked Ads policy and assess the actual presentation.

## Make the answer reproducible

A quick release review can prevent an old declaration from drifting away from the app:

1. Open the exact Play Console listing and check Needs attention and the existing Ads answer.
2. Identify the release variant, ad SDKs, placement components, and any remote settings that affect ad display.
3. Walk the app’s major routes and note banners, interstitials, native placements, ad walls, widgets, and house promotions.
4. Classify paid placement and in-app purchase or upgrade offers separately from ad formats.
5. Compare any cross-promotion with Google’s specific main-menu example and its limits.
6. Save the build identifier, relevant configuration, screenshots or test notes, and the reason for Yes or No.
7. Review the answer when the monetization design or release configuration changes, then save it in Play Console.

This is a focused product inventory, not a promise that a declaration guarantees review approval. Google says it may verify the presence of ads and display the label if appropriate. It also says misrepresenting whether an app contains ads violates Play policies and may result in suspension. Keep the decision accurate, and escalate an ambiguous placement before release rather than relying on an old answer.

## Release checklist

Before sending the build for review, confirm:

- The Ads declaration belongs to the correct Play Console app.
- The production build and active settings were checked, not only a development build.
- Any ad SDK integration and each placement have a documented purpose.
- Banners, interstitials, native ads, widgets, ad walls, and house ads were considered.
- Paid product placement and purchase or upgrade offers were not automatically treated as the ads label.
- Cross-promotion matches the full conditions of Google’s main-menu example if you answer No.
- The person who can change the release configuration knows what would require revisiting the answer.
- The saved Yes or No matches what users can encounter in the shipped app.

The useful question is not simply whether the app earns money or has an advertising-related package. It is whether the app presents ad formats covered by Google’s declaration, and whether a narrow cross-promotion example actually matches the experience. Verify that against the release people will install, then keep the reasoning with the app’s release record.

## Sources

- [Prepare your app for review — Google Play Console Help](https://support.google.com/googleplay/android-developer/answer/9859455)