Create Global Profiles

Learning Objectives

After completing this unit, you’ll be able to:

  • Define data preparation rules that help identify when multiple records are the same customer.
  • Run data jobs to import data and create global profiles.

Like many businesses, NTO stores customer information in multiple data sources. Its B2C Commerce instance includes customer contact information and order history. Its Service Cloud org tracks support cases. Pia and her implementation team learned in the Customer 360 Data Manager Fundamentals module about the value of global profiles with global party IDs to represent each person and link them across all of their system profiles and transactions.

With the NTO data sources connected to Customer 360 Data Manager, Pia is ready to complete the next procedures to create global profiles.

  1. Prepare data and customize rules.
  2. Import source data and schema configuration files into file staging.
  3. Generate global profiles and global party IDs.

The setup process with the second step highlighted: data preparation and load.

Let’s break down each of those steps to see how Pia accomplishes this critical objective in one work day. 

Pia sitting at her desk, smiling, with a cup of coffee. Clock on the wall shows 8 AM.

Define Data Rules for Global Profiles

In Customer 360 Data Manager Fundamentals, you learn about data preparation rules, reconciliation rules, and match rules. Though preparation rules and reconciliation rules are applied automatically during global profile data processing, match rules are customizable. 



We recommend that you try using at least one of the default match rules before customizing. The default match rules fit most common scenarios.

As the enterprise architect for NTO, Pia reviews Match Rules in Salesforce Help to learn about the default match rules. Before she imports data, she decides to add a custom match rule that aligns with NTO’s data stewardship practices. She wants to include NTO’s loyalty program ID as one of the match fields. To do this, she creates a rule to match last name with the Identification Number field, which is used for its loyalty program ID. Then Pia activates the custom rule and the default match rules that NTO is using. Let’s follow along with Pia in the Trailhead Simulator.

Trailhead Simulator

  1. Launch the Trailhead Simulator. Click Begin.
  2. In Customer 360 Data Manager under Setup, click Global Profile Rules.
  3. Click New.
  4. Specify your match criteria. For the field, select Last Name.
  5. Click Add Condition.
  6. Select Identification Name.
  7. Click Add Condition.
  8. Select Identification Number.
  9. Enter a name for the rule. In this example, enter Last Name_Loyalty ID.
    The match rule form with fields added for Exact Last Name, Exact Identification Name, and Exact Identification Number.
  10. Click Save.
  11. Beginning at the top, click the dropdown arrow next to each rule and click Activate. For the simulation, start at the top and work your way down.
    The dropdown menu with a mouse clicking Activate.

The match rules are activated.

Files into Staging

Pia is now ready to import NTO’s data and schema configuration from its data sources. To do this, she needs to complete these procedures: 

  1. Create customer data and schema configuration files from each data source object used in global profile creation.
  2. Import the files into Customer 360 Data Manager file staging.

Customer 360 Data Manager uses a configuration (.conf) file from each data source to map the data source schema to the global profile schema. Then, a data file is used to bring in the actual customer data to process into global profiles. 

For NTO’s implementation, Pia needs these files:

Configuration Files

  • B2C Commerce—Customer System object
  • B2C Commerce—Order System object
  • Salesforce org—Person Account object
  • Salesforce org—Contact object

Data Files

  • B2C Commerce instance
  • Service Cloud org

First, Pia assembles the system admins and developers from the Customer 360 Data Manager implementation team to discuss what she needs from each data source. They review the Data Files for Global Profiles considerations in Salesforce Help. This critical step ensures that the admins generate files following the requirements for file syntax, record validation, file and date formats, and file size. 

Next, the team accesses the Customer-360-Data-Manager Git repo, where they find file templates. 

Customer-360-Data Manager Git repository for file templates and code snippets.

Because NTO hasn’t customized its Salesforce schema, the team uses the .conf templates to streamline the process. They carefully review the templates, making minimal changes to ensure the exported data maps correctly from the file to the global profile schema. 

The steps to create and upload the data and configuration files differ between a B2C Commerce instance or a Salesforce org like Sales or Service Cloud. Let’s review both.

B2C Commerce Data File into File Staging

First, Pia needs the B2C Commerce data files. She already connected their B2C Commerce instance as a data source, so she can run a job to generate the data file. You can follow along using the Trailhead Simulator.

  1. Launch the Trailhead Simulator. Click Begin.
  2. In Customer 360 Data Manager, under Setup, click Data Jobs.
  3. Click New Job.
  4. Select B2C Commerce to File Staging.
  5. Click Next.
  6. Under Data Source, select the B2C Commerce instance: ecom-2015372227.
  7. Select the B2C Commerce site that is authorized for the instance. For this example, select SiteGenesis.
  8. Click Next.
  9. The customer and order objects are selected, which contain information from the customer list for your site.
  10. No need to select filter criteria for this example. Click Next.
  11. Enter a name for the job that makes it easy to identify. You can include information about the instance, filters, and objects. For this example, enter Commerce_Customer and press Enter or Return on your keyboard.
  12. Click Next.
  13. Click Start Job.

After the data file is created, Pia finds it on the File Staging tab. She repeats the process to generate a data file for the Order system object.

B2C Commerce Configuration File into File Staging

Next, it’s time to get the .conf files into the file staging area in Customer 360 Data Manager. Follow along using the Trailhead Simulator.

  1. Launch the Trailhead Simulator. Click Begin.
  2. In Customer 360 Data Manager, under Setup, click Data Jobs.
  3. Click File Staging.
  4. Click Config Files.
  5. Click Upload File.
  6. Select the Standard_CommerceCloudCustomer.conf file.
  7. Click Open.

Pia repeats these steps to upload all of the configuration files she needs for each object. Pia is ready to move on to NTO’s Service Cloud org.

Service Cloud Data and Configuration Files into File Staging

Pia needs two configuration files for the Service Cloud objects she will map:

  • Salesforce Org—Person Account object
  • Salesforce Org—Contact object

Felix, the Service Cloud admin for NTO, uses the .conf files for Service Cloud provided by Salesforce in the Git repo. He creates the data file for the Service Cloud objects using Workbench. He creates a query that includes the standard and custom fields NTO wants to include in its global profiles, using the example in Salesforce Help: Create a Data File for Your Org. He names the files with the prefix sc_ to ensure the files display when creating global profiles. Felix sends the files to Pia.

Pia logs in to Customer 360 Data Manager to complete the data job for uploading the configuration files. Follow along using the Trailhead Simulator.

  1. Launch the Trailhead Simulator. Click Begin.
  2. In Customer 360 Data Manager, under Setup, click Data Jobs.
  3. Click File Staging.
  4. On the Data Files tab, click Upload File and select the data file. For this example, select CRM_PersonAccount.csv.
  5. Click Open.
  6. Click Config Files in the file type list.
  7. Click Upload File and select the .conf file for Service Cloud. For this example, select standard_PersonAccount.conf.
  8. Click Open.

With all of the configuration files in file staging, Pia can create the global profiles.

Create Global Profiles from File Staging

Next, Pia reviews the steps in Salesforce Help: Create Global Profiles and uses Customer 360 Data Manager to process the imported data into global profiles. This process reviews the files, applies data preparation rules, and creates global profiles. 

The setup process with the third step highlighted: create profiles.

Trailhead Simulator

You can use the Trailhead Simulator to practice creating global profiles along with Pia.

  1. Launch the Trailhead Simulator. Click Begin.
  2. In Customer 360 Data Manager under Setup, click Data Jobs.
  3. Click New Job.
  4. Select File Staging to Global Profile Hub.
  5. Click Next.
  6. Select a data source. For this example, select Service Cloud EU Production.
  7. Click Next.
  8. Select the object you are loading. For this example, select Account.
  9. Click Next.
  10. Select the standard_PersonAccount.conf file. Click Next.
  11. Select the data file to load. For this example, select CRM_PersonAccount.csv.
  12. Click Next.
  13. Enter a name that helps you identify the job. For this example, enter Load_account and press Return or Enter on your keyboard.
  14. Click Next.
  15. Click Start Job.

The job status shows how it’s processing: Submitted, Running, and Complete.

Pia repeats this process for each data source they’re using to build global profiles. Pia is almost ready to export global profiles to import into source systems, but first she’s using Customer 360 Data Manager for NTO’s next objective: identify and correct data quality issues.


Keep learning for
Sign up for an account to continue.
What’s in it for you?
  • 1 in 4 land a new job
  • 50% receive a promotion or raise
  • 80% learn new technologies that boost their resume
  • 66% say it increases productivity
Source: Trailblazer Community Impact Survey 2019