Allow only Google UMP flow without AppLovin's "Terms of Service and Privacy Policy prompt"

[AntonPetrov83]

Feature Description

Is it possible to enable only Google UMP consent for GDPR-regions without enabling the AppLovin's "Terms of Service and Privacy Policy prompt" ???

From the documentation:

Regional Compliance Check: If the user is not age-restricted under COPPA, AppLovin determines whether the user is located in a GDPR region. If the user is in a GDPR region, the MAX SDK presents Google UMP. If the user is not in a GDPR region, MAX SDK presents the user with a Terms of Service and Privacy Policy prompt. This step ensures that users are informed about data collection and usage and have the option to consent or decline.

[gulliversgames]

This is definitely needed. We implemented our own "Terms of Service and Privacy Policy" prompt in our game on a native good-looking popup. In previous ApplovinSDK versions, there was an option to use it in platform-specific. However in 12.0.0 version, that option gone and all apps (with Google UMP flow) are forced to use most-disgusting-popup-ever on Android to show their TS/PP as below:

[santoshbagadi]

We use the Android native System pop up. It looks like your app has a very old Android Support Library which is causing it to show the old Android popup. Updating to newer AndroidX jetpack libraries should give you a more material style popup.

The CMP flow provided by us is optional, and you may use your own CMP flow to gather consent. Just make sure that our SDK is initialized after the CMP flow finishes. Our SDK will be able to get the TCF string from the disk written by the CMP and pass it along to the mediation providers as described in this doc: https://dash.applovin.com/documentation/mediation/unity/getting-started/privacy#tcf-v2-consent

We are going to discuss internally on providing just the CMP flow, and will leave this ticket open to update on the progress.

[bartutiryakioglu]

@santoshbagadi We tried updating our support libraries but Applovin SDK's dependencies conflict with the new ones as you can see from the below picture. We are using 12.0.0 version and we tried to resolve dependencies through EDM4U in an empty project. It would be really good if we could separate platforms for this feature.

[santoshbagadi]

You may have to enable Main Gradle Template to make sure that the old libraries are not resolved.

[bartutiryakioglu]

@santoshbagadi we have other libraries which external dependency manager resolves and we can not use external dependency manager with main gradle template. Is there any other option for this problem. You suggested us to use new androidx jetpack but Applovin SDK forces us to use the legacy one.

[santoshbagadi]

Our SDK doesn't have any dependencies that require legacy support libraries. It seems like it is a bug in the External Dependency Manager that resolves to older support libraries.

Here are the only two dependencies of our library, which only use AndroidX libraries.

• https://mvnrepository.com/artifact/com.google.android.gms/play-services-ads-identifier/17.1.0
• https://mvnrepository.com/artifact/com.google.android.gms/play-services-appset/16.0.0

[plotlessplot]

+1 for using Google UMP to obtain consent without also having to trigger AppLovin's "Terms of Service and Privacy Policy" prompt. We'd like to keep using our own UI for that but also trigger the CMP message via MAX (for ease of implementation).

I would also like to know how is localization handled for the "Terms of Service and Privacy Policy" prompt. We currently translate our own T&C/PP popup to 6 different languages and I'd like to know if the prompt will be localized if we use MAX's Consent Flow to simplify the Google UMP implementation.

[pfay-fc]

Similarly, it would be nice if we could also use our own iOS App Tracking Transparency flow while making use of Applovin's out-of-the-box Google UMP support.

[wojciech-juszczynski]

We are going to discuss internally on providing just the CMP flow, and will leave this ticket open to update on the progress.

@santoshbagadi any updates on that?

[santoshbagadi]

After careful consideration, we've decided not to proceed with this feature. We believe that accommodating such customizations would introduce significant complexities.

Our SDK would still be able to get the consent from CMPs if you decide to implement your own custom solution. You'd just need to make sure that the user completes the flow before initializing our SDK.

[bartutiryakioglu]

We use the Android native System pop up. It looks like your app has a very old Android Support Library which is causing it to show the old Android popup. Updating to newer AndroidX jetpack libraries should give you a more material style popup.

The CMP flow provided by us is optional, and you may use your own CMP flow to gather consent. Just make sure that our SDK is initialized after the CMP flow finishes. Our SDK will be able to get the TCF string from the disk written by the CMP and pass it along to the mediation providers as described in this doc: https://dash.applovin.com/documentation/mediation/unity/getting-started/privacy#tcf-v2-consent

We are going to discuss internally on providing just the CMP flow, and will leave this ticket open to update on the progress.

I would like to ask something related to that problem. When we call permission request from Unity.Notifications plugin, popup comes with the new Android UI as you can see from the below picture. However, when we call ump or privacy policy from Applovin's plugin, popup comes with the old UI. Are you sure that this is not related to how you call that popup?

[santoshbagadi]

The permissions dialog doesn't rely on the Application's theme. This comes from the Android OS itself (instead of the application's theme).

[bartutiryakioglu]

The permissions dialog doesn't rely on the Application's theme. This comes from the Android OS itself (instead of the application's theme).

Do you have any idea why would the theme is different for the first pic @gulliversgames uploaded and the last pic I upload?