Android ads: testing and monetization are different milestones
Use AdMob guidance to distinguish rewarded-ad testing, privacy handling, readiness review and direct APK distribution.
0101 / Check the distribution route
Track direct APK delivery, store publication and ad readiness separately. Full AdMob serving requires review and a public listing in a supported store. Website distribution can validate installation and product flows without implying Google Play publication or ad approval.
0202 / Test with official test ads
Use Google Mobile Ads SDK test units or test-device settings. Handle loading, failure, presentation, interruption and dismissal, with voluntary participation. Grant points from the actual reward event and prevent duplicate credits server-side. Dismissal alone is not an earned reward.
0303 / Complete privacy handling first
Follow UMP guidance to refresh consent information on each launch, show required forms and check whether ads can be requested. Offer privacy options when required. Test first-time, refusal and existing-consent states rather than permanently caching a boolean.
0404 / Verify publication and activation separately
Prepare authentic store metadata, privacy information, signing and applicable testing. Linking the store still triggers an independent ad review. Keep a server-side switch and activate production IDs only when ready. Core creation, account and download flows should survive ad failures.
New Google Play personal accounts and other stores have their own testing and release rules. A website download QR code is not evidence of store approval, ad approval or future income.
Sources & further reading
An original Qiyue synthesis of these sources. Suggested actions are not platform guarantees.