Is ads initialization after consent bugged?

[andrea...@gmail.com]

Implemented UMP in the start of August and initialize the ads after consent info update in this way

ConsentRequestParameters params = new ConsentRequestParameters
                .Builder()
                .setTagForUnderAgeOfConsent(false)
                .build();

consentInformation = UserMessagingPlatform.getConsentInformation(this);
        consentInformation.requestConsentInfoUpdate(
                this,
                params,
                new ConsentInformation.OnConsentInfoUpdateSuccessListener() {
                    @Override
                    public void onConsentInfoUpdateSuccess() {
                        createAds()
                    }
                },

Ads visualization dropped badly, and this not just in Europe (where you may think it could be caused by user refused consent), but in ALL countries with a sharp drop in USA that are our main market. Could be the fact we create ads onConsentInfoUpdateSuccess the cause of the issue?

[P. S.]

Same problem here. After implementing User Messaging Platform the app visualization dropped badly.

If a user consents ads will be show. But if the user does not consents or only partitially consents no ads appear anymore.

[P. S.]

I've now added an await at MobileAds.initialize(). So that MobileAds is initialized before anything is done to get or obtain user consents. Because here it says:

2. Should I ask GDPR consent before Admob.init() or after? Does sequence matter or not?

• You should initialize the Mobile Ads SDK first

I hope this to help. 

Future<void> main() async {
    WidgetsFlutterBinding.ensureInitialized();
    await MobileAds.instance.initialize();
    // ...
    await UmpContext.instance.initialize();
    // ...
}

[andrea...@gmail.com]

Thanks for the reply, but if ads SDK is initialized before UMP, doesn't this work outside GPDR rules because it hasn't consent info at moment of the loading?

[diablins...@gmail.com]

I think it is bugged, same problem here

[diablins...@gmail.com]

After reading a lot of threads... it's not a bug, it's they way it works. If a user rejects to store cookies (both, "No consent option" or  default "Manage options" switches) then google will not serve ads because he needs to set cookies in their ads. And no consent means no ads displayed. Since 2020 this is working like that, and EEE is forcing now to show consent dialog.

I only find 2 fixes for this:

- Find another ad provider that doesn't work like this.
- Force users to consent or deny them to use the app.

My app will die soon

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for reaching out to us. Please do note that there are condition that needs to meet before ads shows to your app via consent. Detailed information can be found here: https://support.google.com/admob/answer/9760862?hl=en&ref_topic=9756841.
 

This message is in relation to case "ref:_00D1U1174p._5004Q2oAaeA:ref"

Thanks,
 

Mobile Ads SDK Team

[FraG]

Won't "most" apps die, then? I'm in the same boat.

- Did you find another ad provider? 

- Do you know of any app that did implement the "Forced consent" without getting tons of negative reviews?

[diablins...@gmail.com]

Hi FraG,

No, i still use the old way until someone release a fix for that. I don't understand why "no consent" means "no ads". I don't care users don't see personalized ads, but seems google can't show ads if they don't allow to store cookies on the device.

So yes... i think many free apps with ads will die, mine included.

[Mobile Ads SDK Forum Advisor]

Hi Frag,

Thank you for reaching out to us.

Can you provide us more information with regard to your concern? Based on the subject itself, have you experience any implementation concern for the consent? Can you confirm if you're using the UMP SDK?

This message is in relation to case "ref:_00D1U1174p._5004Q2oAgyt:ref"

Thanks,
 

Mobile Ads SDK Team

[P. S.]

A "declined consent" or "partitially declined consent" may result in an empty app with a decision screen to either accept the consent or buy the premium version via in-app-billing. So that it is a "soft forced consent".

But there is currently no way to check what the user has selected. Or did I saw it wrong? In this case using another ad provider could be a good option. Or is Google planning to add a solution here?

[P. S.]

Using https://support.google.com/admob/answer/9760862?hl=en&ref_topic=9756841 there should be an app option for the publisher to see whether the end user has accepted the consents for purpose 1, 2, 7, 9 and 10 to check if the user agrees to see at least non-personalized ads.

Something like this...

ConsentInformation.instance.userAcceptedConsentForPersonalizedAds(); // true/false
ConsentInformation.instance.userAcceptedConsentToSeeAtLeastNonPersonalizedAds(); // true/false
ConsentInformation.instance.userAcceptedNotEnoughConsentToSeeAnyAds(); // true/false

[spyNet Camera]

You can find a good solution here:

https://stackoverflow.com/questions/65351543/how-to-implement-ump-sdk-correctly-for-eu-consent/68310602#68310602

https://stackoverflow.com/questions/69307205/mandatory-consent-for-admob-user-messaging-platform/70324431#70324431

At lest, we can check whether the user choices will allow to show ads and show a message if not...