Why are ads not working?
It’s very common to take time because you don’t have any users yet. So if you are sure setup is right then when a number of users increase the ads automatically showing. Note:
- Make sure that you don’t click your own ads (it will block your account)
- During configuration on RocketWeb, you set AdMob delay currently (Best time is 5~60 second)
- Your website content doesn’t violate the google policy.
- More about policy: https://support.google.com/admob/answer/6128543?hl=en&ref_topic=2745287
How you know the setup is fine?
Please run your app on Emulator. If you see the test ads then setup is fine. It will show on the real device soon. When a number of user increase ads will showing. And some time for your content and location google doesn’t have ads to show.
How do you see the errors?
If the ads not showing on Emulator then to see the error click on Logcat. You will found the error code. And every code has a specific meaning. For more: https://support.google.com/admob/thread/3494603?hl=en
Common Error Codes are :
- Error Code 0 : ERROR_CODE_INTERNAL_ERROR
This indicates that something happened internally; for instance, an invalid response was received from the ad server.Newly created Ad Units can take upto 2 hours to become active (SpinUp Time). Any Ad requests from newly created Ad Units would also receive Error Code 0 in response to Ad requests until they are ready to serve live ads.What to do? Test Ads!!
- Error Code 1 : ERROR_CODE_INVALID_REQUEST
The ad request was invalid; for instance, the ad unit ID was incorrect.This commonly suggests that the Ad Request implementation is not as per the SDK’s requirements – Resources like the sample codes and sample apps provided in the developer documentation can help in implementing the functions correctly.
- Error Code 2 : ERROR_CODE_NETWORK_ERROR
The ad request was unsuccessful 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. Some Telecom providers may also limit specific traffic due to policy, which can also lead to such an error.
- Error Code 3 : ERROR_CODE_NO_FILL
Description (Dev Docs Link) : The ad request was successful, but no ad was returned due to lack of ad inventory.Why is it 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. Error code suggests that the implementation is correct, and that the Ad Request was not 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.Policy related restrictions on certain Apps or Ad Units will also lead to Error Code 3 being returned in response to Ad Requests.
Tips:
If sill you fetch problem then follow this and use a large interval time. Ex: 30000 = 30 second. Follow: https://help.infixsoft.com/error-the-google-mobile-ads-sdk-was-initialized-incorrectly-admob-publishers/
