Qualified’s native integration with Salesforce allows users and automations to sync with your Leads, Contacts, Accounts, and more.
To get started, go to Settings → Integrations → Salesforce → Lead Mapping.
Mapping data to basic required fields
Many implementations start by mapping a basic set of information to Salesforce to create and convert Leads into an Account, Contact, and Opportunity.
Let's start with the most basic required fields in Salesforce: name, email, and company. You'll notice when you first open this page that these lead fields are dynamically pulled in because they're required by default to create a lead in Salesforce. You'll now want to go in and select the visitor field in Qualified that will map to Salesforce.
If you don't see one of your Salesforce fields in this list, it means that the user you've connected to Salesforce with doesn't have access to that field. You can change this setting in Salesforce by navigating to Setup → Object Manager → Lead → Field → Set Field Level Security.
If you don't see the visitor field that you'd like to match up with your Salesforce field, select "Create Field" from the drop-down menu to create it.
Mapping data to more complicated data types
Data types
Data types control what values a Salesforce field will accept in that field. In the basic example above, the field "Company" is a text field, meaning it will accept a string of characters, and the field "Email" is an email field, which means that it must contain a valid email address. Let's show an example of a more complex (and quite common) data type, such as a picklist.
It's pretty common in Salesforce for fields like "company size" or "industry" to have a default set of values set by your Salesforce admin. As a result, when you map data into these fields, it's a good idea to only allow the values set by your Salesforce admin, and once you select the field from Salesforce the mapping automatically pulls in these values as shown here:
Fields not supported
There are some Salesforce fields that we cannot map into at this time:
- Lookup fields
- Multi-select picklists
- Formula fields
Mapping checkbox data to Salesforce
Mapping to a checkbox can be a bit more complex than other data fields as checkboxes are always true or untrue (checked or unchecked) and are often used to trigger workflows within your Salesforce instance.
Before mapping your checkbox, you'll notice two options during the data mapping process: default or fixed value. A default value allows you to map a value to the field only if the field is already empty.
Because checkboxes in Salesforce are never empty (meaning they are always true or untrue), in most cases you'll not want to use this option in your mapping. Instead, the fixed value option will allow you to always override whatever is in the field in Salesforce with a predetermined value (in this case: true).
If you'd like to mark your checkbox as 'true', meaning you'd like to check it when a lead is created or updated in Salesforce, you must then select 'true' as your fixed value.
Mapping hidden field data to Salesforce
It's a common practice to have some field values hardcoded when creating leads in Salesforce. This prevents your sales reps from setting these values manually and instead allows Qualified to set the values based on your rules.
The most common of these fields on the lead object is the lead source. Setting a hardcoded ("hidden") value to this field will tell you that the lead originated from a Qualified conversation on your website and can be used later by marketing managers and sales managers for reporting purposes.
.svg)
