Why Your AdMob Ads Are Showing "No Fill" (And How to Actually Fix It)

If you've integrated Google AdMob into an Android app, you've probably seen it: your interstitial or banner ad fails to load, and Logcat shows Error code: 3 — "No Fill." The instinctive reaction is to assume something's wrong with your implementation. Nine times out of ten, that's not where the problem actually is.

We've debugged this exact issue across several Android apps — ringtone apps, utility apps, news aggregators — and the pattern holds: the ad request code is usually fine. The real cause almost always sits in the AdMob account or ad unit configuration, not in your Java or Kotlin.

What "No Fill" actually means

No Fill doesn't mean your integration is broken. It means AdMob's ad request succeeded, but no advertiser had a relevant ad to serve for that specific request at that moment. Your code did its job — it asked for an ad, and the honest answer that came back was "nothing available right now."

The most common real causes

1. The ad unit is brand new. Freshly created ad units in AdMob often take a few hours, sometimes longer, to start returning fills consistently while Google's system "learns" the inventory for that unit.
2. Low fill rate for your app's region or category. Some countries and app categories simply have fewer advertisers bidding at any given moment. This is normal and fluctuates by time of day.
3. Test ad unit ID left in a production build, or vice versa. Mixing up your test ad unit ID and your live one is one of the most common causes we see — and it produces exactly this symptom.
4. Account or policy restrictions. If your AdMob account has an active policy violation notice, ad serving can be limited or paused entirely on affected units, even though your code works perfectly.
5. App not yet fully approved. Newly linked apps sometimes need to go through AdMob's app review before ad serving ramps up to normal levels.
6. Overly aggressive frequency capping or targeting. If you've set tight frequency caps or narrow targeting in your ad unit settings, you can end up starving your own inventory.

How to actually diagnose it

Before touching any code, work through this checklist in order:

• Open the AdMob console and check for any policy or account status messages at the top of the dashboard — this is the first thing to rule out.
• Confirm you're using the correct ad unit ID for the build type you're testing (test vs. production).
• Check the "Ad unit status" for the specific unit — make sure it's marked active, not paused.
• Look at your fill rate reporting by country. A low fill rate concentrated in one region is very different from a global outage.
• If you're using mediation, check whether other networks in your waterfall are configured and active — a single-network setup with no fallback is far more likely to hit "No Fill."

Where code actually matters

Once you've ruled out the account-side causes above, there are a few implementation patterns worth checking:

• Preload, don't request-on-demand. For interstitials, load the next ad as soon as the current one is dismissed, rather than requesting one right when you need to show it.
• Add a fallback path. Use FullScreenContentCallback to detect load failures and continue your app's flow normally instead of blocking navigation on an ad that never arrives.
• Don't retry too aggressively. Hammering the ad server with repeated requests in a tight loop after a No Fill doesn't help — it can make fill rates worse and risks policy issues.

InterstitialAd.load(context, adUnitId, adRequest, new InterstitialAdLoadCallback() {
    @Override
    public void onAdFailedToLoad(LoadAdError loadAdError) {
        // Don't block your app's flow — continue normally
        // and try preloading again for next time.
        interstitialAd = null;
    }

    @Override
    public void onAdLoaded(InterstitialAd ad) {
        interstitialAd = ad;
    }
});

The takeaway

Before spending hours re-reading your ad integration code, check the AdMob console first. In our experience, the account and configuration side resolves the majority of "No Fill" cases — the code is usually the last place to look, not the first.