Hi Joe,
I work with Teejay and will assist you. The consent user gives is stored in a TCF string in
SharedPreferences in Android, and in NSUserDefaults in iOS. The latest versions of the Mobile Ads SDK automatically pick up the TCF Consent String from that storage and ads get served based on consent given. There's no need to set your own flags as the SDK picks up the consent automatically.
Regarding seeing no ads when all toggles on the "Manage options" page are selected, I replicated this. Currently, without mediation, once you "Manage Options", you can select Google as a vendor in the "Vendor List" to see ads from Google. To see test ads, all you need to do is to consent to purpose 1 and to Google.
Regarding toggles always appearing in the "off" position, this may be working as intended - in
How IAB requirements affect EU consent messages, it states that the default state of each consent toggle in your EU consent message is set to “no consent,” “no opt-in,” or “off.” If you use Funding Choices as your CMP, this means that users who select “Manage options” in the consent message see that each purpose is set to “Do not consent.” To learn more, visit the
IAB Europe’s Appendix B, Policy C(d.
Regarding a method to determine consent given after consent is submitted, there are currently many
CMP vendors besides UMP with Funding Choices that will work with the Mobile Ads SDK and some may have consent detection methods set up to assist you in creating a paywall, you may want to explore to see which one fits your needs better.
I will raise with the rest of my team your requests and comments for:
- a method to determine consent given so that paywall functionality can be implemented
- accessing prior consent obtained from user and showing the user the options already consented to.
You may monitor our release notes in
iOS and
Android for an update.
Regards,
 |
Aryeh Baker |
Mobile Ads SDK Team |
|
|
|

ref:_00D1U1174p._5004Q2DIQGb:ref