- Use
- AdMob (native)
- Banner
- Bottom, above tabs
- Interstitial
- Natural breaks, capped
- Verify
- app-ads.txt
AdMob vs your website's ads
Web ad networks are built for browsers. Google offers a separate path for showing web ads in app WebViews, but the simplest setup for a converted app is to hide your web ads inside the app (using an .in-app CSS class) and let the converter show AdMob units natively. You avoid double ads and policy grey areas.
Placements that work
| Format | Where | Notes |
|---|---|---|
| Adaptive banner | Bottom of the screen, above tabs | Always visible, low annoyance |
| Interstitial | Between actions: after reading an article, after a level | Cap frequency (e.g. not more than once every few minutes) |
| Rewarded | Optional: “watch an ad to unlock” | Only if you have something to unlock |
Rules that get apps suspended
- Ads that cover content or buttons, or appear right where users tap.
- Interstitials on app launch or exit.
- Ads in apps for children without the right settings.
- Encouraging clicks.
app-ads.txt
Publish https://yourdomain.com/app-ads.txt with your AdMob publisher line, and list the same domain as the developer website on your Play listing. It verifies your inventory and protects revenue.
When ads aren't worth it
Shops, booking and SaaS apps usually earn more from conversions than from ads — an ad is a reason for a customer to leave. Ads make sense for content, tools and games.
Frequently asked
Can I use AdSense in my converted app?
AdSense isn't designed for in-app WebViews; Google provides specific WebView ad integrations and AdMob for apps. For converted apps, native AdMob units are the straightforward choice.