Violation of Inappropriate Ads policy

[sergio....@gmail.com]

Dear Mobile Ads SDK Team,

I am trying to make my app comply with the GDPR law.

Currently, my application has no age restrictions.

In order not to bother the user with various dialogs, I have simplified the algorithm to the following:

1) if the user is not from the EU - then personalized advertising (as before) must be shown;

2) if the user is from the EU - non-personalized advertising must be shown, plus the age mark (3+) will be added.

Thus, the law is observed. Children from the EU will not see any inappropriate advertising, and for children from other countries the internal AdMob filter will work, therefore, they will not see any inappropriate advertising as well.

Here is the code:

private AdRequest getRequestAdMob(boolean isLocationInEea) {
        AdRequest.Builder builder = new AdRequest.Builder();
        if (isLocationInEea) {
            Bundle extras = new Bundle();
            extras.putString("npa", "1");
            extras.putString("max_ad_content_rating", "G");
            builder.addNetworkExtrasBundle(AdMobAdapter.class, extras);
        }
        return builder.build();
}

The project uses the following dependencies:

implementation 'com.google.android.ads.consent:consent-library:1.0.6'
implementation "com.google.firebase:firebase-ads:15.0.1"

But when I try to publish the app which uses this code, I get blocked by GooglePlay, due to the following:

Thanks for reaching out to the Google Play team.
Thanks for submitting **** to Google Play. After review, your app has been rejected due to a policy violation. If you submitted an update, the previous version of your app is still available on Google Play.
Issue: Violation of Inappropriate Ads policy
The ads shown within your app must be appropriate for the intended audience of your app, even if the content by itself is otherwise compliant with our policies. For example, ads that show mature content or services cannot be served in apps that have a content rating for younger audiences.
Action required: Make sure your ads are set appropriately for the intended audience of your app
Read through the Inappropriate Ads policy, Content Ratings page, and Help Center article for additional details.
Take appropriate steps to ensure that your ads services and ad content filtering are set appropriately for the content rating of your app.
You may need to check with your ad service provider to make sure the advertising campaigns you selected will only show content consistent with your app’s intended audience.
If you use AdMob, please refer to the AdMob Help Center for more details on ad content filtering.
Sign in to your Play Console and submit the update to your app.
If you’ve reviewed the policy and feel our decision may have been in error, please reach out to our policy support team. One of my colleagues will get back to you within 2 business days.
Thanks for your continued support of Google Play.
Best,
The Google Play Review Team

 

Could you comment given situation? Looking forward for your response.

Regards,

Sergio Shevatro

P.S. It is necessary to point out that the following code passes Google Play validation and the application is not blocked.

private AdRequest getRequestAdMob(boolean isLocationInEea) {
        AdRequest.Builder builder = new AdRequest.Builder();
        Bundle extras = new Bundle();
        if (isLocationInEea) {
            extras.putString("npa", "1");
        }
        extras.putString("max_ad_content_rating", "G");
        builder.addNetworkExtrasBundle(AdMobAdapter.class, extras);
        return builder.build();
}

However, if the given code is used, then the advertising content will be reduced and in 80% of cases the following will be received code 3, which corresponds to the fact that there was no suitable advertising for this particular user. As a consequence, providing 100% G rating advertising using, the general income is being reduced.

[mobileadssdk-a...@google.com]

Hi Sergio,

Thank you for providing your code snippets and other helpful details.

Given that you provided 2 versions of your code implementation for your getRequestAdMob() method, could you confirm if the first implementation is the one that you've uploaded in the PlayStore? I'm asking because the first implementation suggests that you will only send an Ad Request with "G" Ad Content label if the location of the user is in EU area. However, given that this is more of a policy related concern, it's best that you raise this to the AdMob Help forum or reach out to the Product Support Team as these are the appropriate channels for your concern.

On the other hand, as for the Error Code: 3 or No fill error you encountered, this could mean that there are just no available ads at the moment for your Ad request. In general, please note that adding targeting details to your Ad request such as Ad content filtering could have an impact on your fill rate and either of the 2 versions of your code implementation for your getRequestAdMob() could encounter the No fill error which could be tagged as expected behavior. Additionally, if you have any concerns about the performance of your Ad Units, you may use this troubleshooter for further assistance.

Regards,

Ivan Bautista

Mobile Ads SDK Team

[sergio....@gmail.com]

Hi Ivan,

Thanks for your reply.

I confirm that. When I tried to download the app with the 1st version of the code, I have got a block while updating the app from PlayStore.

With the code changed to the 2nd version, the lock was canceled.

Thanks for the links. I will try to get help there. Because I still think that the 1st version of the code does not violate AdMob rules.

Regards,

Sergio Shevatro

понедельник, 9 июля 2018 г., 10:07:14 UTC+3 пользователь mobileadssdk-a...@google.com написал:

[mobileadssdk-a...@google.com]

Hi there,

I deleted your attached screenshots that are showing your Ad Unit Id as this is considered as confidential information. Please avoid posting your Ad Unit Ids in the public forums.

Assuming that your Principal class is a subclass of Activity, then your code implementation should work as expected since they are almost the same as our Banner and Interstitial sample implementation. That said, could you create a new thread and specify what exactly are you having issues with?

In addition, you may try to play around with our sample apps to test your Ad Unit Ids or see how it is implemented in an Android app.

Regards,
Ivan Bautista

Mobile Ads SDK Team

On 10/24/18 06:31:14 andres...@gmail.com wrote:

help me please understand what I should do but I do not know where to put the code I am new to this and could you help me with the complete code of the app to see how it would be? Here I leave a screen capture of how I have my code and I want to know how I should modify it I hope your answer friend

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/e1dda4d9-6ce8-45c1-8265-debe6565cff3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.