IABTCF_gdprApplies still returns 1

[Konstantin Shkulev]

Hi! We are using the latest Google Mobile Ads SDK for Unity to obtain consent from EU users via Google UMP. Our testers found a bug where IABTCF_gdprApplies does not change its value when user moves out from EU.

Steps to reproduce:
1. Use VPN of EU country to fake your location
2. Launch game and gave consent in CMP window
3. Close game
4. Disable VPN (you must live outside EU) or use VPN of non-EU country
5. Launch game

In this case after updating ConsentInformation IABTCF_gdprApplies is still set to 1 with ConsentStatus = Obtained and PrivacyOptionsRequirementStatus = Required.

Is this a bug or a proper behaviour, like if user once applied to GDPR he still be able to manage consent even if he lives outside of EU?

[Mobile Ads SDK Forum Advisor]

Hi,

Thanks for contacting us.

I am checking your concern and will get back to you shortly.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ7RA:ref" (ADR-00236924)

Thanks,
 

Mobile Ads SDK Team

[Mobile Ads SDK Forum Advisor]

Hi,

It appears to be an intended behavior. According to the IAB, there is a requirement to display a consent pop-up for users in the European Economic Area (EEA), but no such requirement exists for users outside the EEA. If a user first logs in from a non-EEA location, all ads will be served. However, If the user declines consent, limited ads will be served.

If a user transitions from a non-EEA location to an EEA location, the IABTCF_gdprApplies flag will change and the user will be given the option to update their consent preferences. Conversely, if a user transitions from an EEA location to a non-EEA location, consent is no longer applicable and ads will be served normally. This is similar to the iOS ATT pop-up. If the user grants permission, ads will be served regardless of the user's location. 

For debugging purposes, you can use the UMPConsentInformation reset method to reset the consent logic. This will reset the IABTCF_gdprApplies flag and all other consent-related settings. 

To resolve your current issue, you should store the user's previous region in the device's defaults. If the user's previous region was the EEA and their current region is non-EEA, and the user has previously granted consent, you should reset the consent settings and proceed accordingly.
This should resolve your current issue.

Kindly get back to us if you need any other help related to Mobile Ads SDK.