Google Play changes - Permissions for the Segmentation of Android 12.

Solar2D Android
#1

I would like to know about the changes that Google is requesting to carry out by April 2022, in particular asks to update the SDKs to its latest version to be compatible with the application set IDs. In the notice it says:

"On devices with Android 12 or a higher version, the advertising ID will be removed when a user disables the customization with that ID in the Android settings.

For users who reject that customization to prevent fraud and denounce it, Google AdvoB recommends updating the Google ad SDK for mobile phones to a later version that is compatible with application set IDs.

Declare new permissions to use the advertising ID in applications that update your destination API level at 31 (Android 12):

In applications whose destination API level changes to 31 (Android 12), a normal Google Play services permit must be declared in the Android manifest file to use the advertising ID. In applications that do not request that permission and update your destination API level to Android 12, the advertising ID will be removed automatically and a zerose chain will be used instead.
In the applications where the Google Ad SDK is updated for mobile phones to version 20.4.0 or a later, the permission will be automatically declared and the developers will not have to do anything to be able to continue using the advertising ID.

Review the modifications of the Google Play families policy and see if it is necessary to take a measure:

Finally, Google Play announced updates that clarify that, if one of the target audiences of applications are minor, applications may not transmit certain IDs (including advertising ID) of minors or users who have not specified their age.

For applications whose target audience also understands minors, we recommend updating Google Ad SDKs for Android mobiles or iOS to versions 20.6.0 and 7.67.0 (or later) respectively. In this way, when ad requests include content labels aimed at children with the TagForchildDirected (TFCD) or TagforunderageofConSent (TFUA) parameters, the advertising ID can not be transmitted. "

My question is, how is it so SOLAR2D prepared to meet these new policies? For example, version of Admob ad SDK is using?

#2

Like to know this also, just received another email from google outlining the post above today.

#3

Well if you got the same e-mail as I did. Android 12 is no longer in scope and Android 13 is not yet out. So this gives us more time to get this resolved. The original e-mail from Google is no longer valid.

#4

Particularly my apps are child-oriented.
And as I understand by Google Mail, from April 1, children-oriented apps should not transmit Android advertising ID (AAID)

In this case, how can we comply with the new Advertising policy?

imagen
imagen1173×937 79.7 KB

#5

That is the same e-mail I received.

  1. Instead of being required for the target of 12, it is now required for the target of 13. ( “give developers more time to ease the transition”).

  2. You have to add the permission for anything above target 12 or you get a bunch of 000s (like we do in iOS). If you don’t care if you receive a bunch of 0s for the id then you don’t have to do anything.

  3. You shouldn’t add this particular permission to apps that target children. Because children should not be tracked.

The sentence that you highlighted is not in isolation. It is part of the actions required related to the new requirements to receive something other than 000s. Unless you are using that Id for something you shouldn’t worry. At least not until you target SKD 13.

#6

Makes sense thanks for clarifying @agramonte