Hi,
Thank you for reaching out to us.
With regard to your concern, can you further elaborate what do you mean by "rejected by UMP"? Are you referring to when the user doesn't accept the consent? Then to your questions, let us provide our insight below:
1. will installing the Admob Unity plugin 8.3.0 definitely fix this problem?
2. Is there any way to stop this according to the UMP results in Admob Unity plugin 7.4.1?
3. The document states two things, which is correct in version 7.4.1?
1. "When seeking consent, you must identify each ad network in your mediation chain that may collect, receive, or use personal data and provide information Google currently is unable to pass the user's consent choice to such networks automatically."
2. "Add ironSource to GDPR ad partners listFollow the steps in GDPR settings to add ironSource Mobile to the GDPR ad partners list in the AdMob UI."
![]() |
Mobile Ads SDK Team |
Hi Yusuke,
Thank you for your response.
With regard to your concern for the ironSource, it seems that this logs are from the ironSource plugin itself as it has the indication of "[ironSource SDK]" which is not controlled by the Mobile Ads SDK itself. Can you confirm if this affects your app for using the mediation network? If yes, kindly provide us your project file and steps to replicate for us to further investigate. In addition to that, we always recommend to use the latest Unity plugin (https://github.com/googleads/googleads-mobile-unity/releases/tag/v8.3.0) to avoid any errors for your implementation.
Then, with regard to non-personalized ads, if you don't consent to the UMP, then the ads will be served as non-personalized ads. As per this article (https://support.google.com/admob/answer/9760862?hl=en&sjid=2418371235660772237-AP) under the ad serving behavior, if consent is missing for Google for Purpose 1 in the TC string, Google will drop the ad request and no ads will be served. For non-personalized ads, consent for cookies or mobile identifiers is still required because non-personalized ads still use cookies or mobile identifiers to combat fraud and abuse, for frequency capping, and for aggregated ad reporting.
In addition to that, you can create your own consent dialog that displays a message on your sites or apps asking your users in the EEA and the UK for consent. Just kindly make sure that you comply with the EU user consent policy (https://support.google.com/admob/answer/7666519?hl=en&sjid=958286124600267954-AP). For mediation consent, just kindly follow the guide on the following networks (https://developers.google.com/admob/unity/choose-networks) that you're using.
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:
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.