According to the comScore web site, publishers can implement the “cs_ucfr” parameter to pass opt-out information to Comscore. The “cs_ucfr” parameter allows Clients to communicate a consent value to Comscore via the Comscore tag code embedded on a Client website. A value of “1” for this parameter designates that the consumer has explicitly consented to the collection and use of the data, and a value of “0” designates a lack of consent. Comscore’s use of information will be governed by this value.
To facilitate this in the Sourcepoint platform, web site can use the custom consent and reject actions to store whether or not a client has consented to comScore's use of their data or not. Perhaps the easiest way to accomplish this is to set a cookie to manage the site visitor's current consent status.
The screenshot below assumes the site can use jquery to set a cookie, but any cookie setting function will work. In this example, if the site visitor executes a do not sell signal then a cookie value called _sp_comscore is created with a value of "0".
The site can then look for this cookie value and determine how to set the comScore “cs_ucfr" flag. If the cookie value exists and is "0", then the flag would be set to "0". If the cookie value does not exist, then the flag is set to "1".
To communicate certain values for a user, comScore uses labels. To learn about setting up labels for comScore, please visit the comScore SDK documentation. To opt users out of the use of their data comScore has created a specific label called cs_ucfr. A value of “1” for this parameter designates that the consumer has explicitly consented to the collection and use of the data, and a value of “0” designates a lack of consent. Comscore’s use of information will be governed by this value.
Developers can query the Sourcepoint consent SDK to understand the user's current consent status and then set the appropriate label value for the cs_ucfr label.