I am not getting any interstitial ads using the new admob plugin thus far. Not sure if it due to super low fill rate or there is a bug. Anyone with similar issue?
P.S Android is working fine.
One of my apps is having the same issue. The others are ok though.
I think it is admob having low fill rates currently.
It has been like this pretty much since beginning of July. The earnings (Impression RPM) have all gone down considerably across all apps for admob too.
Note: these are all on Android, which seems the reverse of you.
My suggestion is to put some prints in the event listener function to look for the .isError value and print out the event.response value. It will tell you why you did not get an ad. These messages will appear in the device’s console log. If you don’t know how to see the console.log, please read: http://coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/
Rob
Yeah. I should have mentioned. (ok I forgot about it till you mentioned logging :-)).
I checked it last week or week before that… and it said this:
onFailedToReceiveAd(Ad request successful, but no ad returned due to lack of ad inventory.)
Well, that’s about as straight forward of a reason as you can get. Some folks use multiple ad providers so that if one provider can’t deliver the ad, you can call another ad service to try and fulfill the ad. See:
http://coronalabs.com/blog/2013/11/19/tutorial-using-multiple-ad-networks/
However this is sort of a brute force way of dealing with it. AdMob supports something called mediation where you can go into their portral and enable other ad providers in addition to AdMob and they make sure that if they don’t have inventory, they hit one of the partners you setup.
Thanks Rob… I was under the impression that Admob mediation would not work with the corona implementation of admob as it required the actual ad providers sdk to be included in the build.
Am I wrong about this?
Technically I am already using mediation, but they are both admob (eCPM Floor Beta + Admob Network)
hmmmm… Just by way of update in case some else gets caught with this one.
One of my guys had changed some code a few weeks ago and messed up the ad ID. So in effect we were setting the same id for Interstitial and Banner ads. Specifically we were setting the Interstitial ID as the banner ID. So with it set this way we were not getting any Interstitials in this app. But the message is as mentioned above… Perhaps not so obvious a message. Anyway, changed it to correct one and saw my first interstitial in this app in weeks.
This does not change the large slow down in revenues from admob though as it is a low producer anyway for now.
One of my apps is having the same issue. The others are ok though.
I think it is admob having low fill rates currently.
It has been like this pretty much since beginning of July. The earnings (Impression RPM) have all gone down considerably across all apps for admob too.
Note: these are all on Android, which seems the reverse of you.
My suggestion is to put some prints in the event listener function to look for the .isError value and print out the event.response value. It will tell you why you did not get an ad. These messages will appear in the device’s console log. If you don’t know how to see the console.log, please read: http://coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/
Rob
Yeah. I should have mentioned. (ok I forgot about it till you mentioned logging :-)).
I checked it last week or week before that… and it said this:
onFailedToReceiveAd(Ad request successful, but no ad returned due to lack of ad inventory.)
Well, that’s about as straight forward of a reason as you can get. Some folks use multiple ad providers so that if one provider can’t deliver the ad, you can call another ad service to try and fulfill the ad. See:
http://coronalabs.com/blog/2013/11/19/tutorial-using-multiple-ad-networks/
However this is sort of a brute force way of dealing with it. AdMob supports something called mediation where you can go into their portral and enable other ad providers in addition to AdMob and they make sure that if they don’t have inventory, they hit one of the partners you setup.
Thanks Rob… I was under the impression that Admob mediation would not work with the corona implementation of admob as it required the actual ad providers sdk to be included in the build.
Am I wrong about this?
Technically I am already using mediation, but they are both admob (eCPM Floor Beta + Admob Network)
hmmmm… Just by way of update in case some else gets caught with this one.
One of my guys had changed some code a few weeks ago and messed up the ad ID. So in effect we were setting the same id for Interstitial and Banner ads. Specifically we were setting the Interstitial ID as the banner ID. So with it set this way we were not getting any Interstitials in this app. But the message is as mentioned above… Perhaps not so obvious a message. Anyway, changed it to correct one and saw my first interstitial in this app in weeks.
This does not change the large slow down in revenues from admob though as it is a low producer anyway for now.