- Analytics Admin Guide
- Analytics Release Notes
- Analytics Admin overview
- System requirements
- Admin Tools
- Admin Tools
- Billing
- Bot removal
- Code Manager
- Conversion variables
- Currency codes
- Custom report descriptions
- Customize calendar
- Data Sources
- Default metrics
- Exclude by IP address
- Finding methods
- General Account settings
- Internal URL Filters
- Logs
- Marketing Channels
- Menu customizing
- Metric visibility
- App management
- Paid search detection
- Publishing lists
- Publishing Widget
- Preferences manager
- Privacy settings
- Privacy reporting
- Processing rules
- Processing rules overview
- Processing rules configuration
- Dimensions available to processing rules
- Processing rules examples
- Examples of processing rules
- Populate a campaign ID from a query string parameter
- Set the product view event from the product overview page
- Add a subcategory by concatenating the category and page name
- Determine a path by copying an eVar value to a prop
- Clean up values in a report
- Populate internal search terms using a query string parameter
- Copy a context data variable to an eVar
- Set an event using a context data variable
- Remove an event from a hit
- Processing rules tips and tricks
- Real-time reports
- Scheduled reports queue
- Server-side forwarding
- Simplified reports menu
- Social management
- Success events
- Timestamps optional
- Traffic variables
- Unique Visitor variable
- Video management
- Analytics in the Adobe Admin Console
- Company Settings
- Manage report suites
- User and Product Management (Legacy)
- Data Governance
- Adobe Analytics and GDPR
- Adobe Analytics and CCPA
- CNIL Consent Exemption
- Frequently asked questions
- Adobe Analytics Data Privacy workflow
- View/manage report suite’s Data Governance settings
- Label report suite data
- Submit access and delete requests
- Data Privacy labels for Analytics variables
- Namespaces
- ID expansion
- Labeling best practices
- Labeling example
- Data Privacy and Data Connectors (Genesis)
- Data Privacy terminology
- Privacy Reporting Variables
- Server Call Usage
- Traffic Management
- Admin API
Privacy Reporting Variables
To provide additional assistance in managing privacy data, a set of reserved variables are available to be used in conjunction with specific context data variables.
These privacy reporting variables provide an easy-to-use framework for capturing the privacy status on each analytics hit.
Variables
-
Consent Management Opt-Out
- Reserved Variable: List Prop
- Type: Comma-delimited string
- Contains:
contextData.['cm.ssf']=1displayed as SSFcontextData.['opt.dmp']=Ndisplayed as DMPcontextData.['opt.sell']=Ndisplayed as SELL
-
Consent Management Opt-In
- Reserved Variable: List Prop
- Type: Comma-delimited string
- Contains:
contextData.['opt.dmp']=Ydisplayed as DMPcontextData.['opt.sell']=Ydisplayed as SELL
Reporting
You can enable the Privacy Reporting Variables through a new Privacy setting available within the Analytics Admin Console.
Each report suite can be configured as follows:
-
In Reports & Analytics click Admin > Report Suites.
-
Select the report suite(s) where you are collecting media data and click Edit Settings > Privacy Management.
-
Click the Enable Data Privacy Reports button.
NOTEOnce enabled these variables cannot be turned off.
-
Once enabled, you will see a confirmation message.
-
The reserved variables are now available for analysis in Reports & Analytics and Workspace. See Consent Management Opt-Out and Consent Management Opt-In.
Implementation
Three context data variables have been pre-defined to work with the privacy reporting management reserved variables. It is up to each implementation engineer to determine how to manage and persist the setting of these variables.
See Context Data Variables for general guidance on implementing context data variables.
SSF
- Context Data:
contextData.['cm.ssf'] - Accepted Values:
- 1 - When sending the value “1”, this indicates that Server Side Forwarding is in an opt-out state. The value “1” paired with this variable will block the sharing of this hit with Adobe Audience Manager. See AAM ePrivacy Compliance.
- 0 - Optional. Use the value “0” for customers who consented to targeted marketing. Not setting the variable will also produce the same results.
DMP
- Context Data:
contextData.['opt.dmp'] - Accepted Values:
- N – When sending the value “N”, this indicates that the consumer is opting out of sharing to data management platforms. Note: As of January 15, 2020, setting this variable to “N” blocks server-side sharing of this hit to AAM.
- Y - When sending the value “Y”, this indicates that the consumer is opting in to sharing to data management platforms.
SELL
- Context Data:
contextData.['opt.sell'] - Accepted Values:
- N - When sending the value “N”, this indicates that the consumer is opting out of the sharing or selling of the data to third parties.
- Y - When sending the value “Y”, this indicates that the consumer is opting in to the sharing or selling of the data to third parties.
Business.Adobe.com resources
Resources
Adobe Account
