Didomi.unitypackageinto your project:
initializemethod and pass your API key:
Didomiobject until it is actually ready to handle your requests. Use the
OnReadyevent in C# to register a listener for the ready event.
@SerializedNameto indicate the name of the JSON properties and ensure that they are correctly encoded into JSON.
user.tokenproperties have a lot of data.
user.tokenproperties are empty.
SetupUIfunction of the SDK in your context where the application starts:
SetupUIfunction is called on every context that the user can launch the app on. This will ensure that consent is always collected as needed and there is no path where the user can launch the app without consent being collected. If
SetupUIis missing in some entry points, you will see lower consent rates as users will be using the app without giving consent.
falsewhen calling the initialize method as shown below.
didomi_config.jsonconfiguration file as a fallback. See the Local option below for more information on how to configure the SDK through a local configuration file.
didomi_config.jsonfile that must be placed in the
Assets/DidomiConfigfolder of your Unity project.
DidomiConfigfolder under the
Assetsfolder of your Unity Project. Put your
didomi_config.jsonfile in the
DidomiConfigfolder is mandatory for local configuration files as the configuration file must be moved to the correct directories when the Android and iOS projects are being generated. On the post process of the Unity project, the Didomi Plugin moves the files from
assets/folder of the Android apps and to the
Data/Resourcesfolder of iOS apps. For iOS projects, the configuration files will also be added to Copy Bundle Resources.
initializecall to set the
didomi_config.jsonconfiguration file from. That allows you to update the SDK configuration without having to re-publish you mobile application.
didomi_config.json(provided in the app bundle) as a fallback.