As part of your Salesforce integration, Leadspace conducts a field mapping process to populate the proper Leadspace fields into your Salesforce fields.
This manual consists of the following chapters:
- Leadspace Fields for Mapping
- Leadspace Auto-Populated Fields
- SFDC Mappings
- Value Mappings
- Fields Checklist for Successful Integration
To have a successful integration, please review the full document before moving on to the other documents.
Leadspace Fields for Mapping
This article consists of two parts:
- Leadspace Fields
The table at the top of the document consists of all the fields Leadspace can populate into your SFDC instance.
The first column indicates the field type (Lead, Contact, or Account). Leadspace can populate data into all three field types.
The second column indicates the Leadspace fields. These are all the fields that Leadspace offers and are what Leadspace can push into your Salesforce. You will use these field names to indicate what Leadspace field will be populating your Salesforce field.
This column indicates whether the field is a text or numeric field type. If you create a custom field in Salesforce that you want Leadspace to populate, you will need to set the field type to the correct format.
** Please note that for most fields, the field type is Text. For a select few (exact revenues, exact company sizes, and score fields), it is Numeric.
This column contains any additional notes that can help determine the field mapping.
For example, note that on the COMPANY_STATE field, Leadspace pushes the the state name in a 2-letter format (rather than a full name format). If you wish Leadspace to push these fields in a different format, please let your Leadspace contact know as this can be adjusted through value mapping.
- Leadspace Picklist Values
The second part of this article contains the list of Leadspace picklist values for the following fields:
- Person Levels
- Person Departments
- Company Size Ranges
- Company Revenue Ranges
- Industries and Sub-Industries
If some of these values don't match your picklist values, we will explain in this document how that can be adjusted under the Value Mapping section.
Leadspace Auto-Populated fields
This document lists all standard Salesforce fields, organized by object (Lead/Contact/Account). The cells highlighted in pink are Salesforce fields that are auto-populated by Leadspace.
Important things to note:
- If you are planning to use the standard fields, you won’t need to map the fields highlighted in the pink cells
- Although these fields auto-populate into your standard fields, they can also be populated to any custom field as well
- If you want to disable auto-population for any standard field, please let your Leadspace rep know so they can disable the automatic population on the backend
On this document, the first tab, “Mapping Format”, would be the actual spreadsheet you will fill in when creating a new field mapping or change the existing mapping at any given time.
Besides from the initial setting of the mappings, in case you would like to add additional mappings in the future, this is the document you will use.
In this format, you will need to fill out the following columns:
- Type (Column D)
- salesforceFieldName (Column E)
- mappedLeadspaceField (Column F)
- defaultValue (Column G)
- override (Column I)
Type (Column D)
This column will indicate to which object you will want Leadspace to populate in your Salesforce out of the possible 3: Lead\Contact\Account
As mentioned earlier, almost all the fields can be populated into all three objects (besides the few fields which apply for Lead only).
salesforceFieldName (Column E)
This column will consist of the API field names you would like Leadspace to populate into your Salesforce instance.
This, of course, can be standard fields OR custom fields.
Please remember that custom fields end with “__c.”
Make sure to insert the proper field name as it exists on your Salesforce or otherwise the mapping won’t work.
mappedLeadspaceField (Column F)
In this column, you will mention the Leadspace field you want us to populate into the field.
You will do it using the “Leadspace Fields” document we explained about earlier on section A.
Just copy the Leadspace field name listed on this document and copy it into the format.
Please keep in mind that some of the fields will be auto-populated by us you’re your standard fields. If you are planning to use the standard fields for those, no need to list them in the document.
defaultValue (Column G)
You will use this column to indicate to us if you want us to set a default value for a specific field for any reason.
For example, a typical use for that would be setting the “Lead Status” field to match you internal terms instead of Leadspace indicating it as “Open”.
This column can certainly remain empty so don’t afraid to leave it as is if needed.
override (Column I)
This column is rather simple, all you need to do is choose if you want Leadspace to override existing data and fill in “TRUE” if you do and “FALSE” if you don’t.
Override means that if the field has any value in it while Leadspace is populating the object, we will replace the data with our data.
In case the field is empty, Leadspace will populate this field whether the override is set on or off.
Once this Excel spreadsheet format ready with all the fields, please send it back to Leadspace’s Integration Manager and your Customer Success Manager.
On the second tab of this spreadsheet, “Mappings Example”, you will find an example of how a finalized mapping format should look like.
The value mapping process is a process designed to make sure Leadspace field values will match the values you use in your CRM whether they are part of a picklist you have or not.
The process allows Leadspace to convert the data values before sending it over to your end.
Common use cases for this could be -
- Matching the states and country picklists you have to Leadspace values
- Make sure the Leadspace values for person levels, company size ranges and company revenue ranges match the ones in your CRM
- Removing the “http://www.” Prefix from websites
- Any other use case you think you might need
Please note that this step is not mandatory and designed only for your convenience.
Moreover, although the process might seem a bit complex, in the “Value Mappings” document attached, on the second tab, “Value Mappings Example”, we will attach a sample file containing multiple examples of how to get it done.
To complete this process, on the first tab in the document, “Value Mappings Format”, you will fill out an Excel spreadsheet format with the following columns:
Source Field Name (column A)
In this column, you will use the field names in the format to choose what the source field you want to convert is.
Meaning, what is the Leadspace value you want to convert.
Important! Please use only fields from the format.
Target Field Name (Column C)
After you chose the source field on the previous clause, now you need to determine what the target we are going to convert is.
In most cases, it would be the same field but in some cases, it won’t.
For example, you may choose to convert Leadspace company revenue range according to the company exact size.
Rule (Column E)
This section contains all the rules Leadspace can apply on the fields, both textual and numeric.
Be sure to choose a rule from the list of rules listed in the format.
First Value (Column F)
This would be the value the source field will be matched against using the rule you chose.
This field is required for all the rules except:
Second Value (column G)
This column applies only to the “IS_BETWEEN” rule to mention what is the range the value could be found in.
For all other rule types, you should leave this column empty.
New Value (Column H)
Assuming the rule you designed so far has been matched, this column indicates what the new value you are going to insert into the target field.
Is empty (Column I)
If you want the new value to be empty or not, you will mention it in this columns. Naturally, if column H has a value, you will need to insert “False” into a column I and vice versa.
Once you have this document completed, send it over as well to Leadspace’s Integration Manager and your Customer Success Manager.
Along with the documents, we have attached a sample mapping file you can use to see how a final form should look like. It will give you a good sense of what your final form should look like and what could be common use cases for value mapping.
Fields Checklist for Successful Integration
To have the integration as successful as it could be, attach is a checklist of settings we highly recommend to check each field to make sure we won’t encounter any major issue while integrating Leadspace with your Salesforce instance.
The settings you should verify -
Make sure that all the user profiles have permissions to write into the Salesforce fields you want Leadspace to populate as during the import of data from Leadspace, data will be written to these fields.
To check the field permissions, please go to your Salesforce Setup -> Administration Setup -> Security Controls -> Field Accessibility -> Choose one of the objects (Lead\Contact\Account) -> Choose “View by Fields”\” View by profiles” Check the field visibility for this field\profile:
If for some the fields you have any active picklists, make sure to address our Value Mapping section
Should you have any questions or remarks regarding the process or this document, please let us know at email@example.com or contact your Customer Success Manager.