UMP/Funding Choices/GDPR – logic to hide/show Manage Privacy button

[monkey...@gmail.com]

I'm using UMP and Funding Choices for my iOS app. It's all working great except that I don't know how to figure out the logic of whether to show a "Manage Privacy" button in the app. I want this to show up for users who need to manage their GDPR privacy settings. With the old consent implementation this was easy. I just checked to see if the SDK said the user was in the EEA. I don't think I can do this with Funding Choices though, right?

How can I write code that decides whether the app needs to show a Manage Privacy button or not? Does the Funding Choices SDK help with this? I can't find anything like "IsUserInEuropeanUnion" or "IsGDPRRequired." 

I've tried to put something else together based on whether consent is required and a form is available. But now that's causing my "Manage Privacy" button to appear when the user doesn't need to do the GDPR form and is only required to handle App Tracking Transparency. Am I missing something that allows me to differentiate what's required? Sorry in advance if I missed something easy with all of this because every developer working on an app in the EEA needs this functionality and I'm betting I must have overlooked it.

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for reaching out to us. Let me do the best I can to assist you in this.

With regard to your concern, you must determine if the user requires consent prior to presenting the form. To check if consent is required, examine the consentStatus property of the UMPConsentInformation object, which returns an enum of type UMPConsentStatus. As per your use case, it it's an expected behavior that the "Manage Privacy" button to appear when the user doesn't need to do the GDPR form and is only required to handle App Tracking Transparency as ATT consent is part of the form presentation flow.

Regards,

Teejay Wennie Pimentel Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2VOwMG:ref

[Sniderware]

Thanks for your patience and help. Sorry for the super long description – I can't tell if you understand the problem that I have. I don't understand what you're saying here:

"As per your use case, it it's an expected behavior that the "Manage Privacy" button to appear when the user doesn't need to do the GDPR form and is only required to handle App Tracking Transparency as ATT consent is part of the form presentation flow."

I want to implement privacy consent, especially for GDPR, (and CCPA) correctly, and I'm using UMP/Funding Choices. I need to offer a way for users to withdraw or change their consent because it's required by GDPR. The GDPR says that it must be as easy to withdraw consent as it is to give consent.

https://developers.google.com/admob/ump/ios/quick-start#load_a_form_if_available

The UMP iOS documentation says this:

"It is a best practice to load a form every time the user launches your app, even if you determine consent is not required, so that the form is ready to display in case the user wishes to change their consent setting." 

My iOS code works with UMP privacy consent. At launch it checks to see if a form is required and shows it. It also loads a new form afterwards in case the user ever "wishes to change their consent setting."

Once a form is loaded, is there any way to determine what kind of form it is? If the code could determine if the loaded form is for GDPR then it could show a "Manage GDPR Consent" button. Here's the problem: The reason this matters is because if the loaded form is ONLY for ATT (like for a user in Canada) then I don't want to show the form because Apple only allows their ATT alert to be shown once. I don't want to confuse non-GDPR users with a button that mostly does nothing. If a user has already completed the UMP ATT dialog the UMP SDK still allows developers to load a form that has the same message for ATT again. If an app shows that form it has a button that says "Continue," but if the user already saw the iOS ATT alert then nothing happens. Is this what other developers do?

Is there a UMP iOS sample app that shows how to let users change their consent setting and only shows the option to the right users? Or is this ATT form just something that I need to accept - that it will be a strange experience for users who have already seen the ATT alert? I guess this seems so weird to me that if this is how we developers should implement it that it would be explained in the documentation.

Thanks,

Eric

[Mobile Ads SDK Forum Advisor]

Hi Sniderware,

Thank you for providing a detailed information of your use case.

Let me bring this to the rest of the team to as further with regard to your concern. Rest assured that one of our team will reach out to you soon.

Regards,

Princess Pamela Pineda Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2VOwMG:ref

[Mobile Ads SDK Forum Advisor]

Hi monkeyvrobot,

If a publisher chooses to implement both the GDPR message and the IDFA message, Funding Choices will ensure that the messages are orchestrated properly.

If the user is in Canada GDPR does not apply. So when the app developer calls Funding Choices via the UMP SDK we will check to see if the IDFA explainer has been shown (and a decision made) before showing it. If the explainer has already been shown, it will not be shown as you have noted.

If the user is in a GDPR impacted country, when the user calls Funding Choices via the UMP SDK, we will look to see if the GDPR message has been shown. If it has not been shown, we will serve the message and follow it with the ATT alert (assuming that the user is on an iOS 14+ device and no ATT decision made).

Please see this help center article under the section "what will my user see" for more information

Cheers,

Nick

ref:_00D1U1174p._5004Q2VOwMG:ref