Trouble with mediation testing

[joao-gb]

Hi, I've recently implemented AdMob mediation on my iOS app which is not live yet and I'm having trouble obtaining ads coming from mediation partners, specifically Facebook.

I've recreated the issue in a small standalone project that I can share if needed. But basically my logic goes like this:

I initialise FBAudienceNetwork.

I set tracking flag to true if user allows it.

I initialise GADMobileAds.

At this point I'm able to check that MetaAdapter was initialised and is ready by using ad inspector, or by logging adapterStatusesByClassName.

I've set up mediation on both admob & Facebook sides by doing this:

I create an ad unit on admob, and I create a mediation group targeting that ad unit.

On this mediation group I select Facebook, and fill up the placement ID with the one I obtain from Facebook.

I'm able to obtain ads from admob, but never from Facebook, always getting Facebook error 1001 — No fill.

I've done several troubleshooting on this, and I'm all out of ideas.

Is it the case that we are only able to obtain ads from mediation in a testing scenario if we use the Mediation Testing Suite? Because I've added my device as a testing device, and on Facebook side I enable the testing ads as well for the duration of the test.

Thanks

[Mobile Ads SDK Forum Advisor]

Hi Joao,

Thank you for reaching out to us. Let me do the best I can to assist you in this.

On AdMob side, publishers may get a no fill error even when requesting an ad with an enabled test device. This is the reason why we highly recommend to use our demo ad units instead to ensure that you will receive an ad on every ad request. As you mentioned that you were able to load test ads from AdMob, then this confirms that you code implementation of the Mobile Ads SDK is fine. As per no fill error while requesting ads on Facebook through mediation, I'm afraid that we cannot comment as the issue might be on the FAN/META side. Please note that the SDK just request an ad to the ad-server (AdMob, Ad Manager, AdX or through Third-party ad network) and does not have any control on match rate / fill rate. On your use case, I would recommend to reach out to Meta via their community page.

Regards,

Teejay Wennie Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2dHkqa:ref

[joao-gb]

Hi Teejay,

Thanks for you answer, just a couple of follow up questions:

When you mention that AdMob highly recommends using the demo ad units, do you mean that I'm able to obtain ads from mediation partners using it or just that it's the best way to test AdMob correct implementation?

Also, I noticed you didn't gave an answer to the MTS (Mediation Test Suite) question I left — I just want to know if using the MTS is required to obtain ads in test mode that are coming from mediation partners. I ask this because I have some colleagues working on an Android version of this app and they were able to obtain ads in this scenario when using the MTS.

I also noticed the MTS is currently in maintenance mode so if it turns out to be the case that I'm only able to get test ads using it, then I'll probably not be able to use it at the moment?

Thanks again,

Joao

[Mobile Ads SDK Forum Advisor]

Hi Joao,

Thank you for your response.

I'm a colleague of Teejay and will be assisting you on this. For your first question, we always recommend to the publisher's to use our ad unit id as this is a correct way of testing your AdMob implementation. This also helps you to avoid invalid traffic since you only use a test ad unit id. For your second question, the use of MTS is not required, but it allows you to test whether you have correctly configured your app and ad units to be able to display ads from third-party networks through mediation. Since you mentioned that MTS is in maintenance mode, you then try to use an Ad inspector. It is an in-app overlay that enables authorized devices to perform real-time analysis of test ad requests directly within a mobile app.

Regards,

Princess Pamela Mobile Ads SDK Team

 

ref:_00D1U1174p._5004Q2dHkqa:ref