Authenticated Consent Overview

Authenticated consent allows your organization to share an end-user's consent preferences across their different authenticated (i.e. logged-in) devices and deliver an improved end-user experience on your platform (since the end-user does not have to re-consent for each device). In this article, we provide an overview of how Sourcepoint retains an end-user's consent preferences and pushes this preference to the end-user's other authenticated devices.

Authenticated consent utilizes a consent identifier to link an end-user's consent preferences to an authenticated (i.e. logged-in) user profile. Using the consent identifier, Sourcepoint will persist the consent preferences for the end-user in other properties in your configuration.

The consent identifier is passed into your Sourcepoint account via an authId implemented on a page or mobile app. Typically, this consent identifier is a username, userID, or any other unique key that your organization uses to identify a specific user.

If your organization uses email address as a unique key for an end-user, you will want to use a hashed email to protect the end-user's personal information.

In the diagram below, we illustrate the data flow between an authenticated end-user interacting with your properties across three devices.

When your consent management portal (CMP) is called on one your properties, Sourcepoint will check whether the authId (consent identifier) has an associated consent preference.

authId has consent preferences

authId does not have consent preferences

Your CMP will not ask for the end-user's consent preferences.

Sourcepoint will load your pre-determined scenario and save any consent preferences to the authId in our database for the next time the authIdis called