How long mopub ad unit takes to warm up? - android

I'm using successfully MoPub displaying ads correclty. I created a new Ad Unit in the MoPub publisher console, I changed the current id with the new id but no ads are displayed anymore.
In the logcat I see the following message:
Ad Unit (xxxxxxxxxxxxxxx) is still warming up. Please try again in a few minutes.
I waited for 8 hours but still get no ads. What's I'm doing wrong?

Today I started receiving ads. It seems that up to 2 days are needed to warm up ad-units. Also posted a request on the mopub forum without having got any response (https://groups.google.com/a/mopub.com/forum/#!category-topic/mopub-users/technical-integration/71iV6IFEFJ0)

ad unit still warming up is something you'd see in an ad unit that doesn't receive a lot of traffic. If you try again in a few minutes/make a few more requests, the ad unit should respond with an ad.

Related

Admob ad request always return code 3

I implement Admob in one of my android application. First time it has a banner add bellow of my application. But after adding banner ad in RecylearView after 8 items then problem occurs. 90% cases it returns response code 3.
Maximum time it showing me:
I/Ads: No fill from ad server.
W/Ads: Failed to load ad: 3
Here response code: 3 means The ad request was successful, but no ad was returned due to lack of ad inventory. But other apps showing ads frequently in same device.
Notes:
It showing demo ad when i test in TestDevice
Problem occurring only non test devices
Rare cases it successfully return ad.
Can anyone please help me to recover from this issue.Is there any issue in my ad_unit or adMob?
Here my code is correct. The issue is that AdMob does not always have an ad to return for every request. This may happen particularly if you have just registered your AdMob publisher ID, as it takes some time and multiple requests before the new ID starts returning ads.
Another reason your fill rate may be low is that you don't have AdSense backfill enabled, or you have filtered out some ads. Check your app settings to see if that is the case.
According to documentation :-
public static final int ERROR_CODE_NO_FILL
The ad request was successful, but no ad was returned due to lack of ad inventory.
Constant Value: 3
Which means:-
If you are getting this error, then your code is correct. The issue is
that AdMob does not always have an ad to return for every request.
This may happen particularly if you have just registered your AdMob
publisher ID, as it takes some time and multiple requests before the
new ID starts returning ads.
Another reason your fill rate may be low is that you don't have
AdSense backfill enabled, or you have filtered out some ads. Check
your app settings to see if that is the case.
Thanks :)

Cannot test the admob API throws Ad failed error

When I try to test the Admob api I get the following error in my logcat.
Ad failed: com.google.ads.AdView{40db6b18 V.E..... ......I. 0,0-480,610 #7f070001 app:id/adView}Ad request successful, but no ad returned due to lack of ad inventory.
Admob can return a blank ad (depends on targeting, user preferences etc), there is a fill rate in admob less then 100%, my suggestion to you - create some "house ads" that will return when you ads are blank.
*Or simply add some test ads, as i remember you can find such a feature in admob.
Your Logcat showing (no ad returned due to lack of ad inventory). It Clearly means that admob is not serving any advertisement to your app at that time.
It is probably because of the fill rate.
You can use AdSense to help backfill ads when AdMod does not have any available.

Using Android Admob sdk I receive same banner all the time

Using Android Admob sdk I receive same banner all the time. On different devices banner is different.
Traces show request for ad and response.
No error or warnings about admob.
Code from my program:
OnCreate()
{
....
AdRequest adRequest = new AdRequest();
m_adView.loadAd(adRequest);
}
Here is request sent from admob sdk to server:
10-12 13:09:28.828: I/Ads(3865): adRequestUrlHtml: AFMA_buildAdURL({"preqs":10,"session_id":"5459438313201923230","u_sd":1.5,"seq_num":"19","slotname":"a14faa4a66469eb","u_w":320,"msid":"com.datecs.bgmaps","js":"afma-sdk-a-v6.1.0","toar":0,"mv":"8014017.com.android.vending","isu":"CF95DC53F383F9A836FD749F3EF439CD","cipa":0,"format":"320x50_mb","net":"wi","app_name":"25.android.com.datecs.bgmaps","hl":"bg","extras":{"_norefresh":"t","gw":1,"mad_hac":"1"},"u_h":533,"carrier":"28401","ptime":362288,"u_audio":3});
I saw "_norefresh" in request url, but I control banners from admob site - refresh rate 45sek. So tis souldn't be a problem.
Any suggestions?
Even if I stop internet - my ads continue to show on screen. sdk repeats last banners cached somewhere in device. On 20-30 ad request I receive once: 'No ads to serve for you' or some like this. So Admob repeat last banners when there is no connection or no new ads from google.
False alarm and spent 2 days to fight nonexistent problem.

onFailedToReceiveAd(Ad request successful, but no ad returned due to lack of ad inventory when using admob with adwhirl

i just want to know if this problem is server side...or i must fix something in my code...
onFailedToReceiveAd(Ad request successful, but no ad returned due to lack of ad inventory
I'm using admob with adwhirl to show ads in my android application.
If you are getting this error, then your code is correct. The issue is that AdMob does not always have an ad to return for every request. This may happen particularly if you have just registered your AdMob publisher ID, as it takes some time and multiple requests before the new ID starts returning ads.
Another reason your fill rate may be low is that you don't have AdSense backfill enabled, or you have filtered out some ads. Check your app settings to see if that is the case.
Finally, a test you can run to see if your AdWhirl code is implemented correctly is to request a test ad. You can do this by specifying test mode in AdWhirl:
AdWhirlTargeting.setTestMode(true);
If you get back a test ad, you'll know your code is working as intended.
One of the solutions you could try:
Some times this will happened if you changed language of your Android device to exotic language (Russian for example). Try to change it back to English and AdMob will find appropriate ad for you. Or you could go to the Google Settings->Ads->Reset advertising ID
I've just found that such error is shown if your AdMob account has been banned. But it works with a test device ID.
Note that this might happen aswell if you're using (forcing) a custom width and height for the banners.
You should use the ones that DOC states:
https://developers.google.com/mobile-ads-sdk/docs/admob/intermediate#play
If you set a custom width and height like:
new AdSize( 521,300 );
It's going to reply with the error you mentioned.
I know this was from long time ago, but here's something i did which solved this problem.
1. on your admob account, click on "manage settings" in the app you've created.
2. click on "edit".
3. under "Android Package URL:" leave blank, and then save settings.
*after you'll save, it'll show this box as "market://", which is fine.
I had this problem when using Rewarded Interstitial (beta).
Changing to Rewarded solved the problem.

Android Admob testmode : No fill. Server replied that no ads are available

I followed the admob SDK tutorial to set up ads for my android application.
But I get no test adds returned :(. Also, on the admob site no requests are registered.
When I run my app the log says the following :
03-18 08:23:56.392: INFO/AdMobSDK(1278): Publisher ID set to xxxxxxxx
03-18 08:23:56.392: INFO/AdMobSDK(1278): Making ad request in test mode
03-18 08:23:56.513: INFO/AdMobSDK(1278): No fill. Server replied that no ads are available (120ms)
The xxx is my publisher Id, but I hid it here with x'es :).
I did set my publisher id in the manifest.
I did set the "setTestDevices method" in my code with the device id the logcat requested
AdManager.setTestDevices( new String[] { "xxxxxxxxxxxxxxxxxxxx", } );
What did I do wrong?? I should get test ads on my phone I suppose?
I find AdMob's test mode to be very unreliable. Sometimes I get no ad, sometimes a test ad, and occasionally real ads show.
I'd not worry about it too much, and instead make sure that ads are showing on the live app. you may want to look at Adwhirl if you don't get ads showing. A fill-reate error basically means AdMob didn't sell all the ad space, so if you want ads to always be shown you may need to look beyond AdMob. Adwhirl is an aggregator, owned by AdMob, so it'll pull ads from other networks if they don't have an ad.

Categories

Resources