Alternatively the CMP can be developed to utilize CMP as an API service on which the TCF complexity etc. is implemented on the server-side and the UI can be rely on components already available within the application framework, only the actions are sending API requests to consent/deny all/set of purposes, features etc. and TCF compliant consent string is returned on each action reflecting the changes.