AdMob Native Ads never loaded

[appetizermonster]

AppLovin SDK version: 11.1.2 Facebook Adapter version: 6.8.0.9 AdMob Adapter version: 20.5.0.8

I first tried enabling the test mode to test native ads of mediated networks by using the Mediation Debugger. I confirmed that the Facebook adapter works with the debugger but the AdMob adapter doesn't work with the following log message: Ad network does not match filter ad networks list

So I tried to set AdMob CPM to $99 to make it have the highest priority in the AppLovin dashboard. but no requests are made on the AdMob SDK side. (Test mode is disabled)

Any hint for resolving the issue?

[chauduyphanvu]

@appetizermonster, do you see anything strange in your log (feel free to share it here and we can help check it out too)? If no requests are made to AdMob then it's possible there was no bid or the adapter drops the ad request due to an invalid configuration.

Vu Chau AppLovin Team

[appetizermonster]

Here's the full log: https://gist.github.com/appetizermonster/755029e712eee65b47cd9a545adb042b

I couldn't find any strange things from the logs. 😢 I'll be appreciated it if you look at the logs.

And one small thing I found is that GoogleMediationAdapter methods are never called. Only the constructor is called. Thanks!

[chauduyphanvu]

@appetizermonster, I checked out your ad unit ID and was able to get ad responses from our ad server to trigger the Google adapter. However, outgoing ad requests to AdMob failed because of the error No ad config:

2022-02-16 16:01:57.435 32044-32044/ I/AppLovinSdk: [GoogleMediationAdapter] Native ad (ca-app-pub-4798176420450252/6944501543) failed to load with error: MaxAdapterError{errorCode=204, errorMessage="No Fill", thirdPartySdkErrorCode=3, thirdPartySdkErrorMessage="No ad config."}
2022-02-16 16:01:57.436 32044-32044/ W/AppLovinSdk: [MediationAdapterWrapper] GoogleMediationAdapter: native ad ad failed to load with error: MaxAdapterError{errorCode=204, errorMessage="No Fill", thirdPartySdkErrorCode=3, thirdPartySdkErrorMessage="No ad config."}
2022-02-16 16:01:57.436 32044-558/ I/Ads: Ad failed to load : 3
2022-02-16 16:01:57.437 32044-32044/ I/AppLovinSdk: [MediationService] Destroying MediatedAd{thirdPartyAdPlacementId=ca-app-pub-4798176420450252/6944501543, adUnitId=e0f5c618e770a1c2, format=NATIVE, networkName='Google AdMob'}
2022-02-16 16:01:57.437 32044-32044/ D/AppLovinSdk: [MediationAdapterWrapper] GoogleMediationAdapter: running destroy...
2022-02-16 16:01:57.437 32044-32044/ I/AppLovinSdk: [MediationAdapterWrapper] Marking GoogleMediationAdapter as disabled due to: destroy
2022-02-16 16:01:57.437 32044-32044/ I/AppLovinSdk: [GoogleMediationAdapter] Destroy called for adapter com.applovin.mediation.adapters.GoogleMediationAdapter@8300338
2022-02-16 16:01:57.437 32044-32044/ D/AppLovinSdk: [MediationAdapterWrapper] GoogleMediationAdapter: finished destroy

This seems to be due to the waterfall/account setup on your AdMob dashboard. You can check out the AdMob Help Center for additional troubleshooting tips: https://support.google.com/admob/search?q=%22No+ad+config%22.

[appetizermonster]

@chauduyphanvu Thanks for the quick response.

I've succeeded in getting ad responses from AdMob without any changes in code. All I did was that adding an additional banner ad unit that has the AdMob waterfall setup, in the AppLovin dashboard. and just switched the native ad template setting back and forth in the dashboard.

And I guess that the error message you attached is caused by the app-ads.txt protection. (I saw the error coming from an app of Lion Studios in my AdMob dashboard today.) So I think that my settings on the AdMob have no problem.

IMHO, It would be possible that there is an issue on the AppLovin backend for some functions such as propagating waterfall settings.

[chauduyphanvu]

Sounds good! Let us know if you need anything else.