Salesforce Data Cloud Setup Guide

In Data Cloud, select CDP Setup from the Setup gear icon.

Select Ingestion API from the left navigation underCONFIGURATION.

Click New, enter a name for the API source (for example, 'FINS_Banking-Data-Connector'), then click Save.

On the details page for the new connector, you must upload a schema file in OpenAPI (OAS) format with a .yaml file extension. The schema file describes how data transferred via the API is structured.
Note: Ingestion API schemas have set requirements - review the schema requirements below if having issues uploading the schema.

Click Upload Schema and navigate to the location of the file you want to use. Select the file and click Open. For the Optimize Customer Experiences with CDP use case, the schema file mule-cdp-connector-schema.yaml is available under src/test/resources/cdp-schema of the FINS Salesforce CDP System API implementation template.

Preview all the detected objects and their attributes in your schema.

Click Save.

From the Setup app, navigate to the Apps->App Manager page.

Click the New Connected App button in the top right.

Enter a connected app name (for example, 'FINS Salesforce CDP System API').

Enter a valid contact email address.

Select the Enable OAuth Settings option and enter 'http://localhost' as the Callback URL.

Under the 'Selected OAuth Scopes' section, add the following scopes from the Available OAuth Scopes list:

Click Save and then Done to create the connected app.

In Data Cloud, navigate to Data Streams and click New.

Select the Salesforce CRM data source and click Next.

To create your data stream, select a Salesforce org (if you have only one Salesforce org connected to Data Cloud, it will be selected by default.

Click the All Objects button, select the target object to sync (for example, Account), and click Next.

For Category, select the Profile option.

Review the fields to include in your data stream. By default, all fields are preselected with the total number of fields available for the object is shown in parentheses.

Click Next and fill in the deployment details:

Click Deploy to create the Salesforce CRM data stream.

Click the data stream from the 'Data Streams' list view to bring up the details page.

Select the New Formula Field action from the top right action list. You may need to click the 'more' down arrow to find the action.

Enter the following values:

Use the Test button to validate the formula output for both empty and non-empty values.

Click Save to save the new formula field.

Login to the Salesforce org containing the objects and fields you want to ingest into Data Cloud

From the Setup page, enter 'Permission' in the Quick Find box and select Permission Sets.

Select the Customer Data Platform Salesforce Connector Integration permission set.
Note: The permission set is available only after you connect your CRM org to Data Cloud.

From Apps, select Object Settings.

Select the object to ingest into Data Cloud (for example, Account).

To change object permissions, click Edit.

Enable Read and View All permissions for the object and Read Access for each field. Use the table above for reference.

Click Save.

In Data Cloud, select Data Streams and click New.

Select Ingestion API and click Next.

Select the connector you configured earlier from the dropdown.

Select all the objects found in the schema as per the above table and click Next.

In the 'New Data Stream' dialog, use the details in above table to configure each object by selecting the object shown under Objects to Configure:

Click Save.

Once the dialog has closed, click Next.

On the final summary screen, review the list of data streams that Data Cloud created and click Deploy.

Click the data stream from the 'Data Streams' list view to bring up the details page.

Select the New Formula Field action from the top right action list. You may need to click the 'more' down arrow to find the action.

Enter the following values:

Use the Test button to validate the formula output for both empty and non-empty values.

Click Save to save the new formula field.

Click into the target data stream from the Data Streams view.

On the Data Stream detail page, click Start Data Mapping.

Ensure Visual View is selected for mapping your data.

Click Select Objects and select the Custom Data Model tab.

If the DMO required for the data stream already exists:

If the required DMO does not exist:

Click Save & Close to return to the stream detail page.

Click the Review Mappings link at the bottom of the 'Data Mapping' section.

Click the pencil icon button beside the 'Data Model entities' group on the right.

Under the Standard Data Model tab, select the objects that need to be mapped (as per the table above) by clicking the plus sign button.

Click Done to save the object selections.

Continue to the Standard object mappings section below.

Click into the target data stream from the Data Streams view.

On the Data Stream detail page, click Start Data Mapping.

Ensure Visual View is selected for mapping your data.

Click Select Objects and select the `Standard Data Model Objects that need to be mapped (as per the table above) by clicking the plus sign button.

Click Done to save the object selections and continue to the Standard object mappings section below.

Click into the target data stream from the Data Streams view.

Click the Review Mappings link at the bottom of the 'Data Mapping' section.

On the Data Streams mapping canvas, you can see all fields in both your DSO and target DMO(s).

Map all fields from the DSO to the target DMO(s) as per the mapping tables below. To map one field to another, first expand the Unmapped section of the target DMO on the right. Click on a field in the DSO on the left and connect it to the DMO on the right by clicking on the target field. For example, click on the PartyType field in the DSO on the left and then click in on the Party Identification Type field in the Party Identification DMO on the right. When you complete the mapping for a DMO, collapse the Unmappedsection to save space.

Once the mappings have been completed for all DMOs, click the Save button to save the changes. If you get an error related to primary keys, double-check your mappings. Ignore 'Identity Resolution' warnings for now.

For each DMO mapped, click on the 'Link' icon to bring up the Object relationships dialog for the DMO and ensure the relationships are seen as per the Data Relationships between DMOs table below. If not, click the New button to add the required relationship.

Click Save and Close to record the mapping and relationship changes.

Select Activation Targets from the top navigation menu.

Click the New button to create a new entry.

Select the aws | S3 external platform and click Next.

Enter an easy to recognize but unique name (for example, 'Data Cloud Segmentation Results Bucket') and click Next.

Specify the S3 bucket name and parent folder provided by your admin for your activation target.

Enter the S3 access key and secret key for the bucket. The S3 credentials provided must have the following permissions: s3:PutObject, s3:GetObject, s3:ListBucket, s3:DeleteObject, s3:GetBucketLocation.
Note: To delete S3 access or secret keys, first delete the activation target.

Select an export file format (for example, JSON).

Click Save to create the Activation Target.

Login to aws and select the S3 service.

Navigate to the bucket you configured in the Activation Target.

Navigate to /Salesforce_c360_Segments to view generated segments.

Select Activation Targets from the top navigation menu.

Click the New button to create a new entry.

Select Marketing Cloud as the target and click Next.

Enter an easy to recognize but unique name (for example, 'Data Cloud Segmentation Results MC').
IMPORTANT: Marketing Cloud activation target names cannot be more than 128 characters, start with an underscore, be all numbers, or include these characters: @ % ^ = < ' * + # $ / \ ! ? ( ) { } [ ] , . (space)

Click Next.

To add or remove business units (BUs) to receive the published segments, click the arrows between the two columns. When an activation target has multiple BUs, the activation filters the contacts by the BUs. The segment activates as a Shared Data Extension (SDE) and not as a Data Extension (DE) to Marketing Cloud. If an activation target has multiple business units configured, modify the activation target configuration to include one business unit only.

Save your changes.

Select Activation Targets from the top navigation menu.

Click the New button to create a new entry.

Select the Segment (for example, Cross-selling money market account or Upselling mortgage account).

Select one of the Activation Targets created earlier (AWS S3 or Marketing Cloud).

Select Account from the 'Activation Membership' dropdown. Click Next.

Select your contact points.
Note: Selecting contact points is optional for S3 activations. When contact points are mapped, select an existing path or click Edit.

To activate additional attributes, click Add Attributes.

Drag the attributes Account Id and Account Name to the canvas. Click Save.

From Unified Individual <ruleset>, select the Global Party field and select the path that relates from Account. Click Next.

Enter a name and description for your activation.
IMPORTANT: You cannot include the following characters in the name field: + ! @ # $ % ^ * ( ) = { } [ ] \ . < > / " : ? | , _ &

Click Save.