Sourcepoint Help Center
Search…
1.0.0
Introducing Sourcepoint
Get Started
Terms & Definitions
Users and User Rights
Browser and Device Support
Implementation
General
Web Implementation
Mobile implementation
AMP Implementation
OTT Implementations
API
General
GDPR TCF v2 API
GDPR non-TCF API
CCPA API
Consent Management Platform (CMP)
Consent Management Platform (CMP) Overview
Properties and Property Groups
Authenticated Consent
Authenticated Consent Overview
Enable Authenticated Consent
Vendor Lists
Privacy Manager
First Layer Message
Native OTT Message
iOS Tracking Message
Scenarios
Partition Sets
Campaigns
CMP Reports
Privacy Lens
Privacy Lens Overview
Standards
Property Sets
Scoring Results
Anti-Adblock Messaging
Anti-Adblock Features
Anti-Adblock Message
Anti-Adblock Reports
Anti-Adblock FAQs
Release Notes
CMP Release Notes
SDK Release Notes
Powered By GitBook
Enable Authenticated Consent
Authenticated consent allows your organization to tie an end-users consent preferences to a unique end-user identifier that will persist across authenticated (i.e. logged-in) devices. In this article, we will cover how to enable authenticated consent for web properties.
Please follow the links before for more information on how to implement authenticated consent for iOS and Android:

Requirements

The following requirements must be met In order to successfully utilize authenticated consent between web and app properties:
  • Properties using authenticated consent must use the same vendor list
  • The consent scope for the vendor list should be set to Shared site (see below)
To implement authenticated consent on a web page, you can write a cookie directly on the page to pass the consent identifier to Sourcepoint.
1
document.cookie = "authId=123123123";
Copied!
​
Previous
Authenticated Consent Overview
Next - Consent Management Platform (CMP)
Vendor Lists
Last modified 6mo ago
Export as PDF
Copy link
Contents
Requirements
Implement authenticated consent on web properties