inmobi problem they say my account is activated but no ads coming.

[mike docey]

 D/InMobiBanner: Ad request successful but no ad served.

I always get admob ads but no inmobi...ecpm set to 0.01 optimization off

[mobileadssdk-a...@google.com]

Hi,

Since you are able to load AdMob Ads on your end, then it's safe to assume that your code implementation for loading Banner Ads is working correctly. On the other hand, I'm afraid the Mobile Ads SDK has no control over which Ad source (e.g. AdMob Network or InMobi) to pull ads from. However, though this is not guaranteed, you can try to set a higher eCPM for your preferred network (InMobi) to possibly prioritize pulling ads from this Ad Network.

As for your mediation setup for InMobi, kindly check if you were able to follow all the necessary steps mentioned in this guide.

For us to test on our end, could you provide to us the Banner Ad Unit Id in question privately using Reply privately to authoroption?

Regards,

Ivan Bautista

Mobile Ads SDK Team

[mobileadssdk-a...@google.com]

Hi,

Thank you for providing your affected Ad Unit Ids privately.

I tested your Ad Unit Ids with our sample apps and I was able to load ads successfully. For your Banner Ad Unit Ids, it seems like I'm getting mostly AdMob Ads. However, for your Rewarded Ad Unit Ids, I was able to load what seems to be a test ad from AdColony.

I've captured the below device logs while testing one of your Ad Unit Ids. The below logs containing information about the server parameters (redacted) set for your mediated Networks is a good indication that the mediation setup is working correctly.

com.google.ads.rewardedvideoexample D/InMobiAdapter: initialize called from InMobiAdapter.

com.google.ads.rewardedvideoexample W/Ads: Server parameters: {"accountid”:”XXXXXXXXXXXXXXXXX”,”gwhirl_share_location":"1","placementid”:”XXXXXXXX”}

………….

com.google.ads.rewardedvideoexample W/Ads: Server parameters: {"app_id”:”XXXXXXXXXXXXXXXX”,”gwhirl_share_location":"1","zone_ids”:”XXXXXXXXXXXXXX”}

com.google.ads.rewardedvideoexample I/AdColony [INFO]: Configuring AdColony

That said, you can try setting a relatively higher eCPM for your preferred Ad Network to increase the possibility of it getting prioritized from the other Ad sources. Please note that any changes in the AdMob UI (e.g. eCPM changes) will take some time (around a few hours) to take effect.

[mg]

ca you try the sample with android 5.1 lollipop?

it seems on this version i never get inmobi banners. rewarded for inmobi came through

[mg]

i asked inmoby support why are there so many requests and so few impression  they said i should increase the number of requests how do i do that? decrease ad refres interval?

On Mon, Jun 11, 2018, 14:47 <mobileadssdk-a...@google.com> wrote:

[mobileadssdk-a...@google.com]

Hi,

I'm afraid there is no actual Android 5.1 device available on my end right now to test it with. That said, I tested your 2 Banner Ad Unit Ids with our BannerExample app (with the InMobi SDK and adapter imported) instead, and ran it on an Android 5.1 emulator, and I was able to load ads successfully. Please note that the Mobile Ads SDK supports Android API 14 (Android 4.0.1) or higher and the InMobi Ad Network supports Android API 15 (Android 4.0.3) or later so testing it on an Android 5.1 device shouldn't be an issue. 

Given that you were able to load AdMob Banner ads and InMobi Rewarded Ads, we can confirm that your code implementation for loading banner ads and your mediation setup for InMobi are working correctly.

As for your other concern about increasing the AdRequests you sent, you can explicitly send the AdRequests as frequently as you wish, or set a lower custom refresh rate (e.g. 30 seconds). The lower the value of the custom refresh rate, the more frequent the Banner Ad Unit will send an Ad request. However, there is still no assurance that all of these AdRequests will pull ads from InMobi. The closest option to prioritize getting ads from InMobi is to set a higher eCPM for InMobi.

[mg]

I will set refresh to 30 secs. post results later.

[mg]

OK now I get no ads displayed, since I am forcing inmobi ecpm=$1

This is logcat

 I/Ads: Starting ad request.

06-12 10:49:50.836 26051-26051/? I/Ads: Use AdRequest.Builder.addTestDevice("x") to get test ads on this device.

06-12 10:49:51.847 26051-26573/? I/Ads: Trying mediation network: https://googleads.g.doubleclick.net/aclk?sa=L&ai=CEUe5MIkfW6axM5mg3wO6toqgBPnJ2qYF0e-FupIBABAIIPjdnGhgx4CAgMACqQIAAAAAgIQuQagDAaoEKk_QOqqLPRJ0sFCHeBKc_fpaT8jaaTr5SFl19oztKD38-tnRA2wHAswK8ZAGAcAGC4AHgfipMJgHAdIIBwiAYRABGAI&num=1&cid=CAASBORoMNY&sig=AOD64_0JQoZxDF0FGqW3VQRC78H34-0JWw&adurl=http://example.com

06-12 10:49:51.847 26051-26051/? I/Ads: Instantiating mediation adapter: com.google.ads.mediation.inmobi.InMobiAdapter

06-12 10:49:51.867 26051-26051/? W/Ads: Server parameters: {"accountid":"x","gwhirl_share_location":"1","placementid":"x","pubid":"x"}

06-12 10:49:52.107 26051-26573/? I/Ads: No fill from any mediation ad networks.

06-12 10:49:52.107 26051-26051/? I/Ads: Scheduling ad refresh 30000 milliseconds from now.

06-12 10:49:52.107 26051-26051/? W/Ads: Failed to load ad: 3

On Tue, Jun 12, 2018 at 9:35 AM, mg <bosn...@gmail.com> wrote:

I will set refresh to 30 secs. post results later.

[mike docey]

also I get this error in logcat before ads failed message (maybe this is causing something.

com.google.ads.mediation.inmobi.InMobiAdapter cannot be cast to com.google.android.gms.ads.mediation.OnContextChangedListener

[mg]

do you have a sample banner test inmobi integrated someplace so i can test myself?

On Tue, Jun 12, 2018, 11:05 mike docey <bosn...@gmail.com> wrote:

also I get this error in logcat before ads failed message (maybe this is causing something.

com.google.ads.mediation.inmobi.InMobiAdapter cannot be cast to com.google.android.gms.ads.mediation.OnContextChangedListener

On Tuesday, June 12, 2018 at 10:51:59 AM UTC+2, mike docey wrote:

OK now I get no ads displayed, since I am forcing inmobi ecpm=$1

This is logcat

 I/Ads: Starting ad request.

06-12 10:49:50.836 26051-26051/? I/Ads: Use AdRequest.Builder.addTestDevice("x") to get test ads on this device.

06-12 10:49:51.847 26051-26573/? I/Ads: Trying mediation network: https://googleads.g.doubleclick.net/aclk?sa=L&ai=CEUe5MIkfW6axM5mg3wO6toqgBPnJ2qYF0e-FupIBABAIIPjdnGhgx4CAgMACqQIAAAAAgIQuQagDAaoEKk_QOqqLPRJ0sFCHeBKc_fpaT8jaaTr5SFl19oztKD38-tnRA2wHAswK8ZAGAcAGC4AHgfipMJgHAdIIBwiAYRABGAI&num=1&cid=CAASBORoMNY&sig=AOD64_0JQoZxDF0FGqW3VQRC78H34-0JWw&adurl=http://example.com

06-12 10:49:51.847 26051-26051/? I/Ads: Instantiating mediation adapter: com.google.ads.mediation.inmobi.InMobiAdapter

06-12 10:49:51.867 26051-26051/? W/Ads: Server parameters: {"accountid":"x","gwhirl_share_location":"1","placementid":"x","pubid":"x"}

06-12 10:49:52.107 26051-26573/? I/Ads: No fill from any mediation ad networks.

06-12 10:49:52.107 26051-26051/? I/Ads: Scheduling ad refresh 30000 milliseconds from now.

06-12 10:49:52.107 26051-26051/? W/Ads: Failed to load ad: 3

On Tue, Jun 12, 2018 at 9:35 AM, mg <bosn...@gmail.com> wrote:

I will set refresh to 30 secs. post results later.

On Tue, Jun 12, 2018 at 9:25 AM, <mobileadssdk-a...@google.com> wrote:

Hi,

I'm afraid there is no actual Android 5.1 device available on my end right now to test it with. That said, I tested your 2 Banner Ad Unit Ids with our BannerExample app (with the InMobi SDK and adapter imported) instead, and ran it on an Android 5.1 emulator, and I was able to load ads successfully. Please note that the Mobile Ads SDK supports Android API 14 (Android 4.0.1) or higher and the InMobi Ad Network supports Android API 15 (Android 4.0.3) or later so testing it on an Android 5.1 device shouldn't be an issue. 

Given that you were able to load AdMob Banner ads and InMobi Rewarded Ads, we can confirm that your code implementation for loading banner ads and your mediation setup for InMobi are working correctly.

As for your other concern about increasing the AdRequests you sent, you can explicitly send the AdRequests as frequently as you wish, or set a lower custom refresh rate (e.g. 30 seconds). The lower the value of the custom refresh rate, the more frequent the Banner Ad Unit will send an Ad request. However, there is still no assurance that all of these AdRequests will pull ads from InMobi. The closest option to prioritize getting ads from InMobi is to set a higher eCPM for InMobi.

Regards,

Ivan Bautista

Mobile Ads SDK Team

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/rPD-9Nlf5qI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.
To post to this group, send email to google-adm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/354a873e-e693-4740-8b72-0f488eed7a38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mike docey]

did you load inmobi ads successfully? how? do you have a sample integrated for inmobi banner?

[mobileadssdk-a...@google.com]

Hi,

Thank you for getting back to us with more helpful information and for sending your recently captured device logs privately.

Please note that changes made in the AdMob UI, such as setting the eCPM, might take some time (maybe a few hours) to take effect.

That said, are you still getting this error message "com.google.ads.mediation.inmobi.InMobiAdapter cannot be cast to com.google.android.gms.ads.mediation.OnContextChangedListener"? I'm asking because there is no indication of it in the more recent device logs you've shared privately. Looking at your most recent device logs shared privately, I see that the mediation setup is working correctly on your end since your server parameters for InMobi are appearing in the logs and this log message "Instantiating mediation adapter: com.google.ads.mediation.inmobi.InMobiAdapter" is a good indicator as well.

Based from the error message "No fill from any mediation ad networks.", this suggests that there are just no available ads from any of your Ad sources (e.g. AdMob Network or InMobi) and the issue is not specific to your code implementation nor the Mobile Ads SDK. However, if you keep on getting No fills, then I suggest that you reach out to the Product Support Team to have this double checked or use this troubleshooter for additional assistance.

[mike docey]

I am still getting D/InMobiBanner: Ad request successful but no ad served.

I dont know how you loaded the ads on your side?

It seems it tries inmobi fails and then displays admob banner

6:44.425 19315-19528/? I/Ads: Trying mediation network: https://googleads.g.doubleclick.net/aclk?sa=L&ai=C6tdAVLcfW57FMIn63gOy-5WoAvnJ2qYF0e-FupIBABAIIPjdnGhgx4CAgMACqQIAAAAAgIQuQagDAaoEKk_QlQrgN1a_2npfCRJnASQ0Vjw3-w5N0ex0IazoDMV1f9QEkPcOpIjhe5AGAcAGC4AHgfipMJgHAdIIBwiAARABGAI&num=1&cid=CAASBORo3Bg&sig=AOD64_2kHhNaMkPX3FEsCrjVIPii2k8Okg&adurl=http://example.com
06-12 14:06:44.426 19315-19315/? I/Ads: Instantiating mediation adapter: com.google.ads.mediation.inmobi.InMobiAdapter
06-12 14:06:44.427 19315-19315/? W/Ads: Server parameters: {"accountid":"e5f3a29bf614498d8b8e283ef8291c63","gwhirl_share_location":"1","placementid":"422","pubid":"878"}
06-12 14:06:44.451 2401-16419/? I/display: [PrimaryDisplay] [DYNAMIC_RECOMP] HWC_2_GLES by low FPS(0)
06-12 14:06:44.453 2793-2890/? D/LocationManagerService: getProviders()=[gps]
    getBestProvider(Criteria[power=NO_REQ acc=HIGH], true)=gps
06-12 14:06:44.453 2793-2808/? D/LocationManagerService: getLastLocation: Request[ACCURACY_FINE gps requested=0 fastest=0 num=1]
06-12 14:06:44.453 2793-3589/? D/LocationManagerService: getProviders()=[passive, gps, network]
06-12 14:06:44.454 2793-3583/? D/LocationManagerService: getLastLocation: Request[POWER_LOW network requested=0 fastest=0 num=1]
06-12 14:06:44.462 2793-3584/? D/AudioService: getStreamVolume 3 index 20
06-12 14:06:44.470 19315-19530/? I/System.out: (HTTPLog)-Static: isSBSettingEnabled false
    (HTTPLog)-Static: isSBSettingEnabled false
06-12 14:06:44.471 2495-3006/? D/EnterpriseController: netId is 0
06-12 14:06:44.471 2495-3006/? D/Netd: getNetworkForDns: using netid 502 for uid 10160
06-12 14:06:44.471 2495-3006/? D/DnsProxyListener: DNSDBG::dns addrinfo af 2
06-12 14:06:44.614 19315-19315/? D/InMobiBanner: Ad request successful but no ad served.
06-12 14:06:44.614 19315-19528/? I/Ads: Trying mediation network:
06-12 14:06:44.614 19315-19315/? I/Ads: Instantiating mediation adapter: com.google.ads.mediation.admob.AdMobAdapter
06-12 14:06:44.615 19315-19315/? W/Ads: Server parameters: {"gwhirl_share_location":"1","pubid":"187\/cak=no_cache&cadc=ef&caqid=VLcfW6jdLqKl3gPB1J3oCw"}
06-12 14:06:44.629 19315-19315/? D/DynamitePackage: Instantiating com.google.android.gms.ads.ChimeraAdManagerCreatorImpl
06-12 14:06:44.639 19315-19315/? I/Ads: Starting ad request.
06-12 14:06:44.640 19315-19315/? I/Ads: Use AdRequest.Builder.addTestDevice("A9008EB26AA53CA28F3EC472CD0F9B3A") to get test ads on this device.
06-12 14:06:44.648 19315-19315/? W/Ads: Not retrying to fetch app settings
06-12 14:06:44.686 2401-2401/? I/display: [PrimaryDisplay] [DYNAMIC_RECOMP] first frame after HWC_2_GLES
    [PrimaryDisplay] [DYNAMIC_RECOMP] GLES_2_HWC by high FPS(5)
06-12 14:06:44.809 4137-5189/? I/vgd: 45-xlb -- metadata{ service_id: 0 }
06-12 14:06:44.883 2793-2793/? D/WifiTrafficPoller: notifyOnDataActivity() - mBusMaxLock.acquire()
06-12 14:06:44.907 4137-4348/? I/vgd: 45-xlb -- metadata{ service_id: 0 }
06-12 14:06:44.941 4137-5190/? I/vgd: 45-xlb -- metadata{ service_id: 0 }
06-12 14:06:44.943 4137-5944/? I/vgd: 45-xlb -- metadata{ service_id: 0 }
06-12 14:06:44.999 2793-3595/? D/AudioService: getStreamVolume 3 index 20
06-12 14:06:45.003 2793-3593/? D/AudioService: getStreamVolume 3 index 20
06-12 14:06:45.007 19315-19315/? I/Ads: Ad finished loading.
06-12 14:06:45.009 19315-19315/? I/Ads: Scheduling ad refresh 30000 milliseconds from now.
06-12 14:06:45.021 2793-3513/? E/Watchdog: !@Sync 160 [2018-06-12 14:06:45.021]
06-12 14:06:45.036 19315-19315/? I/Ads: Ad finished loading.

[mobileadssdk-a...@google.com]

Hi,

I'm afraid we can't provide any sample Ad Unit Ids that is mediated with InMobi. However, you can experiment with this modified sample app that I'm using to test your Banner Ad Unit Ids.

The ads that I was able to load successfully earlier on my end are not from InMobi. Also, based from the logs you provided, particularly "Instantiating mediation adapter: com.google.ads.mediation.inmobi.InMobiAdapter", this suggests that the mediation setup for InMobi is working correctly.

Given all our findings, this seems to be more Ad serving related rather than anything specific with your implementation of the Mobile Ads SDK. For further questions about serving from your mediated networks (e.g. InMobi), it's best to reach out to the Product Support Team for this.

As for the log thrown "D/InMobiBanner: Ad request successful but no ad served.", this seems to be thrown on the InMobi side so I suggest that you confirm this log from their team directly.

[mg]

i removed inmobi and will not use it anymore. . their support is non responsive. obviously they dont have inventory for europe demographics but fail to say so

[mg]

thank you very much for help.

On Wed, Jun 13, 2018 at 10:04 AM, mg <bosn...@gmail.com> wrote:

i removed inmobi and will not use it anymore. . their support is non responsive. obviously they dont have inventory for europe demographics but fail to say so

[mike docey]

Also, just to share some experiences with inmobi. I've sent 10 000 requests got 1 impression!

On Wednesday, June 13, 2018 at 10:04:57 AM UTC+2, mike docey wrote:

i removed inmobi and will not use it anymore. . their support is non responsive. obviously they dont have inventory for europe demographics but fail to say so