Families Ad Format Requirements: Fix Google Play Rejections with AdMob

GOOGLE PLAY POLICY GUIDE • UPDATED SEPTEMBER 2026

Families Ad Format Requirements: How to Fix a Google Play Rejection

A practical guide to compliant AdMob ads for apps that target children, families, or both children and older audiences.

What this Play Console issue means: Google found an ad, offer or monetisation placement that may cause accidental clicks, interrupt child users, use an unsuitable format, or fail another Families requirement. It is not solved only by changing the AdMob content rating—your format, placement, age handling and every ad source must comply.

In this guide

1. What the issue means
2. Which apps must follow Families rules
3. Prohibited ad formats and placements
4. How to configure AdMob correctly
5. Flutter implementation
6. Pre-submission checklist

What Does “Families Ad Format Requirements” Mean?

This issue appears when Google Play considers an app to include children in its target audience and finds advertising or monetisation that is not suitable for those users.

Google Play’s Families policy applies to more than third-party ads. It covers ads, cross-promotion of your own or third-party apps, offers for in-app purchases, paid product placement and other commercial content. A button promoting another app can therefore create a policy problem if it looks like normal app content or is likely to lead to an accidental tap.

The important goal is simple: a child must be able to use the app without being tricked, pressured or blocked by advertising.

Which Apps Must Follow the Families Ads Rules?

These requirements apply when at least one target audience selected in Play Console includes children. Google also reviews the real app experience. Child-oriented imagery, wording and content can affect its assessment even when a developer’s declared audience does not match the product.

App audience	Families ad obligation
Only children	All ads must come from Google Play Families self-certified ads SDK versions, and all monetisation must meet Families rules.
Children and older users	Use a neutral age screen. Ads shown to children or users of unknown age must use Families self-certified SDKs and follow the Families rules.
Not designed for children	Families rules may not apply, but the app still must meet all normal Google Play and AdMob policies.

Do not select broader age groups merely to gain downloads. Google expects each selected group to be genuinely appropriate for the app. Inaccurate target-audience declarations can itself lead to policy action.

Families Ad Format Requirements: What Is Not Allowed?

For child-only apps, these restrictions apply to the full app. For mixed-audience apps, they apply when ads are served to children or users whose age is unknown.

• No app-open ads. AdMob explicitly says apps in Google Play’s Designed for Families programme cannot use app-open ads.
• No interstitial immediately on launch. A full-screen ad must never appear as soon as the app starts.
• No uncloseable interruption. An ad that interferes with normal use or gameplay—including rewarded and opt-in ads—must provide a clear way to exit after no more than five seconds.
• No ad walls. Do not take over the screen or block normal use without a clear, usable dismissal route.
• One ad placement per screen. Do not show multiple banners, video ads or multi-offer banners on one page.
• Clearly distinguish ads from app content. Ads, offerwalls, app-promotion cards and IAP offers must not resemble game controls, lesson cards or normal content.
• No deceptive taps. Never move an ad into a place where the user normally taps; never make a close icon open another ad; never move a close target away from the finger.
• No emotional pressure. Do not use guilt, fear, shock or manipulative language to make a child view an ad or request a purchase.
• Virtual currency must be clear. Children must be able to distinguish virtual game coins from real money used for purchases.

Which AdMob Formats Are Safer for Families Apps?

There is no “automatically approved” ad format. Compliance depends on the audience, the ad request, the creative and the exact placement. But the following is a safer starting point.

Format	Families guidance
Single banner	Potentially usable when it is one clearly separated placement, not close to game controls and does not show multiple offers.
Interstitial	Never at app launch. Use sparingly at a real transition, with a clear close route and no interruption of normal use.
Rewarded / opt-in	May not interfere with gameplay or normal use. If it does, the user needs a clear exit within five seconds. Never use it as a forced gate.
Native ad or self-promotion	Must be obviously an ad or commercial offer, never disguised as a level, lesson, button or content card.
App open	Do not use in Designed for Families apps.

How to Configure AdMob for a Families App

1. Declare the real target audience. In Play Console, open Policy and programs → App content → Target audience and content and select only age groups the app is genuinely designed for.
2. Declare ads and provide access instructions. Play Console requires accurate ad information, a privacy policy and review access instructions.
3. Use an eligible ads SDK. For children or unknown-age users, use only Google Play Families self-certified ads SDK versions. If you use AdMob Mediation, every ad source and custom event in the child flow must be self-certified.
4. Use a neutral age screen for mixed audiences. Do not use a leading question such as “Are you an adult?” with a large “Yes” button. Age screening must be neutral and the child or unknown-age path must receive compliant ads.
5. Apply child age treatment before requesting ads. The current Google Mobile Ads SDK uses Tag for age treatment (TFAT). It replaces the older TFCD and TFUA settings.
6. Set the maximum ad rating to G for child traffic. This helps limit returned ad content to the G rating. It does not replace placement review or your legal obligations.
7. Review all monetisation—not only AdMob. Check cross-promotion, upgrade prompts, reward screens, links, WebViews and mediation partners.

Important: Google’s SDK controls help with compliance but do not make a developer compliant by themselves. The publisher remains responsible for the app’s ad sources, placement, content and applicable child-privacy laws.

Flutter: Set Child Age Treatment and G-Rated Ads

For current Google Mobile Ads Flutter Plugin releases, configure age treatment before initialising and loading ads. The older tagForChildDirectedTreatment and tagForUnderAgeOfConsent properties are deprecated.

import 'package:google_mobile_ads/google_mobile_ads.dart';

Future<void> configureChildAds() async {
  final configuration = RequestConfiguration(
    ageRestrictedTreatment: AgeRestrictedTreatment.child,
    maxAdContentRating: MaxAdContentRating.g,
  );

  await MobileAds.instance.updateRequestConfiguration(configuration);
  await MobileAds.instance.initialize();
}

Use this only when the child setting is legally and product-wise appropriate for the request. For a mixed-audience app, your age-screen result must determine whether the request receives child treatment. Do not simply mark every user as an adult to obtain higher advertising revenue.

After implementing the configuration, test the actual child flow in the app. Google’s Ad Inspector recommends in-context testing because out-of-context tests do not carry the app UI’s child-directed treatment configuration.

Common Reasons for Rejection

• Showing an app-open ad in a children’s or Designed for Families app.
• Displaying an interstitial as soon as the splash screen ends.
• Using a rewarded ad that blocks a child from continuing for more than five seconds.
• Putting more than one banner, video or offer placement on the same screen.
• Using a cross-promotion card that looks like a play button or app content.
• Using a mediation partner or custom event that is not Families self-certified for child traffic.
• Selecting children and adults in Play Console without a neutral age screen.
• Leaving an old SDK configuration in place and assuming that a deprecated child-directed tag covers all current requirements.

Families Compliance Checklist Before Resubmitting

1. Confirm the target ages selected in Play Console accurately describe the real app.
2. Remove app-open ads and any launch-time interstitials from the child experience.
3. Check every screen: never show more than one ad placement.
4. Confirm each interruptive ad has an obvious, working exit within five seconds.
5. Check that every ad, IAP prompt and cross-promotion is visually distinct from app content.
6. Set child age treatment and MaxAdContentRating.g before loading child or unknown-age requests.
7. Audit mediation groups, ad sources and custom events against Google Play’s Families self-certified list.
8. Test with test ads on a physical device, including the exact first launch, background return, reward, close and purchase flows.
9. Update the privacy policy, Data safety information and Play Console declarations so they match the released app.

Frequently Asked Questions

Can a Families app use AdMob?

Yes, but ads served to children or users of unknown age must use Google Play Families self-certified ads SDKs and meet all Families content, data and format requirements.

Are app-open ads allowed in Designed for Families apps?

No. AdMob’s own app-open guidance says that apps within Google Play’s Designed for Families programme cannot use app-open ads.

Are rewarded ads allowed for children?

They are not automatically prohibited, but they cannot interfere with normal use or gameplay without a clear exit after five seconds. They must not be used as a forced gate or a deceptive purchase prompt.

Does setting G-rated ads fix the rejection?

No. G rating filters ad content; it does not fix an app-open ad, a launch interstitial, multiple placements, an unclear commercial offer or an unsuitable mediation source.

Final Thoughts

Families policy review is about protecting the child experience, not merely turning on a setting. The safest approach is to use minimal advertising, clear separation between app content and commercial content, child-appropriate ad sources, neutral age screening for mixed audiences and careful device testing before submission.

Official references

• Google Play Families Policies
• Comply with Google Play’s Families Policy using AdMob
• Google Mobile Ads Flutter: Targeting and age treatment
• AdMob app-open ad guidance
• Play Console: Target audience and app content

Google Discover Publishing Guidance

Google Discover cannot be requested or guaranteed. Google says pages are automatically eligible when they are indexed and comply with Discover content policies. Keep this guide updated when policy details change, use a specific factual headline, and avoid promising “guaranteed approval.”

• Use one large, high-quality image genuinely related to the article and enable max-image-preview:large in the Blogger theme.
• Use og:image or schema.org image markup where your theme supports it; do not use a generic site logo.
• Keep the page publicly accessible, indexable and useful to developers facing a genuine Play Console issue.
• Show the update date and retain links to Google’s official policy sources.

Featured image brief

Create one large, high-quality editorial image showing a realistic Android phone with a clean child-safe app screen and a Google Play policy review card. Add a clearly readable headline: “FAMILIES AD FORMAT RULES”. Show small visual callouts for “No App Open Ads”, “Exit Within 5 Seconds”, “One Ad Per Screen” and “G-Rated Ads”. Keep the scene professional and organic with solid blue-gray, white and soft green colours. No gradients, no neon, no generic AI shapes, no copied Play Console screenshot and no child faces.