---
schema_version: "1"
id: ac7096bb81bae3d4ac6bc367c3f3f70a7fbf3b611f8e4b77c21752b26d2c677b
title: Optimize Customer Experiences Use Case Setup Guide
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/financial-services/latest/sfdc-data-cloud-setup-guide.md
canonical_url: https://docs.mulesoft.com/financial-services/latest/sfdc-data-cloud-setup-guide
source_site: docs.mulesoft.com
content_type: documentation
content_hash: c2508589c97339696d533db0b31e67f3be23da13c8020634a65314a96069677a
description: MuleSoft Documentation Site
release: "1.12"
latest: true
---
---
product: Financial Services
version: 1.12
is-latest-version: true
---

# Optimize Customer Experiences Use Case Setup Guide

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

The
[Optimize Customer Experiences with Data 360](https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/1.12/pages/dcb-oxw/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20Data%20Cloud/)
in MuleSoft Accelerator for Financial Services requires initial configuration in Salesforce
Data 360. Complete the core configuration by following the
[Data 360 learning path](https://help.salesforce.com/s/articleView?id=data.c360_a_customer360_lm.htm&type=5).

After completing the setup, apply the use case-specific guidance on this page. For additional use
case information and the downloadable assets, refer to the use case documentation in Anypoint
Exchange.

## Data Connectors and Sources

Configure Salesforce CRM and Ingestion API connectors to bring CRM and external system data into
Data 360.

- Salesforce CRM serves as the primary source for Financial Services Cloud customer and account
  data.

- Marketing Cloud is the target destination for audience activation outputs.

- The Ingestion API is used for external data sources such as Snowflake, Databricks, and Amazon S3.

The use case expects source data to include globally unique party identifiers for downstream profile
unification.

## Ingestion API Schema Scope

The ingestion schema includes:

- FinancialAccount

- FinancialTransaction

- ExternalFinancialAccount

- WebEngagement

Refer to the
[FINS Salesforce Data 360 System API Implementation Template](https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/)
for the Ingestion API schema file and payload examples.

## Data Streams and Mapping Focus

Create the required data streams, and then map source objects to the target data model to make sure
customer profiles and engagement data are segmented and activated.

- Define the streams for the Financial Services objects that are required for profile, transaction,
  and engagement analysis.

- Map source objects to the target model objects that are needed for identity, segmentation, and
  activation outcomes.

- Confirm that required relationships are present before audience publishing.

## Identity Resolution Focus

Configure the identity logic to unify person and account signals that are needed for customer-level
profile views used in personalization and engagement targeting.

## Calculated Insights Focus

Use calculated insights to support audience definitions, campaign decisions, and financial
engagement analytics. For more information, see
[Enhance Data with Insights](https://help.salesforce.com/s/articleView?id=data.c360_a_insights.htm&type=5).

## Segmentation and Activation Focus

Build audience segments from unified profiles and financial engagement signals. Activate segment
outputs to configured downstream channels, including Marketing Cloud where applicable.

## Guidance for Standalone Deployments

If you deploy the
[FINS Salesforce Data 360 System API](https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/)
independently of the use case, do the following:

- Omit use case-specific segmentation and activation configuration.

- Omit use case-specific Marketing Cloud activation setup.

- Omit use case-specific calculated insights unless required by downstream consumers.

- Keep only the connectors, schemas, streams, and mappings that are required by your API data
  contracts.

## See Also

- [Prerequisites](https://docs.mulesoft.com/financial-services/latest/prerequisites)

- [MuleSoft Accelerator for Financial Services](https://docs.mulesoft.com/financial-services/latest/)