Optimize Customer Experiences Use Case Setup Guide
The Optimize Customer Experiences with Data 360 in MuleSoft Accelerator for Financial Services requires initial configuration in Salesforce Data 360. Complete the core configuration by following the Data 360 learning path.
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 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.
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 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.



