Reference dossier / Money & markets

A rewarded video unlock must be opt-in, Google's own rules say

Google's own ad documentation requires an explicit choice screen before a rewarded unlock ad plays.

What was announced or recorded

Google's AdMob developer documentation sets out the rules for 'rewarded' video ads on both major mobile platforms: an Android guide and an iOS guide, both retrieved on 16 September 2026. This is the mechanic behind a 'watch an ad to unlock' option, an alternative some apps offer alongside a coin purchase.

What the documents establish

The iOS guide states plainly that rewarded ads 'must always be an opt-in experience', and that a publisher must give the user 'an explicit choice' to view one before it plays. The Android guide describes the same flow from the implementation side: a publisher loads a rewarded-ad object, registers a callback for when the user has earned the reward, and may attach optional server-side verification data so the reward is confirmed by the developer's own server rather than trusted to the app alone. Both guides warn that testing with anything other than Google's designated test ad unit, rather than a live production ad, 'can lead to suspension' of the developer's account. Both also note that the reward callback fires before the ad is dismissed when Google serves the ad directly, but that ads delivered through AdMob Mediation, where a third-party ad network is plugged into the same slot, may fire that callback in a different order.

Announced versus delivered

These pages govern the contract between the ad network and any publisher who chooses to build a rewarded-unlock feature; they say nothing about whether ReelShort, DramaBox, or any other named short-drama app actually uses AdMob or offers a rewarded-unlock option at all, which this dossier has no primary document confirming either way. What the documents do establish is the baseline the format would have to meet if it did: an explicit choice screen before the ad, not an automatic or forced view, and a technical path for verifying the reward server-side rather than trusting the client.

What to watch

Editorially, the way to confirm whether a specific app actually uses this mechanic is to check that app's own help pages or in-app screens for a named 'watch an ad' unlock option, rather than assuming a coin-only app also offers one; this dossier found no such confirmation for the apps discussed elsewhere in it.

  • Does a given short-drama app's own help pages or in-app screens describe a rewarded-video unlock option, separate from its coin purchases?
  • When an ad network other than AdMob is mediated into the same rewarded slot, does the app disclose which network actually served a given ad?
  • Does the opt-in requirement these documents describe match what a user actually sees before a rewarded ad plays inside a specific app?

An ad network's own rulebook describes what a compliant rewarded ad must look like; it is a standard the format could be checked against, not evidence that any particular app currently meets it, and the two should not be collapsed into one claim.

Sources & evidence

Rewarded Ads | Android | Google AdMob ↗

developers.google.com · Official source
Source date: Not stated by source · Checked: 16 Sept 2026

  • States the Android implementation flow for rewarded ads, including server-side verification and the test-ad requirement.
Rewarded Ads | iOS | Google AdMob ↗

developers.google.com · Official source
Source date: Not stated by source · Checked: 16 Sept 2026

  • States the opt-in requirement for rewarded ads and the iOS implementation flow.