Hello Google Mobile Ads SDK team,
I’m facing an issue where Unity Ads are not showingin AdMob mediation, even though Google AdMob ads display successfully. The integration was done correctly using the latest Unity Ads SDK and adapter versions, but only AdMob network ads are served — no Unity ads appear in logs or on-screen.
Platform:Android
Language:Java (Native Android)
AdMob SDK version: 24.7.0
Unity Ads SDK version: 4.16.3
Unity Ads Adapter version: 4.16.3.0
Mediation type:Waterfall (Unity Ads Active, Optimization in progress)
Ad unit type:Rewarded Ad
Device tested: Samsung M01
✅ AdMob adsload and display correctly.❌ Unity Adsnever load or show, despite being active in the mediation waterfall.
Unity Ads logs show the following error:
Verified internet connectivity (ping to configv2.unityads.unity3d.com successful).
Added Unity Ads adapter in AdMob mediation and linked API key + Organization core ID.
Enabled Unity Ads in dashboard and confirmed placement active.
Tested with test mode and production mode.
Cleared cache/data, reinstalled app, re-synced mediation adapters.
Logs show background worker success, but Unity ad requests not received.
Unity Ads should load and show rewarded ads as part of AdMob mediation waterfall along with AdMob network ads.
Only AdMob ads show; Unity Ads never load, and the request fails with host resolution error.
Please help identify if this issue is due to:
Network resolution handling in the Unity Ads adapter or SDK
Any recent change in Unity Ads endpoint configuration
Missing configuration in AdMob mediation setup
Also, please confirm if Unity Ads requires any special permission, API key location, or initialization order when used with the latest AdMob SDK.
Hi,
Thank you for contacting the Mobile Ads SDK Support Team.
Could you please confirm whether you have followed the implementation steps for Unity Ads mediation as described in the following guide?
Unity Ads Mediation Setup
To help us with further investigation, could you please provide the following information:
Kindly provide the requested details via reply to the authoroption.

[2025-11-03 13:49:39Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vST35:ref" (ADR-00338261)
--
---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com .
To view this discussion visit https://groups.google.com/d/msgid/google-admob-ads-sdk/9354ea6d-35d7-4994-8d28-c83e1d455c7fn%40googlegroups.com .
Thank you for getting back to us.
Please note that we didn’t receive the files which you have shared. Could you kindly reshare the files using the link below.
If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files via reply to authoroption or by performing the following steps:
1. Navigate to
2. Fill out all fields, and attach your file(s).
3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

[2025-11-06 13:51:19Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vST35:ref" (ADR-00338261)
I tested the provided sample project on both emulator and physical devices (Motorola and Samsung), and the ads were loaded successfully from both AdMob and Unity Ads mediation.
Could you please confirm if this issue occurs in a specific region? Also, please share the Charles logs via reply to author option? for further investigation.
If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:
1. Navigate to
2. Fill out all fields, and attach your file(s).
3. Please reply back to this thread when you have uploaded your file(s). Please do not share this link.

[2025-11-07 11:02:40Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vST35:ref" (ADR-00338261)
Hi,
Thank you for getting back to us.
Upon executing the sample project you provided, I was unable to successfully load Unity Ads, and I noted that the Unity Ads Mediation Adapter failed to initialize. Additionally, I observed that the app ID currently employed in the Manifest.Xml file is ca-app-pub-3940256099942544~3347511713 which is a known AdMob Test ID. However, the app ID associated with the ad unit ID ca-app-pub-78377xxxxxx037/88xxxx39 is ca-app-pub-7837xxxxx6037~590xxxx79.
Could you please clarify the reason for utilizing the test app ID instead of your proprietary app ID? I recommend attempting the execution once more using your correct app ID and confirming the resulting outcome?
Additionally, I also observed that you are using the oldest version of Unity Ads Mediation Adapter 4.12.3.0.
It is always recommended to use the latest version of the SDKs to avoid any issues. As of today the latest version of the Unity Ads Mediation Adapter is 4.16.3.0.

[2025-11-07 14:42:22Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vST35:ref" (ADR-00338261)