App Rejected for Advertising ID - Google Play (FAMILY PROGRAM'S APP)

There are a lot of problems with children's apps, very strict rules.

If you're an independent developer, it's better not to go there, this audience is very hard to monetize and has very low retention. Without recognizable brands, you have nothing to do there.

You need to familiarize yourself with google requirements for such apps, fix everything and post an update.

If you have only Admob and no analytics you need to disable user data collection, disable personalized ads. Set a restriction on advertising content by age and re-fill the google user data.

You need every trace of tracking in projects in the Google Play's Design Apps for Families Programs removed, also you need a plugin like this to remove those listed identifiers: constructcollection.com/documentations/mobile/mobile-advert-families-programs

I use Admob and understand that the advertising ID maybe depends on the required DGPR settings. What should I do?

You do not need the GDPR requirements you are thinking of for Google Play's Designed for Families Programs, specifically the Advertising Id. Furthermore, if you are using the Mobile Advert object, it's automatically incompliant because the consent dialog is hardcoded.

I'm not sure if you can get away using the Mobile Advert as long as you do not launch the consent dialog. Although, considering it is Google, I wouldn't risk it. In spite of that, you still need a plugin to remove those ids specified, like this plugin does: constructcollection.com/documentations/mobile/mobile-advert-families-programs

> > I use Admob and understand that the advertising ID maybe depends on the required DGPR settings. What should I do?

>

> You do not need the GDPR requirements you are thinking of for Google Play's Designed for Families Programs, specifically the Advertising Id. Furthermore, if you are using the Mobile Advert object, it's automatically incompliant because the consent dialog is hardcoded.

>

> I'm not sure if you can get away using the Mobile Advert as long as you do not launch the consent dialog. Although, considering it is Google, I wouldn't risk it. In spite of that, you still need a plugin to remove those ids specified, like this plugin does: constructcollection.com/documentations/mobile/mobile-advert-families-programs

Ohh, okay.. and what do you think about these actions? Perhaps they can help?

Those are only for COPPA, which are one of the requisites.

> > > I use Admob and understand that the advertising ID maybe depends on the required DGPR settings. What should I do?

> >

> > You do not need the GDPR requirements you are thinking of for Google Play's Designed for Families Programs, specifically the Advertising Id. Furthermore, if you are using the Mobile Advert object, it's automatically incompliant because the consent dialog is hardcoded.

> >

> > I'm not sure if you can get away using the Mobile Advert as long as you do not launch the consent dialog. Although, considering it is Google, I wouldn't risk it. In spite of that, you still need a plugin to remove those ids specified, like this plugin does: constructcollection.com/documentations/mobile/mobile-advert-families-programs

>

> Ohh, okay.. and what do you think about these actions? Perhaps they can help?

>

>

Those are only for COPPA, which are one of the requisites.

Yes, but judging by this window we can treat all users as children. It also mentions the GDPR window, which is why there is a problem, because when it wasn’t there, everything was fine. The window requires mandatory data collection.

Can you understand this? Google has introduced a mandatory requirement to illuminate the window, but it is prohibited for children. Haha, sur.

They themselves cannot understand their decisions, it’s the same network, like Admob, like Google, they shouldn’t have problems. I can't remove the GDPR window because it's mandatory. Why should I bypass some strange methods and new plugins and write something in the manifest... Hide something.. Is it really not possible to just track whether it is a child or not, and show a window depending on the age.. Maybe there is an action "Tag for under age of consent" is exactly it.

I apologize for so much text, but I want to figure it out once and for all. I removed children from the app and lost most of my audience. I won't be able to continue to receive such a stable income, and develop an update... It's a nightmare.

It would also be a good idea for the Construct developers to look at this whole situation, because as you write, they “dialog is hardcoded”... I am surprised by the silence of many, because this is clearly a problem.

> > > > I use Admob and understand that the advertising ID maybe depends on the required DGPR settings. What should I do?

> > >

> > > You do not need the GDPR requirements you are thinking of for Google Play's Designed for Families Programs, specifically the Advertising Id. Furthermore, if you are using the Mobile Advert object, it's automatically incompliant because the consent dialog is hardcoded.

> > >

> > > I'm not sure if you can get away using the Mobile Advert as long as you do not launch the consent dialog. Although, considering it is Google, I wouldn't risk it. In spite of that, you still need a plugin to remove those ids specified, like this plugin does: constructcollection.com/documentations/mobile/mobile-advert-families-programs

> >

> > Ohh, okay.. and what do you think about these actions? Perhaps they can help?

> >

> >

>

> Those are only for COPPA, which are one of the requisites.

Yes, but judging by this window we can treat all users as children. It also mentions the GDPR window, which is why there is a problem, because when it wasn’t there, everything was fine. The window requires mandatory data collection.

Can you understand this? Google has introduced a mandatory requirement to illuminate the window, but it is prohibited for children. Haha, sur.

They themselves cannot understand their decisions, it’s the same network, like Admob, like Google, they shouldn’t have problems. I can't remove the GDPR window because it's mandatory. Why should I bypass some strange methods and new plugins and write something in the manifest... Hide something.. Is it really not possible to just track whether it is a child or not, and show a window depending on the age.. Maybe there is an action "Tag for under age of consent" is exactly it.

I apologize for so much text, but I want to figure it out once and for all. I removed children from the app and lost most of my audience. I won't be able to continue to receive such a stable income, and develop an update... It's a nightmare.

It would also be a good idea for the Construct developers to look at this whole situation, because as you write, they “dialog is hardcoded”... I am surprised by the silence of many, because this is clearly a problem.

If you are trying to vent, I understand. But, if you are asking me what's the issue, then to elucidate what's happening based on your provided Google rejection response:

1. It's not an issue with your event sheet.
2. Rather, it's an issue with your SDK integration and Android Manifest.
3. You shouldn't have anything in your project that identifies your users since it's targeted only for children.
4. In your case, your project's build integration.
5. Assuming you only have the Mobile Advert plugin, you need to remove those identifiers.
6. No, you do not need a consent dialog. Quite the opposite actually, it's preferably removed, if not required.
7. Strictly remove the AD_ID permission.

When writing for this compliance for my own projects and plugin collections (a quick solution). I used this as my guide: support.google.com/googleplay/android-developer/answer/9893335

Chadori

Today I purchased your $30 monetization collection https://chadori.itch.io/monetization-collection. I purchased the entire bundle just for the MobileAdvertFamiliesPrograms plugin to obtain compliance on my google play game.

I am unable to get construct 3 to compile any APK. I am using the latest stable release. I get the following error:

I sent you a few emails earlier this week and last to see if you would sell the plugin separately, but I was unable to contact you. Now that I have purchased the package and need your help, I thought I would see if I can reach you here.

Thanks for your time.

Hi haypers, this happens when the Mobile Advert Families Programs plugin is added last in the Construct 3 project. I requested a feature to fix this with the Construct 3 Build Service, but just like most of my requests for mobile to support SDK integrations, this was unprioritized by the Construct Team as well.

For the fix, you can use the public issue with the Mobile Cloud Save plugin.

1. Fix using the Construct 3 editor.
2. Fix using the text editor (reliable fix).

If this happens, you only have to do this once in your project.

Basically, the goal is to put the Mobile Advert Families Programs plugin at the top of the objects list of the Construct 3 project.

The plugins that need this fix in the collection when this bug occurs are the following:

1. Mobile Cloud Save
2. Mobile Advert Families Programs

I'll try to bring this issue up again with the Construct Team. Unfortunately, this is the only way to support the listed plugin features while still following the Construct 3 Build Service guidelines while also supporting the built-in Mobile Advert object. There is another workaround, but it takes more time through a plugin than for the Construct 3 engine to just support it itself.

We should have references about this in the Discord Community as well.

I hope that helps.