Actions75
- Compliance Report Actions
- Consent And Preference Actions
- Data Manager Actions
- Add Preference Into Your Configuration Tree
- Add Purpose Into Your Configuration Tree
- Create Preference
- Create Purpose
- Delete Preference
- Delete Purpose
- Delete Selected Preference
- Delete Selected Purpose
- Get Available Regulations and Related Information
- Get Configuration Tree
- Get Preference
- Get Purpose
- Get Vendor
- List Preferences
- List Purposes
- List User Rights
- List Vendors
- Update Preference
- Update Purpose
- Privacy Request Actions
- Widget Actions
- Create Authentication Provider
- Create Consent Notice
- Create Widget
- Delete Widget
- Get Archived Widget
- Get Current Draft Configuration For Notice
- Get Custom Theme
- Get Deployment
- Get Entity
- Get Widget
- List Archived Widget
- List Custom Themes
- List Deployments
- List Entities
- List Widgets
- Publish Current Draft Configuration For Notice
- Publish Widget
- Set Default Authentication Provider
- Update Component
- Update Current Draft Configuration For Notice
- Update Custom Theme
- Update Entity
- Update Multiple Components
- Update Multiple Entities
- Update Widget
Data Manager → Create Preference
AI-generatedOverview
This node operation creates a new preference in the Didomi Data Manager. It is useful for managing user data preferences centrally, allowing organizations to define and store user preferences related to data privacy and compliance. For example, it can be used to add a new user preference for data handling or consent management within an organization's privacy framework.
Use Case Examples
- Creating a new user preference to comply with GDPR regulations.
- Adding a preference to track user consent for marketing communications.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional parameters to customize the API request, such as filtering or pagination options. |
Output
JSON
json- The JSON response from the Didomi API representing the created preference or related data.
Dependencies
- Didomi API with API Key and Secret credentials
Troubleshooting
- Missing API Key or API Secret will cause authentication failure; ensure credentials are set correctly.
- Required parameters such as Configuration Tree ID must be provided; missing these will throw errors.
- API errors from Didomi are wrapped and presented with error messages; check the error details for troubleshooting.