In this guide, you'll learn how to map data from Qualified to Salesforce, so that you can create Leads and update Contacts. We'll explain how this works in 4 simple steps:
Once you connect to Salesforce the Settings > Lead Mapping section of the Qualified application is where you'll configure your Salesforce data mappings. Many implementations start by mapping a basic set of information to Salesforce for the purpose of Lead creation or Lead creation and subsequent conversion into an Account, Contact, and Opportunity. Let's start with the most basic required fields in Salesforce, such as name, email and company. You'll notice when you first open this page your Lead fields are dynamically pulled in as these are the fields by default required by Salesforce to create a Lead. 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, you can create it on the fly by selecting "Create Field" in the drop down menu.
What's a data type? It is the "type" of data that 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.
In Salesforce it's pretty common for fields like "Company Size" or "Industry" to have a default set of values set by your Salesforce administrator. 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:
There are some Salesforce fields that we cannot map into at this time:
Mapping to a checkbox can be a bit more complex than other data fields as it is always either true or untrue (checked or unchecked) and can often be the thing that triggers workflows within your Salesforce instance.
Before mapping your checkbox you'll want to notice two options during the data mapping process: Default value or Fixed value. A default value will allow for you to map in 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 for you to always override whatever is in the field in Salesforce with a pre-determined 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 has been created or updated in Salesforce you must then select 'true' as your fixed value.
It's a common practice to have some field values hard coded when creating Leads in Salesforce. Meaning, you don't want your sales reps to set these values manually, but you want the system to set them based on your rules. The most common of these fields on the Lead object is Lead Source. Setting a hard coded (or "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.
You've just learned how to map data from Qualified to Salesforce, so that when your sales reps use the application, they can create Leads, or create and convert a Lead into an Account, Contact, and Opportunity. We've also explored how to map hidden fields into Salesforce for reporting purposes by your sales and marketing managers.
As a next step in your education, you might find the following guides useful