6sense maintains its own set of values for Revenue Range, Employee Range and Industry in its company database. If your CRM or MAP has specific picklist values for these attributes, they may or may not match with 6sense’s values. To ensure 6sense is enriching the system values you expect when creating new leads or updating existing records in CRM or MAP, you can set up a mapping between the 6sense values and your picklist values.
You are not required to create custom mappings. By default, 6sense enriches records using its defined set of firmographic values.
A best practice is to create separate custom fields on Accounts, Leads, etc. to accept 6sense’s values.
If you cannot use separate custom fields for any reason, or if your organization has strict rules on data validation within your CRM or MAP that require you to use different pre-existing values than what 6sense has available, then you can configure custom value mappings.
If you need to update State values through 6sense, and your organization has strict validation rules within Salesforce where the system will not accept any State values from smaller countries, then you should consider excluding those countries using the State Exclusions by Country setting. If your Enrichment Orchestrations or contact purchases do not update any Salesforce Fields with State values, then that setting is not relevant.
Set up mapping between 6sense and a CRM or MAP
The following example shows custom value mappings for Salesforce. The steps are the same for other systems.
To set up custom mappings from 6sense values to CRM or MAP values:
Go to Settings > Data Settings > Custom Value Mappings.
Click on the Value Mapping for your system.
This example shows a Salesforce Custom Value Mapping, with tabs corresponding to the core firmographic values that are configurable: Employee Range, Revenue Range, Primary Industry, Industry (Legacy), Country, and State.
In each tab, the 6sense Value column represents the set of firmographic values available in 6sense’s database. Add the mapping values for your CRM or MAP in each relevant tab.
For example, let’s say that your organization does not use as many bands for Employee Range as 6sense does; perhaps the lowest band is 1 – 100 employees. Instead of allowing 6sense to enrich any Salesforce accounts, leads, or contacts with the values of 0 – 9, 10 – 19, 20 – 49, or 50 – 99, you map all of those values to your custom value of 1 – 100, as shown:
The example settings mean that whenever 6sense identifies a record as having 0 – 9, 10 – 19, 20 – 49, or 50 – 99 employees, instead of enriching your Salesforce fields with those values, 6sense instead enriches the Salesforce field with the value of 1 – 100. Other 6sense values are not mapped to any custom values in Salesforce.Update relevant values for the other tabs.
If you configure State Exclusions by Country: specify whether any countries’ states should be ineligible for enrichment.
Click Save.
FAQ
Do I need to set up any custom value mappings by default?
No. If your organization is comfortable using 6sense’s firmographic values as is, then you do not need to use custom value mappings.
When should I configure customer value mappings?
The main reason you should consider reviewing and setting up custom value mappings is if your organization has a pre-defined set of values that can be used when labeling records with industry, revenue, or employee values. These settings will allow you to map 6sense’s available values to your organization’s pre-defined set of values.
Does this affect all analytical views within 6sense? How about the Company Identification API?
No. Custom value mappings are currently only applicable to enrichment Orchestrations and when creating new leads or contacts during acquisition workflows. All analytics views within the 6sense Platform and Sales Intelligence, along with values returned as part of the Company Identification API, continue to use 6sense’s default firmographic values, regardless of any custom value mappings.
What values can I select for mappings?
You can map 6sense’s firmographic values to any value you choose to provide as input. 6sense does not validate whether your entry is already used with your CRM or MAP, so make sure you confirm that any custom value you choose to map is a value your organization expects to see in that system.
Can I map to a custom value that is not already used in my CRM or MAP?
Yes. As mentioned above, 6sense does not check whether a custom value is used within your CRM or MAP. Therefore you can choose to map to an existing value, or you can choose to map to a value that does not exist in your CRM or MAP yet. Using the latter approach means that 6sense Orchestrations may be the source of any new values that your team begins to see in CRM or MAP, so make sure you confirm with your team before introducing such mappings.