Consent Manager (GDPR, CCPA, ATT)
1. Request Consent Info Update
Consent manager SDK can be synchronized at any moment of the application lifecycle. We recommend to synchronize it at application launch. Multiple synchronization calls are allowed.
Required parameter is
appKey - Appodeal API Key and
ConsentInfoUpdateListener - listener for result request.
After request completion, you can receive information about the previous user consent and regulation zone. Before request these parameters are
You can check whether to show a Consent Dialog or not. Before request these parameters are
You can force consent manager to write iAB keys in
SharedPreference by setting up storage property before the request to
SDK does not remove iAB keys from
SharedPreference and only overrides them
You can register yourself as a vendor before request.
|name||String||Display name. Will be displayed in the consent window|
|bundle||String||Custom string to check consent result for the vendor|
|purposeIds||Array of integers||iAB purposes ids array|
|featureIds||Array of integers||iAB features ids array|
|legitimateInterestPurposeIds||Array of integers||iAB leg int purposes ids array|
2. Show Consent window
SDK allows calling consent window API only after request
After the SDK requests, you can build and load the consent window. Loading allowed in any regulation zone and independent from previous consent.
You can check that the consent window is ready or not
You can check that the consent window is showing or not
After consent window Is ready you can show it as Activity or Dialog
Handling presentation callbacks
3. Error handling
All returned errors are Exception instances with custom codes:
|INTERNAL(1)||Error on the SDK side. Includes JS-bridge or encoding/decoding errors|
|NETWORKING(2)||HTTP errors, parse request/response|
|INCONSISTENT(3)||Incorrect SDK API usage|