DidomiSdk
class. Also make sure to always call the SDK after it is fully initialized (see onReady).ready
event has been triggered.EventListener
EventListener
purposeId
provided as a parameter)purposeId
provided as a parameter)vendorId
provided as a parameter)vendorId
provided as a parameter)userStatus.purposes?.consent?.disabled
.Future<List<Purpose>>
Purpose
containing the purposes disabled by the user.userStatus.purposes?.consent?.disabled
.Future<List<String>>
String
containing the IDs of purposes disabled by the user.userStatus.vendors?.consent?.disabled
.Future<List<Vendor>>
Vendor
containing the vendors disabled by the user.userStatus.vendors?.consent?.disabled
.Future<List<String>>
String
containing the IDs of vendors disabled by the user.userStatus.purposes?.global?.enabled
.Future<List<Purpose>>
Purpose
containing the purposes enabled by the user.userStatus.purposes?.global?.enabled
.Future<List<String>>
String
containing the IDs of purposes enabled by the user.userStatus.vendors?.consent?.enabled
.Future<List<Vendor>>
Vendor
containing the vendors enabled by the user.userStatus.vendors?.consent?.enabled
.Future<List<String>>
String
containing the IDs of vendors enabled by the user.evaluateJavaScript
.Future<String>
getQueryStringForWebView
on iOS platform will return an empty String.Future<String>
didomiConfig.user.externalConsent.value=...
. It can be appended to your URL after a ?
or a &
if your URL already contains a query string.String
Future<Purpose?>
Purpose
with ID purposeId
found in the array of required purposes, or null
.Future<List<Purpose>>
Purpose
containing the required purposes.Future<List<String>>
String
containing the IDs of required purposes.Future<List<Vendor>>
Vendor
containing the required vendors.Future<List<String>>
String
containing the IDs of required vendors.texts
property specified in the didomi_config.json
file as described here https://developers.didomi.io/cmp/mobile-sdk/consent-notice/customize-the-theme#translatable-texts-for-custom-notices.Future<Map<String, String>>
didomi_config.json
file, which can be either local or remote, or a file that is bundled within the SDK.didomi_config.json
(either local or remote).didomi_config.json
(either local or remote).didomi_config.json
file (locally or remotely) in 3 different ways:userStatus.purposes?.consent?.enabled
or userStatus.purposes?.consent?.disabled
.ConsentStatus
that indicates if the user has given consent or not to the specific purpose.unknown
is returned if the consent status is not known yet. From a GDPR perspective, you'll want to treat unknown
as disable
(ie no consent given) but it is helpful to know that the user has not interacted with the consent UI yet so that you can subscribe to events and wait for consent information to be collected.enable
.userStatus.vendors?.consent?.enabled
or userStatus.vendors?.consent?.disabled
.getUserConsentStatusForVendorAndRequiredPurposes
does all the required checks for you so it might be a better choice.c:
.ConsentStatus
that indicates if the user has given consent or not to the specific vendor.unknown
as disable
(ie no consent given) but it is helpful to know that the user has not interacted with the consent UI yet so that you can subscribe to events and wait for consent information to be collected.enable
.userStatus.vendors?.globalConsent?.enabled
or userStatus.vendors?.globalConsent?.disabled
.c:
.ConsentStatus
that indicates if the user has given consent or not to the specific vendor and all the purposes that require consent for that vendor.unknown
is returned if the consent status is not known yet. From a GDPR perspective, you'll want to treat unknown
as disable
(ie no consent given) but it is helpful to know that the user has not interacted with the consent UI yet so that you can subscribe to events and wait for consent information to be collected.enable
.userStatus.purposes?.legitimateInterest?.enabled
or userStatus.purposes?.legitimateInterest?.getDisabled
.ConsentStatus
that indicates if the user has allowed legitimate interest data processing to the specific purpose.unknown
is returned if the legitimate interest status is not known yet. From a GDPR perspective, you'll want to treat unknown
as disable
(ie no legitimate interest status given) but it is helpful to know that the user has not interacted with the legitimate interest UI yet so that you can subscribe to events and wait for legitimate interest information to be collected.userStatus.vendors?.legitimateInterest?.enabled
or userStatus.vendors?.legitimateInterest?.getDisabled
.getUserLegitimateInterestStatusForVendorAndRequiredPurposes
does all the required checks for you so it might be a better choice.c:
.ConsentStatus
that indicates if the user has allowed legitimate interest data processing for the specific vendor.unknown
is returned if the legitimate interest status is not known yet. From a GDPR perspective, you'll want to treat unknown
as disable
(ie no consent given) but it is helpful to know that the user has not interacted with the legitimate interest UI yet so that you can subscribe to events and wait for legitimate interest information to be collected.userStatus.vendors?.globalLegitimateInterest?.enabled
or userStatus.vendors?.globalLegitimateInterest?.disabled
.c:
.ConsentStatus
that indicates if the user has allowed legitimate interest data processing to the specific vendor and all the purposes that require legitimate interest for that vendor.unknown
is returned if the legitimate interest status is not known yet. From a GDPR perspective, you'll want to treat unknown
as disable
(ie no legitimate interest given) but it is helpful to know that the user has not interacted with the legitimate interest UI yet so that you can subscribe to events and wait for legitimate interest information to be collected.onReady
method.UserStatus
object describing all the available and computed user information. userStatus.vendors?.global?.enabled
or userStatus.vendors?.global?.disabled
.c:
.ConsentStatus
that indicates if the user has allowed both consent and legitimate interest data processing to the specific vendor. disable
will be returned. If both are allowed by the user, the function will return enable
.String
Future<Vendor?>
Vendor
with ID vendorId
found in the array of required vendors, or null
.assets/
folder. Defaults to didomi_config.json
if null.assets/didomi_config.json
. If there is no Internet connection available and no previously cached file, the local file will be used as fallback.null
.false
(loading remote config).false
to use a remote consent notice configuration loaded from the Didomi Console.true
to disable loading configurations from the Didomi Console."es"
, "fr"
, "en-US"
, "zh-HK"
, etc.