PreferenceLink
PreferenceLink allows you to record consent transactions performed by your users (here called data subjects) and store all the information necessary as burden of proof. These consent transactions result in a series of values saved about your subjects/users, which you can later recall via a dedicated endpoint. These values are determined by the fields in the data schema that each consent section has modified and could include the user’s preferences (newsletter, profiling, etc.)
Click here to view our developer-focused documentation, which is designed to give your organization a clear and quick overview of how to integrate with PreferenceLink.
The developer documentation focuses on scenarios for integration and flow of events. We recommend familiarizing yourself with all of the content in the developer portal, as it's a great complement to our API documentation.
Here is a sampling of what is available in the developer documentation:
Getting Started: Onboarding, Glossary
PreferenceLink 101: Data Schemas, Date Fields, Vendors
Guides: Working with PreferenceLink, Flow Samples, Integration Methods
API Reference: Detailing how to interact with the PreferenceLink API