Funding choices still not working correctly

[Frank]

Hi

Funding choices is still not working correctly under Android

When the user hits „Agree“ everything is fine with ads

When the user goes to „Options“ and hits the „Send“ button
whithout changing everything then ads failed to load with errorcode.

This means we are all bancrupt in a short period.

At least non personalized ads schould be shown if the user hits Send“ without changing anything

Also an option to quit the app or buy a pro version should be offered if ads are turned off like before in the old sdk

Next problems are

Consent status is always unknown and

even if the user changes things in the options for example activates personalized ads and hits „send“ then also no ads will
be shown

I hope you fix this soon or nobody will have an income anymore soon when we get forced to use ump I think this be happen soon

Frank

[Mobile Ads SDK Forum Advisor Prod]

Hi Frank,

Thank you for bringing this to our attention. Can you share with us a sample of the code that you are using so that we can look over it and see what we can do to help you. As well as any stacktrace or error messages you are getting. Also if you have Charles logs that help to capture this behavior that would also be appreciated.

Regards,

William Pescherine Mobile Ads SDK Team

 

ref:_00D1U1174p._5004Q23v9D5:ref

[fran...@gmail.com]

Hi 

some other people have already mentioned this problems too. 

I did nothing else than following the guide here  with admob test ad ids:

https://developers.google.com/admob/ump/android/quick-start

also i have added google as ads provider  ! 

it is really important to improve this so we do not lose all our income. 

The "old" consent has the options : personalized, non personalizes or quit (purchase) the app. 

And the UMP should to the same in my opinion but as i mentioned in my message the ads will not load anymore. and the error code is 3 . 

User hits " Not agree"   or "Send" button 

no ads will be served anymore even no non personalized apps .

This is the worst case = no income anymore

Then we must deny access to the application or offer only a pro version  or reset the consent so the user can agree again. This would be only possible with an extra layout with options at the moment

Next problem : Even if the user goes to the options and turns "personalized ads " on and hits the "Send button" then also no ads will be served anymore  - also worst case 

The key [IABTCF_PurposeConsents] 01 

Also turning on in options: simple ads, personalized ad,  save device identifier and hitting "Send" will result in no ads anymore. 

User hits "agree" - this will happen 

 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_CmpSdkID] 300

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_CmpSdkVersion] 1

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PolicyVersion] 2

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_gdprApplies] 1

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PublisherCC] DE

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeOneTreatment] 0

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_UseNonStandardStacks] 0

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_VendorConsents] 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_VendorLegitimateInterests] 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeConsents] 1111111111

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeLegitimateInterests] 0100111111

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_SpecialFeaturesOptIns] 1

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_TCString] CO4o1cqO4o1cqEsABBDEA0CoAP_AAE_AAAYgF5wAwAuAJ0AXmBecAIALgC8wAA

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_AddtlConsent] 1~1716.827

2020-08-24 11:31:32.756 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_UserConsentRecordId] C2F9453F-C91C-4A8F-81B9-2291D56AFD92

2020-08-24 11:31:32.757 5747-5747/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=dismiss&args=%7B%22status%22%3A%22CONSENT_SIGNAL_SUFFICIENT%22%7D

2020-08-24 11:31:32.757 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[dismiss]: {"status":"CONSENT_SIGNAL_SUFFICIENT"}

2020-08-24 11:31:32.759 5747-5747/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=complete

2020-08-24 11:31:32.791 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[complete]: {}

2020-08-24 11:31:32.843 5747-5747/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=load_complete&args=%7B%22status%22%3A%22ok%22%7D

2020-08-24 11:31:32.843 5747-6012/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[load_complete]: {"status":"ok"}

2020-08-24 11:31:32.862 5747-5747/com.example.consentdialogtestapp D/UserMessagingPlatform: Wall html loaded.

2020-08-24 11:32:08.319 5747-5773/com.example.consentdialogtestapp W/System: A resource failed to call release. 

The key [IABTCF_PurposeConsents] 1111111111

User hits "Not agree " - no ads will be served anymore with error code 3

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_CmpSdkID] 300

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_CmpSdkVersion] 1

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PolicyVersion] 2

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_gdprApplies] 1

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PublisherCC] DE

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeOneTreatment] 0

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_UseNonStandardStacks] 0

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_VendorConsents] 0

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_VendorLegitimateInterests] 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeConsents] 0

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeLegitimateInterests] 0100111111

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_SpecialFeaturesOptIns] 0

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_TCString] CO4o0x1O4o0x1EsABBDEAzCgAAAAAE_AAAYgAAALzgBABcAXmAAA

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_AddtlConsent] 1~

2020-08-24 11:26:12.240 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_UserConsentRecordId] 70DDADE8-038C-42F6-9B38-18318BF88578

2020-08-24 11:26:12.245 5071-5071/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=dismiss&args=%7B%22status%22%3A%22CONSENT_SIGNAL_SUFFICIENT%22%7D

2020-08-24 11:26:12.246 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[dismiss]: {"status":"CONSENT_SIGNAL_SUFFICIENT"}

2020-08-24 11:26:12.247 5071-5071/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=complete

2020-08-24 11:26:12.284 5071-5493/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[complete]: {}

The key [IABTCF_PurposeConsents] 0

User hits "Send " button in option without "touching" anything. - no ads will be served anymore with error code 3

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_CmpSdkID] 300

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_CmpSdkVersion] 1

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PolicyVersion] 2

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_gdprApplies] 1

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PublisherCC] DE

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeOneTreatment] 0

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_UseNonStandardStacks] 0

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_VendorConsents] 0

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_VendorLegitimateInterests] 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeConsents] 0

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeLegitimateInterests] 0100111111

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_SpecialFeaturesOptIns] 0

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_TCString] CO4z87mO4z87mEsABCDEA0CgAAAAAE_AAAYgAAALzgBABcAXmAAA

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_AddtlConsent] 1~

2020-08-27 20:27:55.752 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_UserConsentRecordId] D65B36FE-51BB-4829-ABA6-C1F25B4CC961

2020-08-27 20:27:55.755 24153-24153/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=dismiss&args=%7B%22status%22%3A%22CONSENT_SIGNAL_SUFFICIENT%22%7D

2020-08-27 20:27:55.756 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[dismiss]: {"status":"CONSENT_SIGNAL_SUFFICIENT"}

2020-08-27 20:27:55.756 24153-24153/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=complete

2020-08-27 20:27:55.797 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[complete]: {}

2020-08-27 20:27:55.851 24153-24153/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=load_complete&args=%7B%22status%22%3A%22ok%22%7D

2020-08-27 20:27:55.852 24153-24240/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[load_complete]: {"status":"ok"}

2020-08-27 20:27:55.870 24153-24153/com.example.consentdialogtestapp D/UserMessagingPlatform: Wall html loaded.

The key [IABTCF_PurposeConsents] 0

[Mobile Ads SDK Forum Advisor Prod]

Hi Frank,

Thank you for all that information it will really help us to look further into this for you. 

I have just one other question to ask you. Have you looked at your AdMob account dashboard recently? And if so have you seen any warning or messages in it mentioning the "IAB TCFv2.0"? Or even when testing out the UMP have you seen anything in the dashboard related to this?

[fran...@gmail.com]

Hi William

yes but there is no message. Only a message related to ios14  app developing.

So i hope you will find a good solution soon and fix the bugs/problems. 

With all these problems at the moment it is impossible to integrate UMP . Is is a big problem for maybe 90 % of all developers to who have ads in their apps. 

Frank

[Mobile Ads SDK Forum Advisor Prod]

Hi Frank,

I work along with William. Thank you for reporting this. Let me raise this issue to the rest of the team for further investigation. We'll update this thread the soonest we have our findings.

Regards,

Teejay Wennie Pimentel Mobile Ads SDK Team

ref:_00D1U1174p._5004Q23v9D5:ref

[John Doe]

Same problem on iOS (checked on simulator with iOS 14). I just did not report it because already saw it in the threads and though you were aware of it. Pressing More Options, then Send turns off all ads, so the latest UMP SDK is not ready neither on Android nor on iOS (

[fran...@gmail.com]

Hello 

any news on this ? 3 weeks are gone now ... Still got no answer and there are no changes on the google documents page. 

When will you give out any information that you will fix all the bugs /make improvements ?  Since almost 3 weeks i want to use the new UMP but i "cannot" use it 

because you do not communicate anything with us. I must still use the old Consent SDK for Android

Still no non personalized ads will be shown if the user hits "send" in the options and there is still no consent status. 

The key [IABTCF_PurposeConsents] 0

The only thing i could do at the moment is to "force" the user to agian and again and again to agree  and reset the consentinformation every time as long as the pref key is 0  to prevent that not ads will be shown 

But this is not what we want and need. We need a fast solution and also an answer. We cannot offer apps without any "ads" and loose all our income. 

We need a fast and good solution also to "quit" the app if the user turns everything off to offer maybe a premium version  like before to "prevent" using the app without ads

So many people gave you information here about all the problems with the new UMP but you do not give any answer

Frank

[Bastiaan van den Berg]

Dear Google Mobile Ads SDK team,

I have the exact same problem, and probably many have. I published my Android apps with the UMP SDK integrated according to the documentation. Now it turns out that if a user does not consent, but chooses 'Manage Options' and presses 'Submit', no ads are shown at all. So clearly something is wrong, and it takes away our income! Can this please be resolved soon. And could somebody give some clarification about this? How can this have been released as a stable version? How can this have been missed? 

Kind regards,

Bastiaan

[Bastiaan van den Berg]

I just got a TCF error report on my AdMob dashboard, which reports error 1.1 for my apps that include the UMP SDK.

The suggested action to take for this error is:

"Confirm whether the user intentionally rejected Google as a vendor, CMP implementation errors have occurred, or there are publisher restrictions."

Does this mean I did something wrong? For me it is not really clear what I need to do to resolve this.

[AppA11y]

What is the solution to this??

[mydevelo...@gmail.com]

up ++++++++++

27 Ağustos 2020 Perşembe tarihinde saat 20:09:44 UTC+3 itibarıyla mobileadssdkforumadvisor şunları yazdı:

[mydevelo...@gmail.com]

Hi,

- Consent form is opened there is no problem for it but when i click do not consent button or manage >> submit  The ads are isn't showed and ConsentInformation.ConsentType always stays at 0.

Proposal:   

Personalized ads should show When Allow is selected, Non-personalized ads should show when not allowing. No advertisements should not be, otherwise we will be offering our applications for free. In addition, if the user does not want to see ads in any way, they should not use the application or be directed to the paid version.

13 Ekim 2020 Salı tarihinde saat 15:06:08 UTC+3 itibarıyla mydevelo...@gmail.com şunları yazdı:

[hdfkFg589Dx.s]

The problem persists.

In short, what should we do?

[Mobile Ads SDK Forum Advisor Prod]

Hi Frank,

Thank you for the response back, and know that we have spoken a lot with our team about the concerns that developers have brought to our attention. Allow me to try to answer some of your concerns as best we can.

Getting consent string:
The best way that we have suggested for people to get the consent string was with the shareInstance as well as using 3rd party CMP's. These have been suggested as ways to go about getting it. But even then the issue is having to parse the string, which IAB controls and changes very often. So this would require massive energy to update to keep up with the changes.

The ability for users to Opt-Out so easily:
This is one that has also been discussed and at present is working as intended. The UMP SDK does give you access to the non personalized ads as it should.Just depending on how much inventory is available at anytime will dictate if ads will be getting served.

To our knowledge the UMP SDK has been designed to meet the standards of the EU GDPR. So as to be in compliance with what they want. You can also talk with our Product Support Team , as they are more hands on when dealing with the ads serving.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2CSOam:ref

[discover]

Sorry, but I do not understand...

"The UMP SDK does give you access to the non personalized ads as it should"

No. If you press the "Do not consent" button, the ads are not delivered

[Mobile Ads SDK Forum Advisor Prod]

Hi Discover,

Thank you for responding back. What I mean by that is that we have tested this also on our end. And have seen that non personalized ads will be served even when no consent is given. But due to other factors, things such as eCPM or available inventory is what is causing ads to not be served. At the same time we are constantly looking at this and mentioning to our team that this seems to be an issue. But at this moment there is nothing new to pass along beyond that.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2CSOam:ref

[mobile bee]

Hi mobileadssdkforumadvisor, so what you are saying is even if the user didn't accept to "Store and/or access information on a device ", non-personalized ads still will be showed?

Regards.

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

I work with William and will assist you. 

Regarding serving non personalized ads, in AdMob & AdSense program policies Publisher integration with the IAB TCF v2.0 it states:

If the consent requirements for personalized ads are not met, Google will serve non-personalized ads when all of the following criteria are met:

• The end user grants Google consent to:
  • Store and/or access information on a device (Purpose 1)
• Legitimate interest (or consent, where a publisher configures their CMP to request it) is established for Google to:
  • Select basic ads (Purpose 2)
  • Measure ad performance (Purpose 7)
  • Apply market research to generate audience insights (Purpose 9)
  • Develop and improve products (Purpose 10)

I just tested without mediation partners and found that when consenting to Purpose 1 and on the vendor list consenting to Google then test ads from Google can show. When "Manage options" is selected with a consent for everything on the that page without selecting Google as a vendor then no ads show. Note that mediation partners may have different consent requirements.

Regarding selecting "Manage Options" and then pressing "submit", 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.

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.

Regarding consentStatus always being unknown, I couldn't replicate this issue in testing. You may send us privately (via Reply to author, or a direct, private reply to this email) a project that gives only unknown consentStatus to test on our end. 

Regards,

Aryeh Baker Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2CSOam:ref

[AndreasB]

> To learn more, visit the IAB Europe’s Appendix B, Policy C(d.

That section explicitly mentions a "default choice", though. No one here argues that a user should see anything but "off" or "no consent" when visiting this "secondary layer" when the dialog is first being displayed.

However, If a user already made their own choice (gave consent) before visiting the secondary layer later, it is unreasonable to assume that a user should still see a "default choice" on each subsequent visit to the secondary layer instead of their own choice.

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for bringing this up. I will raise up with my team your request for allowing prior consent to dictate toggle position. You may monitor our release notes in iOS and Android for an update.