In this article, we will cover how to integrate Sourcepoint's CMP into Comscore using their
cs_ucfr parameter. The integration will pass end-user's opt-out information to Comscore.
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. Comscore’s use of information will be governed by this value.
||Designates that the end-user has explicitly consented to the collection and use of their data.|
||Designates that there is a lack of consent to the collection and use of an end-user's data.|
Web properties can leverage the custom consent and reject actions to store whether or not a client has consented to comScore's use of their data.
Note: Sourcepoint recommends that you set a cookie to manage your web property's end-user current consent status. While we utilize a jquery to set a cookie in the example below, any cookie setting function can be utilized.
In the example below, if an end-user on the property executes a "Do Not Sell" signal then a cookie value called
_sp_comscore is created with a value of
The web property can 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
iOS and Android opt-out
To communicate certain values for an end-user on mobile apps, comScore uses labels. To learn about setting up labels for comScore, please visit the comScore SDK documentation.
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.