Create loop in the message of the GDPR

[Hezi medina]

Hi,

I can to do the next way: until the user confirms, the message will continue to appear.

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for reaching out to us.

To clarify, does your implementation mean that you are going to show the consent message repeatedly until the user agrees to give consent? If not, kindly elaborate further so we could provide appropriate guidance.
 

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

Thanks,
 

Mobile Ads SDK Team

[Hezi medina]

"To clarify, does your implementation mean that you are going to show the consent message repeatedly until the user agrees to give consent?"

Yes, it's what I want to do :)

Have some guide to how I can to do that?

[Tihomir RAdeff]

I don't think this is allowed if even possible...

[Mobile Ads SDK Forum Advisor]

Hi Hezi and Tihomir,

@Tihomir, Thank you for your insight on this. If you have any other concerns related to implementation of Mobile Ads SDK, kindly create a new thread so we can better track it.

@Hezi, If you want to continuously show the consent until the user agrees to give consent, seems to be not a recommended way in implementing your consent as it appears that you're enforcing the user to give consent. As per this article (https://support.google.com/admob/answer/10207733?hl=en&sjid=9029818839945321388-AP) it mentioned that if user doesn't consent, Ads may not serve to users who don’t consent to certain purposes. But, you can check here (https://support.google.com/admob/answer/9760862?ref_topic=10303737&sjid=9029818839945321388-AP) for personalized and non-personalized ads serving.

In addition to that, as per our documentation guide (https://developers.google.com/admob/android/privacy#display-message), you should request an update of the user's consent information at every app launch, using requestConsentInfoUpdate() (https://developers.google.com/admob/ump/android/api/reference/com/google/android/ump/ConsentInformation#public-abstract-void-requestconsentinfoupdate-activity-activity,-consentrequestparameters-consentrequestparameters,-consentinformation.onconsentinfoupdatesuccesslistener-successlistener,-consentinformation.onconsentinfoupdatefailurelistener-failurelistener) 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. 

[Hezi medina]

" If the user's consent does not allow ad serving based the consent settings as mentioned in the previous document, you may limit your app's functionality until the user has consented to the criteria for Personalized or Non-Personalized Ads."

https://groups.google.com/g/google-admob-ads-sdk/c/TbgQsZjtnyQ

This what I want to do but don't understand how?
have some tools, idea, ways, about that?

I want to block the app until the users clicks on the Accept all / Consent 

[James N]

Interesting, I've been in several different threads about this issue. I thought I got it figured out - that I'll show a popup if they don't consent that says that they need to consent to keep the app free, and then reshow the UMP dialog again for them to consent. Although I don't like that flow, there is no better approach that I can think of (without changing the UPM itself to just show 2 options - for them to accept personalized or non-personalized ads). So please clarify Google AdMob Team if my approach is valid - or perhaps show other ways how to approach this.

[Mobile Ads SDK Forum Advisor]

Hi Hezi,

Thank you for your response.

With regards to blocking your app or limiting your app's functionality, this is only possible through your own implementation as there are no tools that would easily incorporate this. The user has to opt in to Purpose 1 (store and/or access information on a device) (where legally required), from this article (https://support.google.com/admanager/answer/9005435?hl=en#:~:text=Although%20non%2Dpersonalized%20ads%20don,to%20combat%20fraud%20and%20abuse.). Although non-personalized ads don’t use cookies or mobile ad identifiers for ad targeting, they do still use cookies or mobile ad identifiers for frequency capping, aggregated ad reporting, and to combat fraud and abuse. Therefore, you must obtain consent to use cookies or mobile ad identifiers for those purposes where legally required, per the ePrivacy Directive in certain EEA countries. See also the documentation on consent for cookies (https://developers.google.com/admob/ios/global-settings#consent_for_cookies_settings) for more information on non-personalized ads vs. limited ads. 

Additionally, the UMP SDK writes the TC String, which is comprised of many bits that can no longer be translated into a single boolean for "personalization". However, you may read the TC String per the spec (https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/TCFv2/IAB%20Tech%20Lab%20-%20CMP%20API%20v2.md#in-app-details) and use that to determine app behavior.