The HubSpot integration field mapping pages allow you to specify the flow of data between Channeltivity and your HubSpot CRM for the Deal Registration, Lead Distribution, and Partner Sync integrations. This article reviews how to set up mappings and explains the different mapping options.

 

Each mapping consists of a Channeltivity field and a HubSpot 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. 

 

When creating a new mapping, you select the fields in Channeltivity in HubSpot that you want to map. If the field does not yet exist in HubSpot, you can create it in HubSpot by clicking the "Create New Field" button. 

 

By default, new 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. 

 

 

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 by 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:

When a Partner submits a new Deal Registration, Channeltivity creates a copy of the registered Deal in HubSpot, and the Deal Registration field mappings allow you to determine the data flow between Channeltivity and the Deal object in HubSpot. Learn more about the HubSpot 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 HubSpot during the initial sync/creation of the record in HubSpot. 
  • Updated: Any changes made in either system will flow into the other during a sync.
     

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

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

 

3. Data flows in one direction. 

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

4. Data flows in one direction.

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

 

Lead Distribution:  

HubSpot Contacts and Deals are imported into Channeltivity as Leads, and the Lead Distribution field mappings allow you to determine the data flow between Channeltivity and the Contact and Deal objects in HubSpot. Learn more about the HubSpot Lead Distribution integration here

 

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

  • Created: HubSpot 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. HubSpot 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: HubSpot 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 HubSpot, making Channeltivity the master on future syncs.
     

3. Data flows in one direction. 

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

 

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

  • Created: HubSpot 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. 

 

Partner Sync:

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

 

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

  • Created: Channeltivity and HubSpot 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 HubSpot data are pushed during the initial sync/creation of the record. 
  • Updated: Updates made to the field in Channeltivity are pushed to HubSpot after the initial sync making Channeltivity the master on future syncs.   

 

3. Data flows in one direction.  

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

4. Data flows in one direction.   

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

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

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