Playable Ad Policy: Misleading Creative, Fake UI and What Gets You Banned

Most playable ad guidance is about specifications — sizes, formats, APIs. Those get a creative accepted by a validator. A separate and less-documented set of rules governs whether it stays up, and breaking them costs more than a rejection: repeated violations reach account level, and a suspended ad account is a different kind of problem from a rejected file.

Gameplay authenticity is the big one

The single most enforced content rule for game advertising is that the ad has to represent the actual product. Platforms have tightened this considerably, driven by a genre of advertising where the ad showed a pin-pulling puzzle and the app was an idle city builder with the puzzle appearing, if at all, as an occasional mini-game.

For playables the practical rule is: the mechanic in the ad should be a mechanic the player will meet early in the app, and it should behave the way it behaves in the app. You can simplify, you can make the ad version easier, you can change the art — what you cannot do is advertise a game that does not exist inside the product.

This is also self-interested rather than merely compliant. A mismatch between ad and app shows up as poor retention, and it does so after you have paid for the install. The policy is enforcing something the ROAS report was going to tell you anyway.

Fake system UI

Creatives that imitate operating-system elements are treated as deceptive across essentially every platform: fake close buttons that are actually the click target, simulated notifications, fake download progress bars, imitation battery or signal indicators, and dialogue boxes styled to look like a system prompt.

The rule extends further than people expect. A close button that is real but tiny, or positioned so the thumb naturally hits the CTA instead, falls under the same heading even though nothing about it is technically fake. Networks that supply their own close control frequently ask that the creative not add a second one, precisely because two close buttons is the shape this abuse takes.

Manufactured urgency and false scarcity

A countdown timer implies something expires. If nothing expires, the timer is a false statement, and platform policies on misleading claims cover it. Same for "only 3 left", limited-time framing on an evergreen offer, and progress bars that imply the user has achieved something they have not.

Urgency inside the mechanic is different and entirely legitimate — a timer the player is racing in the game itself is gameplay, not a claim about the offer. The line is whether the urgency is about the interaction or about the commercial proposition.

Claims you have to be able to support

Ratings, download counts, awards and press quotes shown in a creative are claims, and platforms can ask you to substantiate them. A five-star rating graphic on an app rated 3.8 is a straightforward misrepresentation. So is a "#1" badge without the category and timeframe that made it true.

This catches teams out most often with recycled assets. A badge produced when the app genuinely was top of a category stays in the template long after it stopped being accurate, and nobody re-checks it because it is part of the furniture.

Where kids' policy overlaps

If the app or the placement reaches children, a stricter regime applies on top of everything above: no behavioural targeting, no personal data collection, and tighter limits on persuasive design. Mixed audiences are the hard case — an app used by both children and adults falls under the stricter rules for the child portion, and assuming a general-audience exemption because most users are adults is a common and expensive mistake.

The review process is asymmetric

Automated checks on packaging, size and external requests fail immediately at upload. Content judgements — authenticity, misleading claims, fake UI — are made by human reviewers, sometimes after the creative has been serving, and sometimes in response to user reports rather than at submission.

That asymmetry has a practical consequence: passing review is not the same as being compliant. A creative can run for weeks and then be pulled, and the pattern of pulls is what escalates to account level. Treating approval as confirmation that a borderline creative is fine is how teams walk into a suspension.

A pre-flight content check

1. Is the mechanic in this ad genuinely in the app, early enough that a new installer will meet it?
2. Does anything on screen imitate a system control, notification or dialogue?
3. Is there exactly one close affordance, and is it the network's rather than ours?
4. Does every urgency or scarcity cue correspond to something that is actually true?
5. Can we substantiate every rating, count, award and quote shown, today rather than when the asset was made?
6. If this can reach children, does it meet the stricter regime rather than the general one?

None of these require legal review, and running them takes a few minutes per creative. The reason to bother is that the cost curve is steep: a rejected file costs a re-export, a pulled campaign costs momentum, and a suspended account costs the quarter.

Policy is not uniform across regions

The rules above are broadly consistent across the major platforms, but enforcement and specifics are not consistent across markets. Advertising standards differ by jurisdiction on comparative claims, on what counts as an adequate disclosure, and on how gambling-adjacent mechanics — loot boxes, spinning wheels, crate openings — may be depicted at all. A creative that runs without comment in one market can be actioned in another.

Reward and chance mechanics are the most common trip hazard, because they are also among the most effective playable formats. If your creative shows a spin, a crate or any randomised reward, check the target markets specifically rather than assuming approval in one implies approval everywhere.