Conversation
- UmpConsentService gathers consent via Google's UMP SDK after the first frame and initializes Mobile Ads only when requests are allowed - Consent failures never block the app; stored consent still applies - Remove the hard nonPersonalizedAds flag from banner/rewarded requests so consented users get personalized fill (UMP signals govern serving) - Settings → Permissions gains an "Ad privacy options" entry when the user's region requires a revisitable consent choice
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
UMP consent flow: gathers ad consent via Google's UMP SDK after the first frame, initializes Mobile Ads only when allowed, and removes the hard non-personalized-ads flag so consented users get personalized fill. Settings gains an ad privacy options entry for regions that require it.
Version 1.0.14+18.