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 → Delete Preference
AI-generatedOverview
This node operation deletes a specific user preference in the Didomi Data Manager. It is useful for managing user data preferences by removing outdated or unwanted preferences from the system. For example, if a user revokes consent for a particular data processing preference, this operation can be used to delete that preference from the configuration.
Use Case Examples
- Deleting a user preference by specifying its Preference ID to ensure compliance with user data management policies.
- Removing a preference that is no longer relevant or valid in the data management system.
Properties
| Name | Meaning |
|---|---|
| Preference ID | The unique identifier of the preference to be deleted. |
| Query Parameters | Optional parameters to refine the request, such as filtering or pagination options. |
Output
JSON
Status Code- HTTP status code indicating the result of the delete operation, e.g., '204 No Content' for successful deletion.
Dependencies
- Didomi API with API Key and Secret for authentication
Troubleshooting
- Missing or empty Preference ID will cause an error: 'Preference ID is required'. Ensure the Preference ID is provided before executing the node.
- Authentication errors if API Key or Secret are missing or invalid. Verify credentials are correctly set.
- API request failures due to network issues or incorrect endpoint URL. Check network connectivity and parameter correctness.
- Unexpected response format errors if the API response is not JSON or empty. Handle such cases gracefully.
Links
- Didomi API - Delete Preference - Official API documentation for deleting a preference in Didomi Data Manager.