Loading
Mail Delivery Issue Impacting Email to Salesforce UsersRead More
Data Protection and Privacy
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Set Up Data 360 for Preference Manager

            You are here:

            1. Salesforce Help
            2. Docs
            3. Data Protection and Privacy

            Set Up Data 360 for Preference Manager

            Stream customer consent information from Data 360 to use in Preference Manager and to ingest customer consent information from preference forms into your Salesforce org.

            Required Editions

            Available in: Lightning Experience and Salesforce Classic in Developer, Enterprise, Performance, and Unlimited Editions. Requires Privacy Center and Data 360 licenses.
            User Permissions Needed
            To use Preference Manager: Manage Preference Manager
            1. Enable Preference Manager permissions.
            2. Turn on Data 360.
            3. Connect to a Salesforce org.
            4. Connect Data 360 to your preference form.
              Ingest into Data 360 the information that your customers add to your preference forms by creating a new Ingestion API connector, a new data stream, and by mapping the fields that you want to ingest to a data model object.
              1. Set up Ingestion API Connector using pvcy_data_cloud_consent as the API source name.
                This name is required. For the schema file that you upload, create a .yaml file with these specifications.
              2. Create an Ingestion API data stream with these settings. In the Ingestion API dropdown list, select pvcy_data_cloud_consent. For Primary Key, select ConsentId. For Category, select Other. Leave Record Modified Field blank.
              3. Map the fields for the pvc_data_cloud_consent-pvc_comm_sub_consent data stream.
            5. Enable object and field permissions for Salesforce CRM connections.
              In System Permissions, select Access Activities.
              Review and update the Data 360 Salesforce Connector permission settings to make sure that all necessary objects are available during data stream mapping. At minimum, enable the Read and View All Records permissions for these objects, and enable the Read Access permission for their fields.
              • Communication Subscriptions
              • Communication Subscription Channel Types
              • Engagement Channel Types
              • Communication Subscription Consent
              Note
              Note To use Data Governance features, grant permissions to the listed objects according to Assign Data Access. If you have more than one data space, you must grant access to objects in each data space. Object names in non default data spaces follow the convention of <DataSpace Prefix>_<Object Name>.
            6. Create these data streams to enable the flow of data from Salesforce CRM into Data 360.

              In addition to these required data streams, you might have other objects that you need to ingest. For example, if you’re using preference forms as part of consent segmentation, you might also need a data stream for the Business Brand object.

              1. Create a data stream for the Communication Subscriptions object.
              2. Create a data stream for the Communication Subscription Channel Types object.
              3. Create a data stream for the Engagement Channel Types object.
              4. Create a data stream for the Communication Subscription Consent object.

            Specifications for the Ingestion API Connector Schema File

            Use these specifications for the .yaml schema file that you upload to the Ingestion API Connector.

            File Format OpenAPI (OAS)
            File Name pvcy_data_cloud_consent.yaml
            File content 
            openapi: 3.0.3
components:
  schemas:
    pvcy_comm_sub_consent:
      type: object
      properties:
        ConsentId:
          type: string
        ConsentStatus:
          type: string
        ContactPointValue:
          type: string
        CommunicationSubscriptionChannelType:
          type: string
             
            Loading
            Salesforce Help | Article