Setting up field mapping on the Cognism Salesforce Application

Olivia

Updated 02 June 2022 10:32

Sections in this Article:

Prospector Mapping Settings
Refresh Mapping Settings
Recommended Fields to Set Up
Which Field Types to Use

Cognism users with the 'Cognism App Admin' permission set on Salesforce, will have the ability to edit the field mapping in the Settings.

This guide will help explain the different mapping options we have available and how we generally recommend setting them up.

Prospector Mapping Settings:

You can access the Prospector Mapping Settings within the Cognism Salesforce App by going to the 'Settings' tab on the navigation bar. You'll see the option on the left-hand side menu:

There are three columns that you'll see: Cognism Fields, Contact Mapping Fields and Lead Mapping Fields

The column on the left (Cognism Fields) are all of the available data points to map from Cognism
The column in the middle (Contact Mapping Fields) is where you select which Contact and Account Fields to map the data points to, using the dropdowns displayed - fields that exist in your Salesforce
The column on the right (Lead Mapping Fields) is where you select which Lead Fields to map the data points to, using the dropdowns displayed - fields that exist in your Salesforce

There are also three sections: Person, Company and Dynamic Fields

- The first section (Person) is everything that relates to the person you're targeting i.e their email address, where they are located etc.
- The second section (Company) is everything that relates to the company you're targeting (the company the person works for) i.e. the Industry, where the HQ is located etc.
- The third section (Dynamic Fields) is where you can set up alternative mapping that's not available in the data points above. More details on this here

When you first install the app, there will be some fields mapped already such as 'First Name', 'Last Name', 'Email' etc. The dropdown will display which Salesforce field they are mapping to.

Any field that is not mapped will either say 'Select Field' if it's never been edited or 'None' if the previous value was removed

You can open the dropdown and search for the field you want to map the data point to. For example, if you choose 'Mobile' then you'll want this data point going to a field that typically displays a person's mobile number (MobilePhone, Phone). The name that appears in the dropdown is the Field API Name.

Fields such as Name and Address are mapped to the default Salesforce fields, unless changed:

First Name and Last Name go to 'Name' on both Lead and Contact
The person City, State and Country go to 'Mailing Address' on Contact and 'Address' on Lead
The HQ location goes to 'Billing Address' on Account and nothing on the Lead. If you'd like to map the HQ location for the Lead, you'll need to create a company-specific location field on this object.

You can tell which object to create the field for by checking the text next to each dropdown. In the 'Person' section, the middle column is for Contacts and the right column is for Leads. In the 'Company' section, the middle column is for Accounts and the right column remains for Leads (as this is a standalone object).

Dynamic Fields:

At the bottom of the page, you will find the Dynamic Fields. These fields allow you to map up to 4 different constant values for each object (Lead, Contact and Account). This is where you can map alternative/custom fields that were not available in the list above.

Mandatory fields such as 'Lead Status' could be mapped here, inserting the value into the box on the left and then finding the field name in the dropdown. Example below:

The value you input into the blank box must be a static/constant value (something that will remain the same for all records saved), it cannot be a date or ID for example.

Another field example to map is 'Record Type'. Insert the Record Type ID into the blank box on the left and find the field 'Record Type ID' in the dropdown. Example below:

Note: For any mapped field, you may have the orange text warning (as above) saying "This field can be incompatible!". This is just a warning message that pops up for certain field types, however, you can still map the field across. If you get a red pop up instead, you won't be able to save the field.

Once you’re satisfied with the data points mapped, ensure to save your configuration by selecting the “Save” button. Note that you can come back at any time to add or remove mappings as is required.

Refresh Mapping Settings:

You can access the Refresh Mapping Settings within the Cognism Salesforce App by going to the 'Settings' tab on the navigation bar. You'll see the option on the left-hand side menu:

The same data points from Prospector are available for mapping in Refresh. The crucial difference is the ability to control how your data will be enriched under the 'Application Rules'.

The Application Rules are in the added fourth column on the far right. You can select which rule you'd like for each line depending on how it will work best for your organisation:

Always Overwrite - if Cognism finds new data for the record, we will always overwrite your existing data with our current data (when applying the refresh changes)
Apply If Blank - if Cognism finds new data for the record, we will only input the value into your Salesforce field if it is blank and no data exists in this field already
Never Apply - no matter if we find new data or not, we will not input any value into this field

Mapping and rules are used for all refresh options (Single/Bulk/Scheduled/Live). It's important to think about this when setting up the mapping.

When you install the application, this column will default to a mix of rules (for example Company Name = Never Apply). You are free to edit these however you wish but it's worth considering the pros and cons of all the options.

Data points that are unmapped will be excluded from the Refresh process, similar to using the rule 'Never Apply', so putting it simply, if you do not map a field, it will not refresh that data.

Recommended/Common Fields to Set Up:

Below are some of our recommended and common fields to map. Each organisation has different preferences and needs and therefore, will use this list for guidance but none of the below are mandatory to use Cognism.

Lead & Contact:

Direct Dial - you can use the existing 'Phone' field but if you'd like a dedicated field for a direct dial, we would recommend creating this
LinkedIn/Personal LinkedIn - the URL for the person's LinkedIn profile
Job Start Date - the job Start Date for the person's most reason position
Cognism Campaign Name - not to be mistaken with a 'Salesforce Campaign', this field is relating to Cognism only. All records saved from Prospector will go into a named Cognism Campaign. You can create new ones each time or save records into an existing campaign
Lead Source - this field will already be created, however, we recommend adding "Cognism" as a value to your existing picklist. The text in the box on the left can be edited as you wish but make sure the value is in your picklist

Lead & Account:

Industry - we have three main recommendations:
- Option 1: We can send you the CSV of our industry values. These values can be cross-referenced with your existing list and added to the Industry field. This is an extensive list of industries.
  - If you go in to edit the list, we recommend clicking ‘New’ instead of ‘Replace’ as this just adds to your current list rather than replacing the old values
- Option 2: Create a new field called "Cognism Industry" for example. This could be created as a text field or picklist (we can send the CSV values over)
- Option 3: Following on from option 2, you could create the new field and then create a formula to input the 'Industry' value based on the 'Cognism Industry' i.e. If Cognism Industry = "Animation" > Industry becomes "Other"
Company Size - we have 3 different options to map
- Company Size (range) - this will be the range for the company size i.e. 1-10, 11-50 etc.
- Company Size From - the lowest number of the range i.e. 1, 11 etc.
- Company Size To - the highest number of the range i.e. 10, 50 etc.
HQ Location (Country, State, City etc.) - on Lead, the location fields will already be mapped in the 'Person' section. If you'd like to have the HQ data, we recommend setting up these fields.
Company LinkedIn - the URL for the company's profile
Company Crunchbase - the company's Crunchbase profile. This shows financial information such as which round of funding they're on
Company Type - we can send over a CSV of our values. Company Type examples include "Non-Profit", "Public", "Private" etc. The closest field that will exist in Salesforce is 'Ownership', however, these values will differ and the picklist will need to match.
Company Technologies - any technologies that the company uses. This can be anything from the CRM they use to payroll software, plus much more. Example = "Salesforce"
Office Phone - the phone number for the specific office location, rather than the HQ
HQ Phone - the phone number for the headquarters
- There is one generic 'Phone' field already existing on the Account object

Which field types to use:

Fields with a star will have a standard Salesforce field or Cognism created field already existing as an option to map (*), however, these fields may require edits. All users saving records from Cognism must have create/read/edit permissions for the mapped fields.

First Name (Text)*
Last Name (Text)*
Job Title (Text)*
Email (Email)*
Email Status (Text)*
Mobile (Phone)*
Direct Dial (Phone)*
Country (Text or Picklist [needs to match our values])*
State (Text or Picklist [needs to match our values])*
City (Text)*
Linkedin (URL or Text)
Job Start Date (Text)
Cognism Campaign Name (Text)
Company Name (Text)*
Company Industry (Text or Picklist [needs to match our values])*
Company Size (Text)
Company Size From (Number)
Company Size To (Number)*
Website (URL or Text)*
HQ Country (Text or Picklist [needs to match our values])*
HQ State (Text or Picklist [needs to match our values])*
HQ City (Text)*
HQ Street (Text)*
HQ Zip (Text)*
Company LinkedIn Handle (URL or Text)
Company Crunchbase (Text)
Company Type (Text or Picklist [needs to match our values])*
Company Tech (Text, Text Area or Long Text Area)
Office Phone (Phone)*
HQ Phone (Phone)*
Company SIC code (Text or Number)*
Company ISIC code (Text or Number)
Company NAICS code (Text or Number)
Company Founded Date (Text)
Company Revenue Range (Text)
Company Domain (Text)