Did i miss a step to implement admob with gdpr?

[ihafizhuddin]

My apps recently have warning from google playstore.

"We've determined that your app, or the SDK within your app, allows children or users of unknown age to send device identifiers. This violates Google Play's Families Policy."

We already updated admob version to version 22.5 and we add ump sdk version 2.1.0 on app build.gradle

implementation 'com.google.android.gms:play-services-ads:22.5.0'
implementation 'com.google.android.ump:user-messaging-platform:2.1.0'

because my apps is targeted for children, we set up UMP SDK with tag under age of consent true

params = new ConsentRequestParameters
.Builder()
.setTagForUnderAgeOfConsent(true)
.build();

my admob implementation also do the same.

requestConfiguration = MobileAds.getRequestConfiguration()
.toBuilder()
.setTagForChildDirectedTreatment(
RequestConfiguration.TAG_FOR_CHILD_DIRECTED_TREATMENT_TRUE)
.setPublisherPrivacyPersonalizationState(RequestConfiguration.PublisherPrivacyPersonalizationState.DISABLED)
.setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE)
.setMaxAdContentRating(RequestConfiguration.MAX_AD_CONTENT_RATING_G)

        .build();

MobileAds.setRequestConfiguration(requestConfiguration);
MobileAds.initialize(this, new OnInitializationCompleteListener() {
@Override
public void onInitializationComplete(InitializationStatus initializationStatus) {}});

But my update still rejected by google with the same warning.

Did i miss steps on my implementation?

[dersekranda]

Hello. I'm having the same problem. Even though I asked many times, I could not get a sufficient answer. If you solve the problem, could you share it with me?

1 Kasım 2023 Çarşamba tarihinde saat 12:29:20 UTC+3 itibarıyla ihafizhuddin şunları yazdı:

[Mobile Ads SDK Forum Advisor]

Hi Ihafizhuddin,

Thank you for contacting the Mobile Ads SDK Support team.

Upon reviewing your concern, I understand that your concern is related to the UMP consent. Kindly share the below information to investigate further.

• Mobile Ads SDK Version
• App ID and Ad Unit ID
• Sample app

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:

1. Navigate to

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=5004Q00002q9dRnQAI&entry.80707362=00208525

2. Fill out all fields, and attach your file(s).

3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

 

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

Thanks,
 

Mobile Ads SDK Team

[ihafizhuddin]

I found the source of the problem. My Apps was created using Cocos 2D and using  SDK Box. The SDK Box transmiting the data. The solution i found is deleting the sdkbox library and api on apps. 

[dersekranda]

params = new ConsentRequestParameters
.Builder()
.setTagForUnderAgeOfConsent(true)
.build();

@ihafizhuddin hello. When you publish as above, does the GDPR form appear on the screen?
If I set it as above, that is, if I set it to true, the form will not appear.

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

Upon reviewing your concern, I understand that your concern is related to the GDPR form. As per the document set tag for under age of consent false means users are not under age of consent.

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

[Mobile Ads SDK Forum Advisor]

Hi, 

Thank you for contacting the Mobile Ads SDK support team.

I see that you have already raised this concern on another thread with the subject 'Did i miss a step to implement admob with gdpr?', and we have already responded there for this issue.

To avoid multiple threads on the same issue, please take a look at that thread and continue the discussion on the same for further updates on the issue.
 

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

Thanks,
 

Mobile Ads SDK Team