Step 3: [Import Data] Map fields and set up matching in the CDP

Context

Once you have created a Salesforce connection you can now start mapping your fields to the CDP. 

Prerequisite: 

• Step 1: [Import Data] Create a Salesforce Data Import Integration User

• Step 2: [Import Data] Create a Salesforce Data Import Connection

  • You must be using the new automated data import workflow. If you are not using the new automated data import workflow, you should reach out to your customer success manager to integrate Salesforce with Rev.Up for data import. 
• Review how D&B approaches matching leads to accounts 
• Strategy for Mapping Fields to the CDP

Step 1: Add a data source to the Salesforce connection.

 

 

Step 2: Map fields 

For each entity from Salesforce, Accounts, Contacts, Leads we have pre-mapped some common standard fields. You can click on the Edit Mapping button to add or remove field mappings. Fields that are not mapped will not be imported.

 

Step 3: Add additional fields using the edit mapping wizard.

To map fields from Salesforce to the CDP, simply drag and drop fields from the right side of the screen to the middle of the screen. You can also use the dropdown in the middle of the screen to choose which field from Salesforce you want to map to the CDP. 

 

The goal of the CDP is to unify customer and prospect data. When you add your fields from Salesforce to the CDP, there are few things to keep in mind: 

• You should map your Salesforce fields to the field in the CDP that most closely matches the meaning of the Salesforce field. You can add a Salesforce field to an existing attribute or create a new attributes. 
• You can map a field from Salesforce to more than one field in the CDP. 
• You can map fields from different connections to the same field in the CDP. This is how you can prevent the duplication of attributes that have the same meaning. An example is Company Name and Account Name may be called different names in different connections, but have the same meaning. 

 

Step 4: Matching Salesforce records within the CDP 

You can use this section to configure how you want your records to match to the CDP. If you are not sure of how you want your records to match to the CDP, you can skip this section by using the Skip for Now button in the source wizard and come back later. 

For additional information on creating these settings, check our our article that covers match and merge.

 

Unique Record ID: By default we will use the 18-digit unique id of the record in Salesforce. This ID will be used to deduplicate your records that come from Salesforce. If you use the default setting it means that we will have the same view of your data that Salesforce does where each record is represented by an 18-digit ID.

If you change this setting we cannot guarantee that your data will import the way you expect.

Matching your records to the CDP: When it comes to matching your records to the CDP there are two methods that are used. 

• D&B Identity Resolution: Be default, lead records in Salesforce do not have an associated account and we will use other information such as company name, domain and others to match your leads to account records. To better understand our lead to account matching process, please review our article. 

Because contacts have an associated account in Salesforce, we by default use this relationship. When you are creating a source for accounts and contacts this will done for you. If you change this setting we cannot guarantee that your data will import the way you expect.

 

You can configure which fields you want to be used for D&B Identity Resolution to match records. In the context of Salesforce, this is most useful for leads. 

 

• ID Matching (deterministic match): If you have mapped for than one field from a data source to the same CDP attribute, we will assume that you want to use this field to match IDs between the data sources.

Because contacts have an associated account in Salesforce, we by default use this relationship. When you are creating a source for accounts and contacts this will done for you. If you change this setting we cannot guarantee that your data will import the way you expect.

 

You can configure which IDs you want to use to match the data source you are working on to another data source in the CDP. For our native connectors most of this work will be done for you, but if you have additional IDs or a custom way your join your data together, you will need to configure this option. 

 

 

 

Step 5: Give your data source a name