If your app is aimed at children, or if your ads can appear in kid-directed inventory, the rules governing playable ads change materially — and the consequences of getting it wrong are regulatory rather than a rejected creative. This guide covers what applies, what it means for the creative itself, and where teams most often get caught. It is an orientation, not legal advice; anything touching children's data warrants a lawyer.
Three overlapping rule sets
They are frequently discussed as one thing and are not.
- COPPA — US law governing collection of personal information from children under 13. It applies to you if your service is child-directed or if you have actual knowledge that you are collecting from children. Liability extends to the SDKs you embed: if an ad network or analytics SDK in your app collects from children without proper consent, that is your exposure, not only theirs.
- Google Play Families policy — a platform requirement for apps targeting children. It mandates certified ad SDKs, prohibits personalised advertising to children, and requires a neutral age screen for mixed-audience apps so children are served non-personalised ads.
- Apple's Kids Category — the strictest of the three. Behavioural advertising and third-party data collection are prohibited outright for apps in that category.
Recent COPPA updates have tightened things further: separate opt-in consent, retention limits, and a requirement that parental notices state specifically how each piece of information will be used — generic language about improving services no longer satisfies the standard.
What changes in the creative itself
The rule with the most direct creative consequence is the prohibition on designs that produce inadvertent clicks from child users. Playables are unusually exposed here, because the format's whole premise is inviting a tap.
- Keep the play area and the CTA clearly separate. A creative where any tap advances toward the store is exactly the pattern this rule targets.
- Do not disguise the CTA as gameplay. A button styled as a game element that opens a store listing is a deliberate confusion of the two.
- Give close controls real, reachable hit areas. Undersized or offset close buttons are a recognised dark pattern and are enforced against.
- Avoid fake interface elements — imitation system dialogs, false notification badges, decoy close buttons.
- Avoid pressure mechanics aimed at children: countdown urgency, loss framing, or implying something is lost by not installing.
The design test
Ask whether a seven-year-old could reach the store listing while believing they were still playing. If the answer is yes, the creative is a problem regardless of intent — enforcement looks at the design's effect, not what you meant by it.
Targeting and measurement
Personalised advertising to children is off the table. Practically that means contextual targeting only, and it means the measurement chain you rely on elsewhere is restricted. Advertising identifiers should not be used for children, so device-level attribution is not available, and several standard optimisation levers are unavailable in kid-directed campaigns.
This has a knock-on effect for anything that personalises the destination. Carrying a user's in-ad choices into the click is a mechanic worth reviewing carefully in a child-directed context — even where the values are innocuous, you are creating a data flow about a child's behaviour, and both the flow and its retention need to be justified rather than assumed acceptable.
Mixed audiences are the hard case
Most teams are not making a children's app. They are making a casual game with broad appeal, some of whose users are children — which is the situation the rules handle least conveniently.
The platform answer is a neutral age screen: an age gate that does not encourage users to enter a particular answer, with children routed to non-personalised advertising. Neutral means neutral. An age gate placed after a screen showing what the user will miss by being under 13, or one that pre-fills an adult birth year, is not neutral and has been treated as non-compliant.
Where teams actually get caught
- Assuming the network handles it. Certified SDKs and correct flags are necessary, not sufficient — the creative design is still yours.
- One creative across all inventory. A playable built for general audiences may include mechanics that are fine broadly and non-compliant in kid-directed placements.
- Analytics inside the creative. Anything measuring behaviour inside a playable shown to children is a data flow that needs justifying.
- Forgetting the end card. The rules apply to the whole creative, and the end card is where the pressure mechanics usually live.
- Treating an app-level setting as sufficient. Flagging the app correctly does not make a creative compliant.
Keep a separate creative line
The maintainable approach is a distinct set of creatives for child-directed inventory, built to the stricter rules from the start, rather than one creative you hope is acceptable everywhere. It costs one more variant and removes an entire class of risk.
A practical starting checklist
- Determine honestly whether your app is child-directed or mixed-audience, and document the reasoning.
- If mixed, implement a genuinely neutral age screen and route under-13 users to non-personalised ads.
- Confirm every SDK in the app is certified for the relevant programme.
- Review each creative for inadvertent-click design — separate play area, honest CTA, reachable close control.
- Review the end card specifically, not only the interactive portion.
- Review what the creative measures and what leaves it.
- Get the whole arrangement reviewed by counsel before spending, not after.
What still works creatively under the constraints
It is easy to read the above as "do not advertise to children", which is not the conclusion. The constraints remove targeting sophistication and dark patterns; they do not remove the thing that makes playables effective in the first place.
The format's advantage is that it shows rather than tells — and in child-directed inventory, where behavioural targeting is unavailable, showing the actual product is more valuable, not less. You cannot rely on the network finding the right user, so the creative itself has to do the qualifying. A playable that accurately demonstrates the game does exactly that: the children who enjoy the sample are the ones who engage, and no targeting model was needed to find them.
- Lead with the real mechanic. Contextual placement means your audience is broad, so the creative has to self-select its users.
- Keep it genuinely simple. Younger users have less patience for instruction and less tolerance for ambiguity than the general audience you may be used to designing for.
- Make success obvious and generous. Ambiguous feedback is confusing for adults and worse for children.
- Skip urgency entirely. It is both non-compliant in spirit and ineffective — the install decision is usually not the child's to make.
Remember who is deciding
In many households the install is approved by a parent. That makes clarity about what the app actually is more valuable than persuasion aimed at the child — a creative that a parent can glance at and understand is doing work that pressure mechanics never will.
Create playable end cards in minutes—no code required.
Open Playable Ads Maker