These are some common questions that publishers may have while implementing MSPA.
If the end-user changes state, there is no mapping of the consents between different sections. Instead, the InMobi CMP will signal to the publisher (via an API) that the end-user has changed states and needs to be re-shown the consent screen. The responsibility is on the publisher to then re-trigger the consent screen. To see the APIs to check user location and trigger consent screen, see APIs to Trigger MSPA Consent Screen.
If the end-user travels from the US to EEU/UK, then the GPP string for the US will not be deleted. Instead, the GDPR consent screen for EEU/UK will be shown. Similarly, if the user travels from the EEU/UK to the US, then the GDPR will not be deleted and the MSPA consent popup will be shown for the U.S region.
If a user has a CCPA string and the publisher enables GPP, the US Privacy consent string will not be deleted. Depending on whether the publisher has set the auto-display of the consent screen, the MSPA consent popup will be shown to the user.
To understand why GDPR is not applicable in the US and why US regulations are applicable only in the US, see Why doesn’t InMobi CMP support GDPR in the U.S?
By installing this SDK update, you agree that your Children Privacy Compliance setting remains accurate or that you will update that setting, whenever there is a change in your app's audience. You may update the app's Children Privacy Compliance settings at https://publisher.inmobi.com/my-inventory/app-and-placements.
Support Center
