Authenticated Consent on Web Properties

This is a page on how to link a user's profile using Sourcepoint's Identity feature for authenticated consent on desktop and mobile-web sites.


Sourcepoint enables its partners to send Sourcepoint an identifier that can be tied to an authenticated or logged-in user profile. This allows partners to provide the same consent for user across different devices as long as they are logged in to those devices. There are two simple ways in which this can be accomplished.

Sourcepoint provides a function window._sp_.​​(authId)​ with authId is a unique identifier string passed to the function. For example, if a logged-in user's unique ID is 1234ABCD, then the function call below would link the user's Sourcepoint consentUUID to ID 1234ABCD.


Sourcepoint partners can also choose to set the authenticated ID directly. To accomplish this, the partner should set a first party cookie value​ with key ‘authId’, and the value of the unique-user identifier. The format of this value does not necessarily matter as long as the value uniquely identifies the logged in user. To ensure that the link to the logged-in user is made prior to Sourcepoint's logic to determine whether or not to show a message runs, the cookie needs to be set on the page ahead of the Sourcepoint script. Below is an example of the cookie being set directly using jQuery for the site

$.cookie('authId', '1234ABCD', { path: '/', domain: '' });

To return to using an anonymous consent profile after the user has logged out, partners can call the function window._sp_.cmp.delete_consent_cookies()​ exposed through the Sourcepoint script. This function will delete the ‘resolvedId’ cookie which is the cookie is used to determine if linking has happened. An example of it being used is below.

function logOut(){
//Site logic to log the user out

If you have any additional questions about using Sourcepoint's Identity solution for authenticated consent, please contact your Sourcepoint Account Manager.