Learn how to set up Salesloft field mappings in Cognism to control exports, map data accurately, and manage update behaviour.
This article explains how to map Cognism contact and company data to the correct fields in Salesloft.
By configuring field mappings and match handling rules, you can ensure accurate data exports, consistent records, and better alignment with your sales engagement workflows.
Field mappings apply to exports from both the Cognism web application and the Cognism Chrome Extension.
Prerequisites
Before you start, you should:
- Be a Cognism admin
- Have Salesloft connected to Cognism
- Have completed the Salesloft integration setup
- Understand how you want Cognism data to appear in Salesloft
Open Salesloft field mapping settings
- In Cognism, go to the setting pages and click Integrations in the left-hand menu.
- Select Salesloft.
- Click Setup or Configure.
- Follow the setup flow until you reach Map Data Fields
Field mappings are configured during the Salesforce integration setup process, or can be updated later using the Configure button.
Configure general export behaviour
Use the Field Mapping step to control what happens when Cognism exports data to Salesloft and finds existing records.
Match handling
When a matching person or account is detected in Salesloft, you can choose to:
- Update the existing person
- Update the related account
- Update both the person and the account
These settings apply when exporting both new and existing data.
Map person fields
Use the Person step to map Cognism contact data to Salesloft person fields.
For each Cognism field, select the Salesloft field you want to map it to from the dropdown.
Available person mappings
A Salesloft person record is created with the following data, where available:
| Cognism field | Description |
|---|---|
| Person’s email address | |
| First name | Person’s first name |
| Last name | Person’s last name |
| Mobile phone | Person’s mobile number |
| Home phone | Person’s home phone number |
| Office phone | Person’s office phone number |
| Company | Person’s company name |
| Job title | Person’s job title |
| Job seniority | Person’s seniority level |
| Industry | Industry the person works in |
| Personal LinkedIn URL | Person’s LinkedIn profile |
| Personal Twitter handle | Person’s Twitter handle |
| Person location | City, state, country, and time zone |
| Work location | City, state, and country |
| Company website | Company website |
| Do Not Call | DNC status based on national registers |
| Owner | Set to the exporting user by default |
Map account fields
Use the Account step to map Cognism company data to Salesloft account fields.
Available account mappings
A Salesloft account record is created with the following data, where available:
| Cognism field | Description |
|---|---|
| Account name | Company name |
| Domain | Company domain |
| Conversational name | Company conversational name |
| Website | Company website |
| Company size | Employee count |
| Industry | Company industry |
| LinkedIn URL | Company LinkedIn profile |
| Company type | Organisation type |
| Location | Street, city, state, postcode, and country |
| Locale | Company locale |
| Phone | Company phone number |
| Year founded | Year the company was founded |
Use static value mappings
Additional mappings let you populate Salesloft fields with static values.
Static values apply the same value to every exported record. A common use case is setting a default owner or source value.
If you want to use a different owner for newly created people or accounts, you can:
- Configure default ownership rules in Salesloft, or
- Set a static value mapping in Cognism
Expected results
After configuring Salesloft field mappings:
- Cognism exports people and accounts to the correct Salesloft fields
- Existing records are updated based on your match handling rules
- Static values are applied consistently to all exports
Next steps
- Test exports with a small number of records
- Review match handling to avoid unintended updates
- Align field mappings with your Salesloft data standards
Comments
Article is closed for comments.