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 → Add Preference Into Your Configuration Tree
AI-generatedOverview
This node operation adds a preference into a specified configuration tree within the Didomi platform. It is useful for managing user data preferences centrally by associating preferences with configuration trees, which can represent different user or organizational settings. For example, it can be used to dynamically update user consent preferences in a privacy management system.
Use Case Examples
- Adding a new user preference to a configuration tree to customize consent options.
- Updating configuration trees with new preferences based on regulatory changes or user feedback.
Properties
| Name | Meaning |
|---|---|
| Configuration Tree ID | The unique identifier of the configuration tree where the preference will be added. This is required to specify the target configuration tree. |
| Query Parameters | Optional parameters to customize the API request, such as filtering or pagination options. |
| Request Body | The JSON body of the request containing the preference data to be added into the configuration tree. |
Output
JSON
response- The JSON response from the Didomi API after adding the preference into the configuration tree. It typically contains details of the added preference or confirmation of the operation.
Dependencies
- Requires Didomi API credentials (API Key and API Secret) for authentication.
Troubleshooting
- Missing Configuration Tree ID will cause an error; ensure this ID is provided.
- Missing or invalid API credentials will prevent authentication and cause the node to fail.
- Invalid or malformed JSON in the request body will cause the API call to fail.
- Network or API endpoint issues can cause request failures; verify connectivity and API status.
Links
- Didomi API Documentation - Official documentation for the Didomi API, useful for understanding available endpoints and request/response formats.