Setting up and using a clean room identity boost involves steps for both the provider
and the consumer. The provider creates a package and sets up their Snowflake environment. The
consumer installs the package, creates a collaboration, and maps their data. After the provider
accepts the invitation and runs the enrichment job, Data 360 automatically
refreshes the enriched data in the consumer's org.
You can’t receive or accept collaboration invitations in Developer Edition.
User Permissions Needed
To set up a clean room identity boost:
One of these permission sets:
Data Cloud Architect
Data Cloud Activation Manager
Data Cloud Activation Specialist
Important Identity boost shares personally identifiable information (PII) in
unhashed form with the identity provider. Before mapping your data, make sure that you have all
required consumer consents and that you comply with applicable data usage agreements and privacy
regulations. Data processing can occur outside your Salesforce region.
Provider: Create a clean room package that includes the identity boost use case, and
publish it to AppExchange.
Creating an identity boost package requires a Developer Edition packaging org. Install
the package, create the collaboration, and accept the invitation in an Enterprise Edition home
org. See Create a Clean Room Package.
Consumer: In an Enterprise Edition home org, install the package from AppExchange.
Consumer and provider: Create mapped templates so that each party maps data to the
required collaboration fields.
The consumer maps Data 360 DMO fields to the provider's required
attributes. Review the data-sharing disclaimer carefully before proceeding because this use
case shares PII with the provider in unhashed form. See Map Data for a Clean Room Use Case.
Consumer: Create a collaboration using the identity boost use case and send an invitation
to the provider.
Provider: In an Enterprise Edition home org, in the Invitation Acceptance wizard, set up
the Snowflake environment and establish the trust relationship with Snowflake.
After the provider accepts, Data 360 creates a clean room-aware
Snowflake data share target and shares the consumer's mapped DMO data to the provider's
Snowflake environment.
Provider: Run the enrichment job on the shared consumer data, then write enriched output
tables to the consumer's Snowflake schema.
Data 360 automatically refreshes the enriched data in the
consumer org. Data 360 reads enriched output tables from the provider's
Snowflake schema through a (Bring Your Own Lake) BYOL connection, creates Data Lake Objects
(DLOs) and enriched DMOs in the consumer org, and sets the collaboration status to
Active.
Consumer: After refresh completes, use the enriched DMOs in the Data 360
org for activation use cases.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.