NOTE: This documentation references many concepts addressed in the glossary of terms. Please visit this page before you continue.
- Click Manage
- Click Capture
- Click Consumer Rights
View Consent Reports
Within the admin console, you can check the population sizes for each consent flag. While this report does not provide consent settings for every user individually, the aggregate report helps you understand how many users within your account consented to which flags.
Follow these steps to access the report.
- Click Manage
- Click Capture
- Click Consent
The consent processing summary shows you how many users you collected a consent signal from, and how many users you do not have a consent setting for.
The consent population distribution shows the count of users that gave consent for each consent category.
For each consent collection type, the total number is the same; it's the total number of records.
Total number of records for Data Collection is 5,000; 100%
45 (non-consent) + 4,955 (consent) = 5,000 Total Records; 99.1% consent
If consent is deselected, the total # of records is 50; 100% non-consent.
45 (non-consent) + 0 (consent) = 50 Total Records
If non-consent is deselected, the total # of records is 4,955; 100% consent.
0 (non-consent) + 4,955 (consent) = 4,955 Total Records
From the UI, you can see what organization links exist for your account. If your organization is linked, you see all pertinent information about the current links defined in the configuration screen.
Setting Policy Regime Association Method & Defaults
We support two policy regime handling options:
- One setting for the entire organization (when Organization level policy regime is selected). For organizations that capture consent (for e.g. through a popup) globally, this option delivers the ability to specify a Custom Policy Regime.
- Location-based policy regime (when User level policy regime is selected). In this case, we automatically select the policy regime settings based on the Geo and we do not allow overriding these regional policy regimes with a Custom Policy Regime. However we do support a custom policy regime for the users that we cannot determine location for, so our customers can choose to be aggressive or conservative as best meets their needs.
From the consent management section of the Audience Studio UI:
- Select Edit Configuration
- Select your desired policy regime association method
- Select your default policy regime
- Click Save
Defining Consent Defaults for Marketing Cloud
Marketing Cloud email activity (opens and clicks) can be used in Audience Studio segmentation. There are two ways to bring this data into Audience Studio - via an automated data feed that brings server-side data from Marketing Cloud to Audience Studio or via pixels that fire within emails that are opened or clicked in compatible environments.
Audience Studio customers can specify consent defaults to be applied when a new user is seen from Marketing Cloud. Consent defaults are applied to users seen on automated data feeds and to users seen via pixel traffic.
To set defaults for new devices seen from Marketing Cloud events:
- From the consent management section of the Audience Studio UI, select Edit Configuration.
- Select your desired consent defaults for each consent flag.
- Click Save.
- Navigate to Marketing Cloud under the Consent Defaults section.
Note that this option will only be available if you have access to the Marketing Cloud connector. Contact the support team to learn more.
These consent flags contain default values based on the global standard policy regime.
- Data Collection = True
- Analytics = True
- Targeting = True
- Cross Device = True
- Data Sharing = False
- Re-identification = False
Custom Consent Options
Before you can set a custom consent option, you need to set the Policy Regime Association to Custom.
Then open the Custom tab in the Consent Defaults section and set specific flags to True (on).
Second Party Consent Options
You also need to provide default settings for Second Party consent events.
These are the same options for each type of consent authorization.
Back-filling Consent for Historical Activity
The backfill option was implemented for a short period when GDPR first came into effect, but it is no longer available, even if you see the Backfill tab within the interface.
Since these settings are no longer available, you can leave them as they appear in your interface.
Defining Consent Resolution Defaults
Because targeting, cross-device, data sharing, and re-identification all require segment processing (analytics), Audience Studio does not support a user consenting to any of these consent categories without also consenting to analytics. In the case where you provide Audience Studio with an affirmative consent for these consent categories but a negative consent for analytics, Audience Studio references a default configuration to resolve the consent conflict.
- True - This option sets all consent flags to true to avoid the conflict.
- False - This option sets all consent flags false to avoid the conflict.
Deleting Erroneous Data Collection
When Salesforce Audience Studio infrastructure is fired via the Control Tag or SDK, then the user consent signals will be checked before any data is sent back into Audience Studio. For example, if the consumer has dissented from data collection, then the Control Tag will not fire pixel.gif for that consumer. There is the possibility that other tags such as ad_impression pixels are firing outside of the Control Tag or SDK. In those instances, the ad_impression.gif will fire and data will be logged in the Audience Studio, however that data will not be used if the consumer has dissented from data collection.
If you would like to ensure that any rogue data that may be logged into Audience Studio gets deleted, please check the second toggle under the Conflict Resolution section of the Consumer Rights Management Configuration UI. When checked, all raw data will be deleted on a daily bases for consumers who have dissented to data collection.