Hi Gavin Guo,
Thank you for contacting the Mobile Ads SDK Support team.
I'm deleting the previous thread from the forum as it consists of PII information.
Regarding your concern about being unable to enter the Mobile application value for the ad unit ID (banner_320*50_google), I have investigated your Ad Manager account with the provided information. I observed that the ad unit ID (banner_320*50_google) is currently mapped to SDK Bidding, and the Mobile application value within SDK Bidding is set to “Google Play Games”. Kindly verify this in your AdManager account.
To add a new ad unit ID mapping for SDK Bidding, Kindly follow the steps mentioned in the help center article “Ad unit mapping for SDK Bidding”.
Remember that Ad Inspector displays all configured ad units and their basic fill status. To verify each ad unit, please follow the instructions in "Enable Secure Signals and verify signals are being shared correctly", this explains why you see interstitial placements and the InMobi SDK in Ad Inspector, even if you haven't added these bidders.
Upon checking your AdMob account, I observed that the ad unit IDs are not yet mapped. You can edit existing ad unit mapping details or add new mappings on the Ad source page of your account. Kindly refer to the Manage your ad unit mapping details help center article for step-by-step instructions.
I hope this helps! Let me know if you have any other questions.
![]() |
Mobile Ads SDK Team |
2) Following the instructions in "Enable Secure Signals and verify signals are being shared correctly", I found it odd that I have never added interstitial placements and the InMobi SDK in AdManager.
=> There is NO such interstitial ad unit mapping in my GAM ad units (and its name looks more like AdMob ad unit than a GAM one. And in Secure Signals, InMobi SDK is OFF.
=> It seems to be app-level related:
I tried another ad unit ID banner-lbddk > banner-lbddk-child, specifying a previous defined app name lbddk-test(not applicable).
The Ad Inspector shows a different adapter setting: GADMediationAdapterPangle (not initialized), seems to be an outdated Pangle adapter?
So how can I add and map a new ad unit ID, with an unpublished test app defined in Ad Manager?
3) Upon checking my AdMob account, you observed that the ad unit IDs are not yet mapped.
=> I am currently performing all the steps here: https://developers.google.com/ad-manager/mobile-ads-sdk/android/mediation/pangle
And my Ad Inspector said that my defined banner unit got no fills, although it does have its full "Third-party bidding parameter > Buyer generated data".
Be aware, I am NOT using AdMob, I am using Google Ad Manager only here. I do not understand why you checked my AdMob account, since ad unit mapping in AdMob is not even mentioned in the above link.
BTW, my Ad Manager Network code is 176126332.
Please help me explain the redundant/outdated ad unit and adapters showing up in the ad inspector while I was testing with these two apps Google Play Games & lbddk-test(not applicable)