Banner Ad is a graphic advertising format in mobile apps, represented by a rectangular banner embedded in the app interface. According to Statista, 2025, the in-app advertising market exceeded $380 billion, of which 18% comes from banner formats. Banner Ads remain the simplest and most accessible monetization method for developers of free apps.
Key Takeaways
Banner Ad is a mobile advertising format that displays a graphic or text ad within the app interface. Standard sizes: 320×50 px (banner), 320×100 px (large banner), 300×250 px (medium rectangle), 728×90 px (leaderboard for tablets). The banner occupies a fixed area of the screen — usually 5–15% of the display height — and automatically refreshes every 30–60 seconds.
According to Google AdMob (2025), adaptive banners are the preferred format, automatically adjusting to the device screen width. Adaptive banner provides a fill rate of 98% compared to 85% for fixed banners because the ad network can match an ad to the exact block size. Average banner CTR is 0.1–0.5%, and Conversion Rate from clicks is 2–5%.
Banner Ad is the least invasive ad format: the banner does not constantly cover content (unlike interstitial), does not require user action (unlike rewarded video), and does not interrupt the user experience. However, low eCPM makes banners effective only with a large number of impressions — apps with DAU less than 10,000 may not recoup the cost of integrating banner ads. According to Appodeal (2025), the minimum threshold for Banner Ad profitability is 30,000 impressions per day.
A Banner Ad works through advertising SDKs (Software Development Kits) that are embedded in the app and manage the loading, display, and refresh of ads.
The ad SDK (e.g., Google Mobile Ads SDK) loads an ad from the ad network when the app launches. The banner requests an ad, the network conducts a real-time bidding auction among advertisers, and the winning ad is displayed in the banner. After 30–60 seconds the process repeats (auto-refresh). The developer earns revenue from impressions (CPM) or clicks (CPC), depending on the network terms.
RTB is a real-time auction where advertisers bid for each impression. When a banner request is made, the following data is transmitted: geo, device type, app category, user history (if consented). The auction winner is the advertiser with the highest bid. Average auction time is 100–200 ms. In-app bidding increases eCPM by 20–40% compared to the traditional waterfall model (PubMatic, 2025 data).
Example of integrating an AdMob adaptive banner into an app using Kotlin:
class MainActivity : AppCompatActivity() {
private lateinit var adView: AdView
private val adUnitId = "ca-app-pub-3940256099942544/6300978111"
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_main)
adView = AdView(this)
adView.adUnitId = adUnitId
adView.adSize = AdSize.getCurrentOrientationAnchoredAdaptiveBannerAdSize(
this, AdSize.FULL_WIDTH
)
val adContainer = findViewById<FrameLayout>(R.id.ad_container)
adContainer.addView(adView)
loadBanner()
}
private fun loadBanner() {
val adRequest = AdRequest.Builder().build()
adView.loadAd(adRequest)
}
override fun onPause() {
adView.pause()
super.onPause()
}
override fun onResume() {
super.onResume()
adView.resume()
}
override fun onDestroy() {
adView.destroy()
super.onDestroy()
}
}
Banner Ads differ in size, behavior, and display technology. The choice of banner type affects eCPM, user experience, and integration complexity.
A static banner is a graphic image (PNG, JPG) or HTML5 animation of a fixed size. Sizes: 320×50 px for phones, 728×90 px for tablets. Static banners have the lowest eCPM ($0.5–$2) due to low engagement. The advantage is minimal impact on app performance (no CPU/GPU load). They are used in utilities, catalogs, and content apps.
Adaptive banners automatically adjust width and height to the device screen size. Google AdMob recommends adaptive banners as the standard: they provide maximum fill rate and 15–25% higher eCPM compared to fixed banners. Adaptive banners are available in anchored (fixed position at bottom/top) and inline (embedded in scrollable content) variants. Inline adaptive banners are the newest format, integrated into a list or feed.
Rich Media banners are interactive ads with video, animation, swipes, and forms. They support MRAID (Mobile Rich Media Ad Interface Definitions) — the IAB standard for interactive advertising. Rich Media banners have an eCPM of $3–$8 but require loading 2–5 MB of data and may reduce app performance on older devices. They are used in premium apps and brand campaigns.
Collapsible is a Google AdMob format where a large banner (320×100 px) automatically collapses to standard size (320×50 px) after 10–15 seconds. The format allows displaying more information in the first few seconds without permanently occupying screen space. Collapsible banners show 20–30% higher eCPM than standard ones, while Retention Rate does not decrease (Google AdMob, 2025 data).
Choosing an ad network critically affects eCPM, fill rate, and revenue stability. Different networks specialize in different regions and app categories.
| Network | eCPM (US) | Fill Rate | Feature |
|---|---|---|---|
| AdMob | $1.5–$3 | 95–98% | Largest network, stable payments |
| AppLovin | $2–$4 | 90–95% | High eCPM, in-app bidding |
| Meta Audience Network | $3–$7 | 40–70% | Maximum eCPM, low fill rate |
| Unity Ads | $1–$3 | 85–90% | Good for games |
| IronSource | $1.5–$3.5 | 85–90% | Mediation and A/B testing |
Mediation is a technology where the ad platform queries multiple networks and displays the ad with the highest eCPM. For Banner Ads, mediation is especially important due to low eCPM — even a 20% increase is significant. Popular mediation platforms: AdMob Mediation (free), AppLovin MAX (free), IronSource (free). Mediation increases banner eCPM by 20–40% and fill rate up to 97% (PubMatic, 2025 data).
In-app bidding is the next level of mediation, where all networks participate in a single auction simultaneously (rather than sequentially as in waterfall). For Banner Ads, in-app bidding gives an eCPM increase of 15–30% due to equal access of all networks to each impression. Supported by AppLovin MAX, AdMob (with Open Bidding), and IronSource.
Banner placement is a key factor determining both revenue and user experience. Incorrect placement can reduce Retention by 30–50%.
The optimal position is at the bottom of the screen (bottom anchor). The banner does not cover content and users get used to its presence. The top position (top anchor) is suitable for apps with bottom navigation. Floating banners are the worst option: they cover content and annoy users. According to Google (2025), bottom banners have 15% higher CTR than top banners and do not reduce Retention.
Auto-refresh is the standard mechanism for Banner Ads, replacing the ad every 30–60 seconds. Recommended interval: 60 seconds for content apps (users are not distracted), 30 seconds for utilities (short sessions). Too frequent refresh (< 30 sec) does not increase revenue — advertisers pay less for impressions in high-density ad apps. Google AdMob does not recommend intervals shorter than 30 seconds.
Proper handling of the Activity lifecycle is critical for Banner Ads. The banner must be paused on onPause, resumed on onResume, and destroyed on onDestroy. Incorrect management causes memory leaks and traffic waste. Correct lifecycle management is shown in the integration code above — onPause, onResume, onDestroy are mandatory.
Dark theme affects banner ads: dark theme users are 20–30% less likely to click on bright banners (AppDynamics, 2025 data). AdMob supports forceAdaptiveBanner for contrast adaptation. For apps with dark theme it is recommended to: use native ads (blend into the theme), choose advertisers with dark-mode creatives, and use a neutral color palette for the banner.
Monitoring Banner Ad metrics allows evaluating the effectiveness of ad monetization and optimizing placement in a timely manner.
| Metric | Description | Benchmark |
|---|---|---|
| Impressions | Number of banner impressions | Depends on DAU |
| eCPM | Revenue per 1000 impressions | $0.5–$3 (US) |
| CTR | Click-Through Rate | 0.1–0.5% |
| Fill Rate | % of successful requests | > 95% |
| Revenue per DAU | Revenue per active user | $0.01–$0.05/day |
| Impression RPM | Revenue per 1000 impressions | Equals eCPM |
Revenue from Banner Ads is calculated using the formula: Daily Revenue = DAU × Sessions × Banner Shows per Session × eCPM / 1000. Example: 100,000 DAU, 3 sessions per day, banner shown in 2 sessions, eCPM $2. Revenue = 100,000 × 3 × 0.7 × $2 / 1000 = $420 per day. With mediation, eCPM can increase to $3, raising daily revenue to $630. For comparison, interstitial with eCPM $8 at one impression per user per day would yield $800 — banners are effective only with high session frequency.
LTV of a user monetized solely by banners: LTV = Daily Revenue per User × Average Lifetime Days. At Daily Revenue per User $0.02 (100,000 DAU, $2000 per day) and an average lifetime of 120 days, LTV = $2.40. For profitability, CPI must be below $2.40. At a game CPI of $2.80, banner-only monetization may be unprofitable — a combination with interstitial or rewarded video is needed to achieve LTV > CPI.
Testing banner position, size, and frequency is an ongoing process. Google recommends A/B testing with the following scheme: control group (70% traffic) with current settings, test group (30% traffic) with new ones. Metrics for comparison: Revenue per User, Retention D7, CTR, and eCPM. After 7–14 days of testing, a decision is made. Typical A/B tests for Banner Ads: bottom vs top, 320×50 vs 320×100, 30 sec refresh vs 60 sec refresh.
Frequently Asked Questions
Good eCPM for banners is $2–$4 in the US, average is $1–$2, low is < $1. For other regions, eCPM is 2–5 times lower. Mediation and in-app bidding increase eCPM by 20–40% compared to a single network.
Optimally — at the bottom of the screen (bottom anchor). The banner does not cover content and does not interfere with navigation. Top placement is suitable for apps with bottom navigation. Avoid floating banners that cover content.
Only one banner per screen. Google AdMob policy — no more than one banner ad view per screen. Violation may lead to account suspension. The exception is mediation with collapsible banners from different networks, but only one visible.
Impact is minimal: the banner SDK adds 2–5 MB to the app size and 10–30 MB of RAM. On modern devices, the effect on FPS is negligible. On devices with RAM < 2 GB, lazy loading with a 1–2 second delay after launch is recommended.
Banner — stable, predictable revenue with minimal UX impact. Interstitial — higher eCPM ($5–15 vs $0.5–3), but risk of user loss with frequent display. Optimal combination: banner always + interstitial no more than once every 90 seconds.
Summary
We will develop a mobile application turnkey
IT Sectr creates iOS and Android applications for startups and businesses since 2017. We will advise you and propose the best solution.
Read also