1. Help Center
  2. CRM and SEP Integrations

Recommended Integration Field Mappings

This details the fields we recommend you map to fields in your CRM, both on the account and contact level. In order to allow Rightbound to push data to your CRM you will need to setup the field mapping for each field.

Basic Fields: These are the fields that are most critical to map to your CRM to get basic data on the contact and the company level. 

Account: On the account level we recommend you DO NOT overwrite data.

  • domain
  • name
  • linkedin - Company LinkedIn link

Contact: On the contact we recommend you DO overwrite data, but use your own discretion on what you would like updated. 

  • first_name
  • last_name
  • linkedin_profile - the contact LinkedIn URL
  • emails
  • position - Job Title on LinkedIn
  • state - of the CONTACT, not company
  • country - of the CONTACT, not company
  • source - We recommend you always add a source field to map to a source or description field in your CRM with a constant value of "RightBound"
  • Mobile - Mobile 1 phone number, most important to map.
  • Mobile 2 - Second mobile phone number if available, important to map.
  • Work Phone - Office or deck phone number, next most important to map.
  • Other Phone - a flexible field that will send an additional work number if found. 

There are additional standard fields that you may find useful, but are not critical to map. These include values like industry, seniority, LinkedIn employee count, and more. It is recommended you review the available fields in the dropdown and map those you think will be useful in your CRM.

 

Recommended Custom Fields: You may need to create new fields in your CRM to map these values from RightBound. These values add information that can be essential for tracking specific use cases, and getting the most value out of RightBound enriched and verified data. 

Contact:

  • Origin Name - The name of the "CRM Insights Research" that this contact was enriched or sourced from. Recommend to send to a new custom field.
  • Persona Name - The name of the "persona" this contact was sourced from or matched for enrichment. Recommend to send to a new custom field.
  • Rightbound Created Time - Date the contact was created from RightBound.
  • Rightbound Updated Time - Date the contact was updated from RightBound.
  • Rightbound Enrichment - What type of enrichment happened (email, phone, etc)
  • Changed Company - Sends a TRUE or FALSE value if a verified contact in your CRM moved to a new account. Recommend to send to a new custom field.
    • Related to "Changed Company" are four fields to push the new company data. It is recommend you map these to new custom fields as well. These will only populate if the contact has moved to a new account from what you had in the CRM.
    • New Company Name
    • New Company Domain
    • New Company LinkedIn
    • New Company Start Date
  • New Contact Moved Company - *If having Rightbound create contacts that moved companies from contacts in your CRM. This will let you know the contact was created because they moved companies
  • Function Changed - Sends a TRUE or FALSE value if a verified contact in your CRM changed function (Example Marketing to Sales.) Recommend to send to a new custom field.
  • Seniority Changed - Sends a TRUE or FALSE value if a verified contact in your CRM changed seniority (Example Manager to Director.) Recommend to send to a new custom field.
  • Enriched - Sends a TRUE or FALSE value if RightBound enriched a contact for email or phone values when verifying and enriching in the CRM. Recommend to send to a new custom field.
  • Matched - Sends a TRUE or FALSE value if RightBound is able to match the contact in your CRM to an existing LinkedIn profile. Recommend to send to a new custom field.