Başar BallıözProduct Engineer
← All posts

Google Play's Families policy and AdMob: ads in an app for children

If children are part of your app's audience, Google Play's Families policy decides which ads you may show, how, and with which identifiers. Here is what the policy asks, how AdMob's settings map onto it, and the choices I made for Tibblo.

By Başar Ballıöz · · 4 min read

This is a developer's summary, not legal advice. Policies change; the official pages linked at the end are what counts.

When the Families policy applies

In Play Console's Target audience and content section you choose the age groups your app is for. If any of them includes children, the Families policy applies. There are two cases:

  • Children only. The app is made for kids.
  • Mixed audience. The app is for children and adults. Google allows this "if you truly have designed your app for all ages", and a mixed-audience app must include a neutral age screen.

Be honest here. Google says misrepresenting your audience can lead to removal or suspension, and imagery or wording that appeals to children can count toward a child audience even if you did not select one.

Tibblo is for children aged 6 and up and their families, so its audience is mixed. The game asks the player's age once, and that answer drives everything below.

What the policy asks of ads

For ads shown to children, or to users whose age you do not know:

  • Use only Families Self-Certified Ads SDKs. Google keeps a list; AdMob is on it.
  • No personalized ads, interest-based advertising or remarketing.
  • Content appropriate for children. Google's examples of what is not allowed include gambling, violence, dating and controlled substances.
  • No deceptive formats. Ads must be clearly distinguishable from app content, must not trick people into clicking or make closing them confusing, and you may not stack several ad placements on one page.
  • Format limits. For apps aimed at children, the policy rules out full-screen ads shown immediately when the app launches, and rewarded or opt-in ads that cannot be closed after 5 seconds when they interfere with play.

The identifier rules are just as important. Google's wording: don't serve personalized ads to children, and don't collect persistent identifiers such as the advertising ID from them. Apps that only target children must not transmit the advertising ID and should not request the AD_ID permission when targeting Android API 33 or higher; mixed-audience apps must not transmit it for children or users of unknown age.

AdMob's settings, one by one

AdMob's request settings map onto those rules:

  • Child-directed treatment (tagForChildDirectedTreatment): marks the request as coming from a child. AdMob then disables interest-based ads and remarketing for it and, on Android, does not send the advertising ID.
  • Under the age of consent (tagForUnderAgeOfConsent): for users in the EEA under the age of consent; turns off personalized advertising. If both tags are set, the child-directed one wins.
  • Maximum ad content rating (maxAdContentRating): G, PG, T or MA. Ads come back at that rating or lower. A rating set in code overrides the one in the AdMob dashboard.
  • Personalization off: the publisher privacy setting can disable personalized ads for any request.

One update worth knowing: AdMob's current documentation marks the two tags as deprecated in favour of a single age-restricted treatment setting (child, teen or unspecified). If you set both, Google applies the most conservative treatment. Check which one your SDK or plugin version supports.

The choices I made for Tibblo

Everything starts from one rule in the code: a player under 13, or one who skipped the age question, is treated as a child. The policy treats unknown age like a child, so the game does too.

  • Children: child-directed and under-age-of-consent tags on, maximum rating G, personalization off. On iPhone, children are never shown Apple's tracking prompt.
  • 13 and over: maximum rating PG; personalized ads only if the player leaves that option on in Settings, and on iPhone only after Apple's tracking prompt.
  • No app-open ads for children, and full-screen ads between activities are spaced further apart for them than for older players.
  • Ads wait for natural pauses between activities, with daily and per-session caps.
  • Rewarded ads pay only when the ad network confirms the reward, so a closed or failed ad never pays and never pays twice.
  • After a real-money purchase, full-screen ads pause for a while, and a one-time No Ads purchase removes the full-screen ones.
  • No analytics in the game at all, which keeps the Data safety form short and honest.

The privacy policy and the parents' guide describe the same rules in plain words. Writing those pages before the code was finished helped: every rule had to be simple enough to explain to a parent.

A checklist before you submit

  1. Target audience set honestly; a neutral age screen if the audience is mixed.
  2. Only Families Self-Certified ad SDKs, including anything behind mediation.
  3. Child-directed (or age-restricted) treatment and a G rating for children and unknown ages.
  4. No advertising ID or other persistent identifiers sent for children or unknown ages.
  5. No full-screen ads at launch for children, no ads that look like content, every ad easy to close.
  6. Data safety form and content rating questionnaire answered to match what the app really does.
  7. An app-ads.txt file on your developer website (see my app-ads.txt guide).

Sources

More posts

Godot on iOS: from an uneven 60 fps to 120 Hz with MetalA Godot 4 game stuck near 60 fps on an iPhone 14 Pro with a main thread busy only 4 ms a frame. How a phone bench and Instruments found the cause, and how switching iOS to Metal gave 119 fps. Quest pacing: measuring where a 150-level game goes flatHow I measured the story pacing of Tibblo's 763-day road from level 1 to 150, found where it went flat after level 40, and fixed it with three-step arcs, a daily limit and a 'Last time…' card.