Questions on Ad Initialization, Consent Caching, and Popup Handling

[RoxDevvv]

Hello InMobi Team,

I have some questions regarding the implementation of consent management and ad initialization within the InMobi SDK, particularly concerning GDPR, CCPA, and other consent-related APIs. I would appreciate your clarification on the following points:

• When to Initialize Ads and Determining Consent Status:

Given the multiple callbacks and varying consent data (such as GDPRData, CCPA String data,USRegulationData , and others), it is unclear when it is safe to initialize ads and how to definitively determine whether the user has accepted consent.

How do we know when to initialize ads based on the consent status from these callbacks?

How can we properly handle scenarios where consent data might be incomplete or unclear?

• Consent Caching:

Is there a way to cache the user's consent status so that we don’t need to request consent again every time? How can we retrieve and store consent data for future use, ensuring that we don't re-prompt the user unnecessarily?

• Forcing the Consent Popup:

In which scenarios should the consent popup be triggered again? For example, if the user previously accepted consent, should the popup be shown again under any circumstances (e.g., policy updates or user revocation)?

• Handling Consent Changes and CMP Versioning:

How can we detect when the consent policy or version changes (e.g., updates to GDPR or CCPA)? If the consent policy has changed, should the cached consent be invalidated, and if so, how should this be handled?

Any guidance, clarification, or examples would be greatly appreciated.

Thank you!

[AbdulBasit-InMobi]

Hi there,

Please go through our documentation here it entails all the information regarding different regulations, how and where they are applicable and also the callbacks that give the required consent given by the user and other related information. If you are still not clear about the behaviour and implementation please reach out to us at cmp-support@inmobi.com

Regards

[RoxDevvv]

Thanks for the link. I’ve gone through the documentation before posting, I’m still unsure about one key part: When exactly is it safe to initialize ads based on consent callbacks data like GDPRData, USRegulationData, and CCPA strings?

Do i have to dig into those data to find out if user consent or i just initialize ads as soon as the callbacks fire.

The docs don’t clearly explain how to handle cases where data is incomplete or missing, or how to cache and reuse consent properly without showing the popup again , looks like the plugin doing that already but there is no exposed function that i can use to know if user already cached

Could you please clarify or provide a small code example?

Also i already send email.
Thank you.

[AbdulBasit-InMobi]

If your integration requires only GDPR consent, you should use the CMPDidReceiveIABVendorConsentEvent callback to initialize the Ad SDK. This event is triggered when the user grants consent for the first time, as well as on subsequent launches after the SDK has been initialized.

For MSPA/CCPA consent, use the CMPDidLoadEvent callback to trigger Ad SDK initialization. The Ad SDKs are expected to read the consent data directly from persistent storage, using the standard IAB-defined keys.

If your use case involves explicitly passing the consent string during SDK initialization, you can retrieve the appropriate value from persistent storage (e.g., UserDefaults or Shared Preferences). Manual caching of the consent string is not required, as consent management is handled internally by the CMP.

Please contact our support team for assistance and any necessary follow-up.

[RoxDevvv]

Hi , Thank you for clarification ,
There is small problem CMPDidReceiveIABVendorConsentEvent does not trigger again in subsequent launches
the only thing trigger in subsequent launches is CMPUIStatusChangedEvent after CMPDidLoadEvent

is that a bug !

[AbdulBasit-InMobi]

You can check the GPP string value in the CMPDidLoadEvent. If it's empty, initialize the ad SDK in the CMPDidReceiveIABVendorConsentEvent; otherwise, initialize the SDK directly in the CMPDidLoadEvent.