Mapping data to Salesforce

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.

Start with the most basic required fields in Salesforce: name, email, and company. When you first open this page, these lead fields are already pulled in, because Salesforce requires them by default to create a lead. Select the visitor field in Qualified that will map to each Salesforce field.

If you don't see one of your Salesforce fields in this list, Qualified may not have the latest list of your Salesforce fields. Whenever you add, remove, or update Lead, Contact, Account, or Opportunity fields in Salesforce, go to Settings → Integrations → Salesforce → Connection and click Update fields at the bottom of the page.

If the field still doesn't appear, the user you've connected to Salesforce with doesn't have access to it. You can change this 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. A picklist is a more complex, and common, data type.

In Salesforce, fields like "company size" or "industry" often have a default set of values set by your Salesforce admin. When you map data into these fields, it's a good idea to allow only those values. Once you select the field from Salesforce, the mapping pulls in these values automatically:

Dependent picklists

Qualified supports mapping to dependent picklist fields on the Salesforce Lead and Contact objects. A dependent picklist is one whose available values depend on the value of another field, its controlling field.

• To use dependent picklist behavior, map both the dependent field and its controlling field.
• If you map to any of the State Code fields on the Lead or Contact object, dependent picklist behavior is required.
• Picklist values on bound fields are read-only in Qualified. To change them, update them in Salesforce and click Update fields on the Salesforce Connection page.
• Deleting the mapping also deletes the bound picklist values in Qualified.

Fields not supported

Qualified can't map to these Salesforce fields:

• Lookup fields
• Multi-select picklists
• Formula fields

Mapping checkbox data to Salesforce

Mapping to a checkbox takes more care than other data fields, because checkboxes are always true or false (checked or unchecked) and often trigger workflows in 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 (they are always true or false), in most cases you won't 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.