applovinAsh
commented
11 months ago We are in the process of updating our SDK to support Google's CMP demands. More information regarding use with Google-certified CMP and SDK updates will be provided soon. We will not have our CMP. For information that is currently available, see here: https://dash.applovin.com/documentation/mediation/ios/getting-started/privacy#tcf-v2.0-consent
You must set binary consent until the SDK update and for networks not supporting TCF Strings. For information on how to set binary consent, see here: https://dash.applovin.com/documentation/mediation/ios/getting-started/privacy#consent-and-age-related-flags-in-gdpr-and-other-regions
MAX SDK Version
11.11.3
Device/Platform Info
iOS 16
Current Behavior
Following on from this issue: https://github.com/AppLovin/AppLovin-MAX-SDK-iOS/issues/58 I'm really struggling to get this GDPR consent working.
I have implemented the Google CMP, but it doesn't seem possible to retrieve the actual consent (true/false) from this, and thus it's not possible to set
hasUserConsenton the AppLovin SDK. The Google docs say they do not set these values for third party SDK's so we must do it, but how can we when we can't get access to what the user selected?Does anyone have another recommended CMP to use? Can AppLovin not add their own CMP flow to the SDK so make all this easier?
Expected Behavior
No response
How to Reproduce
.
Additional Info
No response