Non-personalized ads still shown in GDPR area despite correct consent and initialization

[Walter]

Hi everyone,

I'm experiencing an issue where non-personalized ads (npa=1) are being shown to testers in GDPR regions, even though everything seems to be configured correctly.

Here’s the situation in detail:

• The app is built with Flutter, using the package google_mobile_ads: ^6.0.0.
• Consent flow is correctly implemented and initialized before any ad requests.
• The Google Ads Inspector reports that everything is in order.
• I decoded the TCF string from the inspector and all the relevant purposes and vendors (including Google) are correctly consented.
• Firebase DebugView confirms that consent signals are being updated:

D/UserMessagingPlatform(19529): Update Firebase: { AD_STORAGE=GRANTED, ANALYTICS_STORAGE=GRANTED, AD_USER_DATA=GRANTED, AD_PERSONALIZATION=GRANTED }

• The InMobi adapter is also correctly referenced and initialized:

D/InMobiMediationAdapter(19529): InMobi SDK initialized.

However, despite all this, I still see:

• Testers in GDPR regions receive non-personalized ads.
• In Firebase, the parameter non_personalized_ads=1 is always set, even when full consent has been granted.
• Outside the GDPR area, the value is correctly non_personalized_ads=0, and personalized ads are served as expected.

Does anyone know what might be causing this behavior? Is there a possible misconfiguration in AdMob’s settings or something specific about the Flutter plugin that could be overriding the personalization flag?

Any suggestions or insights would be really appreciated!

Thanks in advance!