UMP Android SDK app or site consent for own purpose

[zhang yujie]

Hi Google Mobile Ads SDK support team,
We are app developer and we want to implement Android UMP SDK to ask consents from app users for using user's data as own purpose. So we selected the corresponding purpose in the Add purposes for your own use section of GDPR settings in Google ad manager console.
To tell the consent status of above situation, we found 2 keys looks very similar and confusing, IABTCF_PublisherConsent and iABTCF_PurposeConsents, so could you pls help to confirm which key should we use as own use purpose consent?

Looking forward to your reply!

Thanks a lot.

[zhang yujie]

Hi,

As you can see in the first screenshot, I only selected first purpose in the Add purposes for your own use section of GDPR settings in Google ad manager console. Is this case we app developer as publisher should use IABTCF_PublisherConsent, correct? This is what we observed in the debugging process, when enable or disable the triggler in Site or App section of ump popup, IABTCF_PublisherConsent is changing accordingly instead of iABTCF_PurposeConsents.

On Friday, December 1, 2023 at 5:06:01 PM UTC+8 Mobile Ads SDK Forum Advisor wrote:

Hi, 

Thank you for contacting the Mobile Ads SDK support team.

Upon reviewing your concern, I understand that you would like to implement the Android UMP SDK to request consent from app users for using their data for your own purposes.

The key to use for determining the consent status of your own use purpose consent is iABTCF_PurposeConsents.

• IABTCF_PublisherConsent is used to store the consent status for the publisher's use of data.
• iABTCF_PurposeConsents is used to store the consent status for each individual purpose for which you have requested consent.

If you have requested consent for multiple purposes, you will need to use the iABTCF_PurposeConsents object to track the consent status for each purpose.

Kindly refer to this About GDPR messages and Request consent for your own use of data  documents for more information.

Please reach out to us, if you need any further assistance. 

This message is in relation to case "ref:!00D1U01174p.!5004Q02qVaKx:ref"

Thanks,
 

Mobile Ads SDK Team

 

[Mobile Ads SDK Forum Advisor]

Hi zhang yujie,

Thank you for contacting the Mobile Ads SDK support team.

I will check with our team regarding your query and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for your inquiry. Please consult the IAB spec for more specific information related to the keys and values. See also How to read consent choices for how to extract this information in practice. 

Thanks,
Justin

ref:!00D1U01174p.!5004Q02qVaKx:ref

[zhang yujie]

Hi,

The IAB spec didn't tell us what's the different use for IABTCF_PublisherConsent and iABTCF_PurposeConsents.

What we find is --- when user checked the consents option in  Site or app section and clicked Confirm choices,  iABTCF_PurposeConsents turns out to be 0. Only when user checked the consents option in Vendor section and submit, iABTCF_PurposeConsents will turn out to be 1.

So can you pls confirm in your first reply email, it it a typo to say The key to use for determining the consent status of your own use purpose consent is iABTCF_PurposeConsents. Which should be IABTCF_PublisherConsent actually.

[Mobile Ads SDK Forum Advisor]

Hello,

To answer your original question, the keys to use for determining the consent status of your own use purpose consent are IABTCF_PublisherConsent and IABTCF_PublisherLegitimateInterests. 

[zhang yujie]

Hi, 

Thank you so much for the answer. It helped a lot and we are almost there!

However we faced another issue... It says GDPR requires consent revocation to allow users to withdraw their consent choices at any time. See Privacy options to implement a way for users to withdraw their consent choices. But after the implementation according to https://developers.google.com/ad-manager/mobile-ads-sdk/android/privacy#privacy_options doc, we can not revoke the form successfully in production environment for any single time. Is there any possible reason why it is happening? Please do help and let me know if you need any more details.

Thanks,

Yujie

[Mobile Ads SDK Forum Advisor]

Hello,

Can you elaborate on, "we can not revoke the form successfully in production environment". Are you not able to show the privacy options form? Have you checked the privacyOptionsRequirementStatus API is set to required? Have you checked the error log in showPrivacyOptionsForm?

[zhang yujie]

Hi,

Yes we are not able to show the privacy options form. We can not find any method to set the privacyOptionsRequirementStatus API to required. Can you let me know how to set it in prod environment? If we can not set it manually, when and how will the API returns as required so that we can show the button for users to open the form to withdraw their consent choices? This is really important for us because during debugging we keep getting  privacyOptionsRequirementStatus as NOT_REQUIRED.

Thanks!

Yujie

[Mobile Ads SDK Forum Advisor]

Hi Yujie,

PrivacyOptionsRequirementStatus is a read-only variable. Please take a look at any of our Android samples to see how use the privacy options in practice. If the API is returning NOT_REQUIRED that is acceptable; this means you are calling requestConsentInfoUpdate to return the latest consent information before querying that API, which is correct. If you were to simulate your location to the EEA (see the test sample for how to achieve this), you will find the API will return REQUIRED. If it returning NOT_REQUIRED in production, that can mean that you can in a GDPR-regulated region such as the EEA and UK.

[zhang yujie]

Thank you so much for the quick response! In the last is it a typo to say that If it returning NOT_REQUIRED in production, that can mean that you can in a GDPR-regulated region such as the EEA and UK, which should be If it returning NOT_REQUIRED in production, that can mean that you are not in a GDPR-regulated region such as the EEA and UK? 

[Mobile Ads SDK Forum Advisor]

@Yulie,

Yup, that was a typo. Thanks for confirming.

- Justin

ref:!00D1U01174p.!5004Q02qVaKx:ref

[zhang yujie]

Hello, 

We are facing a new issue about UMP SDK. Every time when app is launching, it will call requestConsentinfoUpdate(). But it always take 2-3 seconds for the API to return the status, during the 2-3 seconds app user will have to see the blank screen which is a bad user experience. Basically user will see the splash screen>blank screen>enter app. Could you please suggest how to solve this or any better flow we should apply? Thanks a lot!

[Mobile Ads SDK Forum Advisor]

Hello,

Are you noticing this delay happen every single time? Please be aware loading a consent form makes a request that is inherently dependent on network conditions.

There are multiple ways to indicate that content is loading in mobile apps. One example is to implement ProgressBar. Another example is to add a text field that says "Loading..." or something like that. 

Thanks,

[Nathan McKean]

Did this every translate into updating documentation for Google because I had not even heard of publisherConsents in the UMP documentation until now and this seems to be what I have been looking for. You sure don't make it easy.

[Mobile Ads SDK Forum Advisor]

Hi Nathan,

We link to the TCF spec in our GDPR doc in this section: https://developers.google.com/admob/android/privacy/gdpr#how_to_read_consent_choices
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02qVaKx:ref" (ADR-00213056)

Thanks,
 

Justin Malandruccolo Mobile Ads SDK Team