AdMob suddenly stopped showing ad requests — no policy issue and no app update

[Thunder Tech Dev]

Hello Everyone,

My app was showing AdMob ad requests, match rate, and impressions properly until a few days ago. Suddenly, in just one day, the ad requests dropped to zero, and since then there has been no new data in the AdMob dashboard.

Here’s the situation in detail:

• The app is live and users are active (I can confirm from Firebase Analytics).

• I have not published any new update recently.

• There are no issues shown in the AdMob Policy Center or Account Status.

• AdMob dashboard shows no requests, no match rate, nothing after that sudden drop.

• Previously, it was working perfectly for several months.

Has anyone else experienced this issue recently?
Could it be an invisible serving limit, SDK initialization problem, or ad unit-level restriction?
Any advice or troubleshooting steps from experts would be highly appreciated.

Thank you so much for your time and help! 🙏

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

I would recommend you to check the Common reasons for low match rate help center article for more information. Kindly review it and share your app ID via reply to author option so we can assist you further.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               
[2025-10-27 07:28:40Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vRpTM:ref" (ADR-00336593)

[Vishvkarma Shegukar]

🎯 Top Troubleshooting Checklist

1️⃣ Check SDK Initialization

Your Mobile Ads SDK might not be initializing.

Look in Logcat for this line:

MobileAds: Initialization complete

If this message does not appear, initialization is failing.

2️⃣ Verify Ad Unit IDs

Make sure you are not accidentally using test IDs or incorrect ad unit IDs.

Even a small typo can stop everything.

3️⃣ Update to the Latest Google Mobile Ads SDK

If the SDK version is outdated, ad serving can stop unexpectedly.

Update and try again.

4️⃣ Consent / CMP Issues (For EU users)

In some countries, if user consent isn’t collected properly, ads do not serve.

Check if your consent dialog is working as expected.

5️⃣ Check Request Error Logs

Look for any ad-related error logs in Logcat. Example:

Failed to load ad: X

The error code will help identify the real issue.

6️⃣ Ad Placement Visibility

If the ad view is not visible on screen, requests might not appear.

Make sure it’s not hidden or set to 0dp height/width.

7️⃣ AdMob Fill and Internet Check

Sometimes fill rate drops, but metrics don’t go to zero.

Verify network permissions:

android.permission.INTERNET

android.permission.ACCESS_NETWORK_STATE

8️⃣ Account-Level Serving Limit

Sometimes there is a silent limit while the account is under review

even without alerts in Policy Center.

You may need to contact support with logs and App ID.

✨ Bonus Tip

Try loading a Test Ad.

If the test ad works, your SDK and code are correct.

Which means the problem is likely server-side or account-level.

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-admob-ads-sdk/6947a2b4-64fb-487a-973a-832aeea3b95en%40googlegroups.com.