configure GADRequest to receive only non-personalized ads

101 views
Skip to first unread message

Senaika

unread,
May 30, 2023, 10:12:56 AM5/30/23
to Google Mobile Ads SDK Developers
Hi,

I have read in this forum that there is a way to configure an GADRequest object to specify that only non-personalized ads should be requested when using Admob on iOS. This scenario happens when a user has consented to receive non-personalized ads after the ATT message prompt from Apple.

How do you configure an GADRequest object to specify that only non-personalized ads should be requested ?

I appreciate any help here.

Kind regards,

Mobile Ads SDK Forum Advisor

unread,
Jun 1, 2023, 5:41:36 PM6/1/23
to alex.r...@gmail.com, google-adm...@googlegroups.com

Hi,

Thank you for reaching out to us.

With regard to your concern, if you're using UMP, then the serving of personalized ads and non-personalized ads will depend on the consent status (https://developers.google.com/admob/ios/privacy/api/reference/Enums/UMPConsentStatus) that the user will choose. Also, Google restricts how it uses certain unique identifiers and other data processed in the provision of services to publishers. As a result, Google will only show non-personalized ads. These parameters override the RDP settings in the UI.

In addition to that, you should request an update of the user's consent information at every app launch, using requestConsentInfoUpdateWithParameters:completionHandler: before loading a form. This can determine whether or not your user needs to provide consent if they hadn't done so already or if their consent has expired.

This message is in relation to case "ref:_00D1U1174p._5004Q2lueHU:ref"

Thanks,
 
Google Logo Mobile Ads SDK Team


Senaika

unread,
Jun 1, 2023, 6:25:00 PM6/1/23
to Google Mobile Ads SDK Developers
Hi,

Thank you for your answer. I'm starting to better understand the purpose of this UMP sdk.

I do have a last question regarding the integration of it in iOS. Let's assume the following scenario, a user installing an app with Google Ads on an iPhone:
1. User install app first time. UMP is shown. User click ok. ATT is shown, user refuses to receive personalized ads. (Thus the IDFA value is a bunch of 0000)
2. A few days pass, user change his mind. User go to the settings of his iPhone (the default pre-installed settings icon), select the new app, and change the option to receive personalized ads for the app (Allow tracking option set to YES). Which means, that on the next app launch, the IDFA will have a value instead of a bunch of 0000.

What happens with the UMP ? Does it do anything ?
How does Google Ads get informed of this change ?

Thank you, I appreciate your help.

Mobile Ads SDK Forum Advisor

unread,
Jun 6, 2023, 3:56:10 AM6/6/23
to alex.r...@gmail.com, google-adm...@googlegroups.com
Hello Senaika,

To answer your inquiries:

  • What happens with the UMP? Does it do anything?
    • Since the IDFA value has changed, the UMP SDK will assume that the user has agreed to show personalized ads. As our documents states: Before displaying a form, you first need to determine if one is available. Unavailable forms can be due to the user enabling limited ad tracking or if you’ve tagged them as under the age of consent. This means UMP SDK checks these values on app launch to see whether or not the user has agreed or disagreed to show personalized ads and whether or not to show the form.
    • More information here: https://developers.google.com/admob/ios/privacy#load-form.
  • How does Google Ads get informed of this change?
    • ​​​​​​​The UMP SDK gets this information based on the availability of a form, use the formStatus property on the UMPConsentInformation instance you created earlier. This occurs on app launch: you should request an update of the user's consent information at every app launch, using requestConsentInfoUpdateWithParameters:completionHandler: before loading a form. This can determine whether or not your user needs to provide consent if they hadn't done so already or if their consent has expired. 

Ammar Atassi

unread,
Jun 7, 2023, 8:30:51 AM6/7/23
to Google Mobile Ads SDK Developers
Help me you
Thank you 

Senaika

unread,
Jun 12, 2023, 6:13:15 AM6/12/23
to Google Mobile Ads SDK Developers
Hello Google,

Just to be sure. I have been told in this thread (https://groups.google.com/g/google-admob-ads-sdk/c/u8gUhgqxH4A/m/eT2oBz8SAAAJ?utm_medium=email&utm_source=footer) that the UMP SDK is not mandatory.
In regards to my question "How does Google Ads get informed of this change?", I am now confused with your last answer. From my understanding, when requesting admob banner in iOS app, the IDFA is submitted, and this is how Google Ads SDK knows about the consent to show targeted ads (IDFA either has a value, either has 0000 for no consent to show targeted ads).

Kind regards,
Senaika

Mobile Ads SDK Forum Advisor

unread,
Jun 13, 2023, 2:09:23 AM6/13/23
to ammarat...@gmail.com, google-adm...@googlegroups.com
Hello Ammar,


Thank you for reaching out to us.

Do you have any inquiries or concerns regarding Mobile Ads SDK implementation? If so, feel free to share with us and we’d be happy to assist.

Mobile Ads SDK Forum Advisor

unread,
Jun 13, 2023, 2:30:10 AM6/13/23
to alex.r...@gmail.com, google-adm...@googlegroups.com
Hello Senaika,

For clarification, the UMP SDK can handle Apple's App Tracking Transparency (ATT) requirements if you've created, configured, and published your IDFA explainer message in the AdMob UI. However, the IDFA value is already being tracked by the Mobile Ads SDK without the need the for the UMP SDK. Hence, the UMP SDK is not mandatory.

You can read more about IDFA support in this document: https://developers.google.com/admob/ios/privacy/idfa.

Senaika

unread,
Jun 15, 2023, 4:18:21 AM6/15/23
to Google Mobile Ads SDK Developers
Thank you for your help. I really appreciate. I will soon release my app with admob, can't wait to see the result.
Reply all
Reply to author
Forward
0 new messages