Guide to common Google Mobile Ads SDK error codes in AdMob

• Confirm that your app is published and ready to monetize.
• If testing new ad units, wait about 2 hours for them to become active.
• Verify the ad unit being tested is targeted by a mediation group or a campaign.
• Contact support if you’ve tried all of the above.

Reference the sample code and sample apps provided in the developer documentation to help you implement the functions correctly.

• Developer docs: 
  Android, iOS, Unity or Flutter
• Sample apps:
  Android, iOS, Unity or Flutter

You receive this error when an ad request cannot be filled due to network connectivity.

This could be due to a user’s phone switching networks or network disturbances distorting the communication between the app and the ad server.

Ensure you have a stable internet connection.

If you have this error code, it means that the ad request was successful, but no ad was returned due to lack of demand.

What is happening? Advertisers can target specific regions, platforms and user profiles based on business relevance, which can sometimes result in lower availability of ads for a particular region or user profile.

This error code suggests that the implementation is correct, but the ad request wasn’t filled because of lack of availability of a suitable ad at that particular instant of time when an ad request was sent from the app.

• Use the Ads not showing troubleshooter and check resources to troubleshoot ads not showing to locate possible root cause of ads not showing.
• Test your app with ad inspector to analyze the ad request, ad sources, privacy and bidding signals, and more. To use ad Inspector, you must first register a test device.
• If your implementation looks correct after checking the above resources, then ads not showing could be expected behavior as there may not have been advertising demand available at the time of your request.