Hi Dmitri,
Some additional clarifications here:
a) Flutter documentation is currently available at
https://developers.google.com/admob/flutter/eu-consent
b) For child users, if the user is under 16, you should set
https://pub.dev/documentation/google_mobile_ads/latest/google_mobile_ads/ConsentRequestParameters/tagForUnderAgeOfConsent.html when creating ConsentRequestParameters. This will indicate to the UMP SDK that the form shouldn't be presented, but still let the UMP SDK write to local storage per the
IAB TCF spec that the user is a child.
c) Once you show the form (or don't show it because after calling requestConsentInfoUpdate, the status was not_required), as long as the
status not_required or obtained, you can make ad requests. The status will still be "obtained" if you show the form and the user doesn't consent to anything. But in that case, the ad server would drop the request if nothing is consented, or handle partial consent depending on what is set. If your app gets a no fill, from there you can act accordingly.
d)
https://support.google.com/admob/answer/9760862 explains what purposes are required for both personalized and non-personalized ads. If neither of those requirements are met (i.e. user consents to no purposes), ad requests will fall back to limited ads mode (
https://support.google.com/admob/answer/10105530) which today effectively means AdMob won't serve an ad, but your waterfall mediation partners might if you integrate mediation.
e) Just this past month, we made some simplifications to the Android/iOS UMP SDKs (
https://ads-developers.googleblog.com/2023/08/weve-made-updates-to-user-messaging.html). These haven't graduated to Flutter yet, but is on the roadmap for later this year. So some of the above steps should hopefully be even easier to implement once that launches.
Thanks,
Eric, Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2mwZSs:ref