Field mappings determine which Cognism data is transferred into Pipedrive when People and Organisations are exported. You can customise these mappings to match your Pipedrive data model and control how existing records are updated.

Field mappings are configured centrally in the Cognism Web Application and apply to all users in your organisation.

Before you begin

Before configuring field mappings:

You must be a Cognism Administrator.
The Pipedrive integration must already be connected.
You must be signed in to Pipedrive.

Open the field mapping settings

Click your profile avatar.
Select Settings.
Open Integrations.
Locate Pipedrive.
Click the Settings (cog) icon next to Log Out.

From here, you can configure your General Settings, Person mappings, Organisation mappings, and Activity mappings.

General Settings

The General tab controls how Cognism handles existing records during export.

Update Rules

You can choose whether Cognism should:

Update existing People when a matching record is found.
Update existing Organisations when a matching record is found.

These settings help prevent duplicate records while keeping your Pipedrive data up to date.

Person Field Mappings

The Person tab allows you to map Cognism contact data to Pipedrive Person fields.

You can map Cognism fields to both standard and custom Pipedrive fields.

For example, we recommend creating a custom field such as cognism_source to identify records created through Cognism.

Organisation Field Mappings

The Organisation tab controls how Cognism company data is exported into Pipedrive Organisations.

You can configure mappings for standard and custom Organisation fields to ensure company information is populated according to your CRM requirements.

Activity Field Mappings

For Engage users, the Activity tab allows campaign activities to be synchronised with Pipedrive.

You can configure how Cognism campaign activities map to the activity fields available in your Pipedrive account.

If you do not use Engage, you can leave these mappings unchanged.

Save your changes

After configuring your mappings:

Review your Person, Organisation, and Activity mappings.
Click Save Changes.

All future exports will use the configured mappings until they are updated again.

Best practice

Before making the integration available to all users:

Review all Person and Organisation mappings.
Confirm that mapped Cognism fields correspond to the correct Pipedrive fields.
Create custom fields where appropriate (for example, cognism_source).
Configure Activity mappings if your organisation uses Engage.
Test the configuration by exporting a small number of records.
Verify that the exported data appears correctly before performing large exports.