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 → Get Preference
AI-generatedOverview
This node operation retrieves a specific user preference from the Didomi Data Manager API. It is useful for scenarios where you need to fetch detailed information about a particular preference stored in the Didomi system, such as user consent preferences or privacy settings. For example, it can be used to get the details of a preference by its ID to display or process it further in an automation workflow.
Use Case Examples
- Fetch a user preference by its ID to check consent status before processing user data.
- Retrieve preference details to audit or update user privacy settings in compliance workflows.
Properties
| Name | Meaning |
|---|---|
| Preference ID | The unique identifier of the preference to retrieve. |
| Query Parameters | Optional parameters to filter or modify the request, such as limiting results or specifying organization user ID. |
Output
JSON
preference- The retrieved preference object with its details.
Dependencies
- Didomi API with API Key and Secret for authentication
Troubleshooting
- Missing or invalid Preference ID will cause an error indicating the ID is required.
- Failure to authenticate with the Didomi API due to missing or incorrect API key or secret will result in an authentication error.
- API request failures or network issues will throw errors with messages from the Didomi API, which should be checked for details.
Links
- Didomi API - Get Preference - Official API documentation for retrieving a preference from Didomi Data Manager.