Support Portal & Knowledge Base

The Salesforce integration field mapping pages allow you to specify the flow of data between Channeltivity and your Salesforce CRM for the following integrations:

• Deal Registration 
• Lead Distribution 
• Referral Integration
• Partner Sync
  
  

This article explains how to set up field mappings and the different mapping options.

Each mapping consists of a Channeltivity field and a Salesforce field connected by a button with arrows. The arrows indicate the data flow/sync direction for the field mapping.  

You can create new field mappings by clicking the "Add Mapping" button and manage existing mappings by clicking on the buttons with the arrows.

There are two types of field mappings: 

• Field to Field 
• Fixed Value to Salesforce Field - populate a Salesforce field with a constant value.

When creating "Field to Field" mappings, you select the fields in Channeltivity and Salesforce that you want to map, and if the field does not yet exist in Salesforce, you can create it in Salesforce by clicking the "Create New Field" button.

By default, new Field to Field mappings will sync bi-directionally, but you can select the  "Advanced Mode" checkbox to reveal other data flow options. The Advanced Mode feature is also used to update existing field mappings.

"Fixed Value" field mappings can be used to populate a Salesforce field with a constant value. For example, you can have Channeltivity set the Source field on the Lead in Salesforce to a specific value when a Deal is pushed to Salesforce as a Lead.  

Field Mapping Keys

Each integration has its own set of data flow options, and the buttons between the mapped fields indicate the data flow for the mapping. You can use the below key to help you identify the sync direction/data flow for your field mappings. Some general rules apply:

• Buttons are white be default. If you select the "Advanced mode" for the mapping, the button will be light yellow.
• A single arrow indicates that field data flows in the same direction when a record is Created (initial sync) and Updated (changes).
• When there are multiple arrows on the button, the top one indicates the data flow when a record is Created. The bottom arrow shows how field data flows when records are Updated.

Deal Registration: 

New Deals are pushed into Salesforce as Leads, and the Deal Registration field mappings allow you to determine the data flow between Channeltivity and the Lead object in Salesforce. You can also map fields to and from the Opportunity object in Salesforce to capture any updates made to the record once it's converted to an Opportunity in Salesforce.  Learn more about the Salesforce Deal Registration integration here. 

1. Bi-directional data flow (Two-Way Sync): This is the default for new mappings. 

• Created: Channeltivity field data is pushed to Salesforce during the initial sync/creation of the record in Salesforce.
• Updated: Any changes made in either system will flow into the other during a sync.
  
  

2. Channeltivity field data is pushed to Salesforce for the initial sync/creation of the record in Salesforce and one-way after the initial sync/creation of the record.

• Created: Channeltivity field data is only pushed to Salesforce during the initial sync/creation of the record in Salesforce. 
• Updated: Updates made to the field in Salesforce after the initial sync are pushed to Channeltivity, making Salesforce the master on future syncs.

3. Data flows in one direction. 

• Created: Nothing happens in Channeltivity.
• Updated: Salesforce data flows into Channeltivity when a change is made to the record in Salesforce, making Salesforce the master on future syncs.
  
  

4. Data flows in one direction.

• Created: Channeltivity field data is pushed to Salesforce during the initial sync/creation of the record in Salesforce.
• Updated:  Updates made to the field in Channeltivity are pushed to Salesforce, making Channeltivity the master on future syncs.

Lead Distribution:  

Salesforce Leads and Opportunities are imported into Channeltivity as Leads, and the Lead Distribution field mappings allow you to determine the data flow between Channeltivity and the Lead and Opportunity objects in Salesforce.  Learn more about the Salesforce Lead Distribution integration here. 

1. Bi-directional data flow (Two-Way Sync): This is the default for new mappings. 

• Created: Salesforce field data is pushed to Channeltivity during the initial sync/creation of the record in Channeltivity.
• Updated: Any changes made in either system will flow into the other during a sync.
  
  

2. Salesforce field data flows into Channeltivity for the initial sync/creation of the record in Channeltivity and one-way after the initial sync/creation of the record.

• Created: Salesforce field data is only pushed to Channeltivity during the initial sync/creation of the record in Channeltivity.  
• Updated: Updates made to the field in Channeltivity after the initial sync are pushed to Salesforce, making Channeltivity the master on future syncs.
  
  

3. Data flows in one direction. 

• Created: Salesforce field data is pushed to Channeltivity during the initial sync/creation of the record in Channeltivity. 
• Updated: Updates made to the field in Salesforce after the initial sync are pushed to Channeltivity, making Salesforce the master on future syncs. 

4. Data flows in one direction. Salesforce field data is pushed into Channeltivity when the record is created. Nothing happens in either system when the record is updated. 

• Created: Salesforce field data is pushed to Channeltivity during the initial sync/creation of the record.  
• Updated: Nothing happens in either system when the field is updated. 

Referral Integration: 

Referrals are pushed into Salesforce as Leads, and the Referral Integration field mappings allow you to determine the data flow between Channeltivity and the Lead object in Salesforce. You can also map fields to and from the Opportunity object in Salesforce to capture any updates made to the record once it's converted to an Opportunity in Salesforce.  Learn more about the Salesforce Referral integration here. 

1. Bi-directional data flow (Two-Way Sync): This is the default for new mappings. 

• Created: Channeltivity field data is pushed to Salesforce during the initial sync/creation of the record in Salesforce.
• Updated: Any changes made in either system will flow into the other during a sync.
  
  

2. Channeltivity field data is pushed to Salesforce for the initial sync/creation of the record in Salesforce and one-way after the initial sync/creation of the record.

• Created: Channeltivity field data is only pushed to Salesforce during the initial sync/creation of the record in Salesforce.
• Updated: Updates made to the field in Salesforce after the initial sync are pushed to Channeltivity, making Salesforce the master on future syncs.

3. Data flows in one direction. 

• Created: Nothing happens in Channeltivity.
• Updated: Salesforce data flows into Channeltivity when a change is made to the record in Salesforce, making Salesforce the master on future syncs.
  
  

4. Data flows in one direction.

• Created: Channeltivity field data is pushed to Salesforce during the initial sync/creation of the record in Salesforce. 
• Updated: Updates made to the field in Channeltivity are pushed to Salesforce, making Channeltivity the master on future syncs.
  
  

Partner Sync:

With Partner Sync activated, creating a Partner Organizations (or Partner User) in Channeltivity will create a linked Salesforce Account (or Contact) in Salesforce and vice versa and keep those records synchronized. The Partner Sync field mappings allow you to determine the data flow between Channeltivity and the Account and Contact objects in Salesforce when records are created and updated. Learn more about the Salesforce Partner Sync integration here. 

1. Bi-directional data flow (Two-Way Sync): This is the default for new mappings. 

• Created: Channeltivity and Salesforce data are pushed during the initial sync/creation of the record.
• Updated: Any changes made in either system will flow into the other during a sync.
  
  

2. Data flows in both directions for the initial sync/creation of the record and one-way after the initial sync/creation of the record. 

• Created: Channeltivity and Salesforce data are pushed during the initial sync/creation of the record.
• Updated: Updates made to the field in Channeltivity are pushed to Salesforce after the initial sync making Channeltivity the master on future syncs.  

3. Data flows in one direction.  

• Created: Channeltivity data flows into Salesforce when the record is created in Salesforce.
• Updated: Updates made to the field in Channeltivity are pushed to Salesforce, making Channeltivity the master on future syncs.
  
  

4. Data flows in one direction.   

• Created: Salesforce field data is pushed into Channeltivity during the initial sync/creation of the record.
• Updated: Updates made to the field in Salesforce are pushed to Channeltivity, making Salesforce the master on future syncs.
  
  

5. Data flows in both directions for the initial sync/creation of the record.

• Created: Channeltivity and Salesforce data are pushed during the initial sync/creation of the record.
• Updated: Nothing happens in either system when the field is updated. 

Note: The Partner Sync integration is a true bi-directional sync, allowing the creation of new entities in both systems and the transfer of field updates between systems. Therefore, in order for the integration to operate successfully, fields required in one system must also be required in the other system and mapped to a corresponding value in the other system. The fields must also be configured to sync bi-directionally for the initial creation to avoid sync errors when creating new entities in the other system.