Salesforce Integration: Field Mapping
Contents of this article (click to jump to section):
- Starting Requirements
- How can I manage my Salesforce mapping options?
- Table Breakdown
- Important Notes about Salesforce Custom Mapping
- Can all Salesforce Fields be mapped using RocketReach's data?
- Testing your Custom Mapping
RocketReach offers custom mapping through our Salesforce integration only for directly-purchased accounts with supported plans.
If you're currently on one of our self-serve plans and would like to access the custom mapping feature, please reach out to our sales team using this form for more information about our custom plans.
Only Team Owners and Team Admins are able to change field mappings. Any custom mappings set by a Owner or Admin will automatically be pushed to all members of the team using the Salesforce integration.
Non-admin team members can see the Salesforce field mappings but cannot make changes (view-only permission).
Each user/member of a team must connect Salesforce in order to use the integration and take advantage of custom mappings.
When you integrate RocketReach and Salesforce, your mappings will default to the fields you have already created in Salesforce. This allows you to determine what data from RocketReach is assigned to what field in Salesforce.
You can find more information about connecting RocketReach to your Salesforce account here.
How can I manage my Salesforce mapping options?
To manage your custom Salesforce mapping, visit the integrations page and select "Manage" under the Salesforce option.
Then, choose Mappings on the settings page as shown below.
From the mappings table, you can manage each contact type (Lead, Accounts, Contacts) separately.
Let's breakdown the table:
RocketReach Field - These fields are the data that is available for each contact that can be exported to Salesforce.
- You can use each data type in the RocketReach fields multiple times in your custom mapping table.
- You can create a custom value RocketReach field. This will transfer anything you type in the “Example” static value into the mapped Salesforce Field for all exported contacts based on your "update action" settings below or by creating a new record in Salesforce.
Example - This is static data that serves as an example of what may be exported.
Salesforce Field- This is the field that is selected to hold the data exported by the RocketReach field on the same line. Each data type in the Salesforce fields can only be selected for one field during custom mapping and cannot be mapped to multiple RocketReach fields.
Update Action - This allows you to choose what happens during the export if a duplicate contact is found to already exist in your Salesforce account. Let's take a closer look:
- For this field, you can choose between "Fill if Blank" or "Overwrite".
- To understand the action of each of these options, you should first understand our deduplication logic for our Salesforce integration. This information (and more!) can be found in our Salesforce Integration article and also in the reference photo below.
- Once we have moved through that logic and either determined that this contact does not already exist in Salesforce or that we were able to locate a match for this contact, what you choose in "Update Action" will tell the integration what to do next.
Fill if Blank - This option will not replace any existing data you already have in Salesforce and will instead add to by filling in the data we have if the mapped Salesforce Field is blank.
Overwrite - This option will fill all corresponding Salesforce fields when we find a duplicate contact, replacing the existing data in Salesforce with the RocketReach data for that field.
The mappings table also allows you to delete rows and create new rows, to tailor RocketReach mappings to your Salesforce custom fields.
- If you have created a custom field in your Salesforce account and marked it as required, you will need to map this field in the RocketReach custom mapping table. If not, we will be unable to create the record because we will be unable to populate the required field.
- If you want to change the Salesforce field to something that isn't listed in the Salesforce field dropdown, you must first create that field in your Salesforce account. Instructions on the Salesforce side can be found here.
- If any changes are done to the field configuration in your Salesforce account, you will need to make the applicable changes to the RocketReach custom mapping table.
- RocketReach will take into account any other setting you have defined within RocketReach when it comes to what data to export. For example, if you have professional emails only or personal emails only selected, the export will take that into account if you choose to map a "Recommended Email" field.
Can all Salesforce Fields be mapped using RocketReach's data?
Some Salesforce Fields are unsupported formats and cannot be mapped to RocketReach fields. These fields will still show in your drop-down, but will not be able to be selected. They will be greyed out with an 'X' next to them.
The exception to this is the Industry Salesforce Field. We have pre-mapped this field to specific data and it is included in the default mappings. If you delete the row that contains the Industry Salesforce field, the only way to restore it is by restoring all mappings to default.
Be sure to test your mapping selections before saving. Please note that this will create a test record in Salesforce, so you may receive a notification that a new record was created when you take this action. We will automatically remove the created test record once the testing is done.
If you have more general questions about our Salesforce Integration, please visit our Salesforce Integration article.