Conditional Mapping for CRM and SEP Integrations

Configure conditional field mappings for CRM integrations

This article explains how you can use conditional mappings to control how Cognism data maps to fields in your CRM.

Conditional mapping allows you to set up rules that decide which Cognism values go into specific CRM fields. This helps ensure your CRM data matches your internal structure and reporting requirements.

Supported CRM integrations include:

• Salesforce 
• HubSpot 
• Pipedrive 
• Bullhorn 
• Microsoft Dynamics 

What you can apply conditional rules to

You can set conditional mapping rules for the following fields:

• Industry 
• Country 
• State 
• Department 
• Seniority 
• Company type 

These rules apply when data is exported from Cognism to your CRM.

Configure conditional mappings (admin)

Only Cognism admins can configure conditional mappings.

Open CRM integration settings

1. Go to Settings > Integrations > Connected CRM > Configure

Select the object to configure

1. Select the CRM object you want to configure (for example, Leads, Contacts, or Companies). 
2. Locate the field you want to apply conditional logic to. 
3. In the Actions column, select Settings Cog.  

Define conditional mapping rules

In the Advanced view:

• Choose how Cognism field values should map to your CRM field 
• Define how different values are handled based on your rules 

These rules control which data is written to your CRM when exports occur.

Save your changes

Saving behaviour depends on your CRM:

• Salesforce 
  • Select Save in the popup window    
• All other supported CRMs 
  • Select Save in the popup  
  • Then select Save again in the bottom-right corner of the configuration page    

Your conditional mappings apply to future exports once saved.

Expected results

After configuration:

• CRM fields are populated based on your defined conditions 
• Data exports follow consistent mapping logic 
• CRM records align more closely with your internal data structure 

Next steps

• Review standard field mappings 
• Test exports to confirm expected behaviour 
• Update conditional rules as your CRM structure changes