Skip to main content
Gainsight Inc.

People Management

Introduction

Gainsight Person model is used to store unique records to represent people in the real world. The Gainsight Person model uniquely identifies a Person across all of their associated Companies and Relationships.

Let’s consider a person named John Smith who works at Acme and look at the attributes that you would like to store about John. The attributes can be divided into three categories:

  1. The personal attributes of John like his Name, Email, Mobile phone, Twitter profile, LinkedIn profile, etc.
  2. The associated details of John while working at Acme (in the context of Company) that includes Company name, Title/Designation, Office phone, Manager, etc.
  3. The attributes of John associated with a Relationship at Acme, like a project implementation or business unit. In this scenario, the attributes might include Role, etc. To learn more about the context of Relationships in Gainsight, refer Relationships Overview.

The above three categories of attributes are stored in the Person model as per configuration in the following sections in this channel:

  1. Person Mapping
  2. Associate to People to Companies
  3. Associate People to Relationships

This article walks you through how you can insert people and their associated details of Company or Relationship into the Gainsight Person model.

Use Case: If the integration with any external system (like SFDC Connector, PX Connector) is not available with Gainsight to sync/fetch Company Person data into Gainsight, you can download people data from the external system through a CSV file and upload from the Person Configuration page. This people data is used across Gainsight, including the People Maps. For Example, you can download Org chart from Lucid Chart through a CSV file, and upload to Gainsight from this page to populate the Org chart in the People Maps.

Prerequisites

Make sure that the company and relationship records that you want to associate with person records are inserted into the Gainsight Company and Relationship objects respectively.

Upload Person Records

To insert Person records into the Gainsight Person model, Navigate to Administration > Person > UPLOAD tab. You can see four sections on this page:

  1. Upload CSV File
  2. Person Mapping
  3. Associate People To Companies
  4. Associate People To Relationships

Upload CSV File

To upload person records from the CSV file:

  1. Navigate to Administration > Person > UPLOAD.
  2. In the Upload CSV section, click Download a sample CSV to view the required fields to download and view the sample CSV which has the required headers. This sample CSV file helps you identify the mandatory and optional headers required in a CSV file to upload person records with association details of Company and Relationship. The headers in the CSV file are shown below:
  • First Name
  • Last Name
  • Name: The combined first and last name of the person being added.
  • Email
  • Company Name
  • Role

Below is a sample CSV file with headers that you can use to insert person records (as shown) with associated details of Company and Relationship into the Gainsight Person model.

1.CSV Header.png

Fields that are selected in the Person Resolution Key Configuration should be added as headers in the CSV file. For the Name header, you can either include it, or include First Name or Last Name. If you do not provide any of the aforementioned headers, you will not be able to proceed from the person mappings section.

Notes:

  • Gainsight supports inserting 5000 records in a single CSV upload.
  • You can choose to associate People with one or more Companies and Relationships. This can be accomplished by duplicating People data within the CSV along with varying Company data. An example of this is available in the sample CSV shown above.
  • You can add people in the CSV file that are already existing in the person object but with different Company or Relationship association details to load records into the Company Person or Relationship Person object.
  • You will begin job configuration by mapping fields to create unique People records.
  1. After configuring your source CSV file, click BROWSE to select a file from your local machine and to upload. The same CSV headers are used for mapping with fields in the Gainsight Person model in the Person Mapping Section.

    Note: Ensure that the CSV file name does not have any spaces.

2.png

  1. CSV Properties: Select appropriate CSV Properties. Recommended CSV properties:
  • Character Encoding: UTF-8
  • Quote Char: “ (Double Quote)
  • Separator: , (Comma)
  • Header Line: 1 (Mandatory)
  • Escape Char: Backslash
  • Multi select separator: Semicolon

Notes:

  • Person Configuration page always supports the files which are encoded with UTF-8 only.
  • Header Line is always 1, this field informs that 1st line in the CSV file is considered as Header for field mappings in the job configuration.
  • User should use the same separator for field values in the job configuration which is used in the CSV file to upload. By default, (comma) is selected as the separator for field values but users can change it as required.
  • Quote Character is used to import a value (along with special characters) specified in the Quotation while importing data. It is recommended to use the same Quote Character in the job configuration which is used in the CSV file to upload. By default, Double Quote is selected in the job configuration but users can change to Single Quote as required.
  • Escape character is used to include special character in the value. By default, Backslash is used as Escape Character before special character in the value. It is recommended to use Backslash in CSV file to avoid any discrepancy in the data after loading.
  • Multi select separator is a separator for multiple items in a multi select dropdown list field. Users should use the same separator in the job configuration which is used in the CSV file to upload. By default ; (Semicolon) is selected as the separator for the multi select dropdown list items but users can change it as required.
  1. Click SHOW PERSON MAPPING. Person Mapping section appears.

3.SHOW PERSON MAPPING.png

Person Mapping Section

To configure the Person Mappings:

  1. In the Person Mappings section, mapping following CSV headers to the Person object fields is mandatory:
  • Fields that are selected as Keys in the Person Resolution Key Configuration
  • First Name, or Last Name, or Name. Mapping any one of these CSV headers to the respective fields is mandatory. If you map First Name and/or Last Name with Person fields, values in the Name field is automatically populated.
  1. In the Mapping section, map required CSV headers with Target Fields appropriately.
  2. Click REVIEW PEOPLE to open the Review People section.

4.REVIEW PEOPLE.png

Review People Section

To review people identified for adding into the Gainsight system: 

  1. Review the new Person records added from the CSV under the New Records section. You can see entries from the CSV that already exist as Person records under the Existing Records section.
  2. Click ADD PEOPLE under the New Records to add them to Gainsight Person. Associate People To Companies section appears.

5.People To Companies.png

Click ASSOCIATE PEOPLE TO COMPANIES to proceed with associating these new/existing people to companies in Gainsight.

Associate People to Companies

Here you can establish associations of newly added or existing person records with companies in Gainsight.

Mapping

Configure the required mappings between the source CSV headers and the Target Fields in this section. This mapping results in populating values from the mapped CSV headers to target fields.

6.Mapping.png

Lookup Mapping

Mapping Company ID is mandatory while establishing an association of a person with a company in Gainsight. You can configure Company ID (GSID) configuration using derived mappings in the Lookup Mapping section. Using Direct import lookup, you can ingest GSIDs from the Company object into the Company ID (GSID) field. This is to lookup to the Company object and match one or more CSV headers with one or more fields in the Company object and fetch Gainsight ID (GSID) of a Company record into Company ID field. For more information on this configuration, refer Data Import Lookup.

To perform Lookup mapping for Company ID:

  1. Click Import Lookup button in the Lookup Mapping section. Data import lookup Configuration dialog appears.

7.Import Lookup.png

  1. Configure the Data import lookup as shown below:
  • Lookup type: Select Direct. Lookup for Company ID is always Direct. You can change this to Self in the custom lookup field mappings. (When you add new lookup mappings by clicking +FIELD MAPPINGS)
  • From: Company object is selected by default. You can select any other object in the custom lookup field mappings.
  • To Target field: Company ID field is selected by default. You can select any other field in the custom lookup field mappings.
  • Match by: Company Name in the CSV file with Name in Company object. Click ADD ANOTHER to add another field to match. You can add up to six headers to fields matching.
  • Select the appropriate options in When multiple match and When no match found. These options are selected by default for Company ID field mapping. You can change them to other options in the custom lookup field mappings.

8.custom lookup field.png

  1. Click APPLY to save this configuration. New person records are now associated with companies in Gainsight according to your lookup configuration.
  2. Click + FIELD MAPPING to add another custom lookup field mapping of a person associated with a Company.

9.FIELD MAPPING.png

  1. Click PREVIEW to view the Person records that are associated to Companies in Gainsight. You can see multiple companies if there are multiple company associations for a person.

10.Preview.png

Click ASSOCIATE PEOPLE TO RELATIONSHIPS to proceed associating these new / existing  people to Relationships in Gainsight.

Associate People to Relationships

If you have Relationships enabled in your org, you can establish associations of newly added or existing people with Relationships in Gainsight. This section is not applicable if you do not have Relationships enabled or if you do not want to associate people to Relationships.

Mapping

Configure the required mappings between the source CSV headers and the Target Fields in this section. This mapping results into populating values from the mapped CSV headers to target fields.

11.headers to target fields.png

Lookup Mapping

Mapping Relationship ID is mandatory while establishing an association of a person with a Relationship in Gainsight. You can configure Relationship ID (GSID) configuration using derived mappings in the Lookup Mapping section. Using Direct import lookup, you can ingest GSIDs from the Relationship object into the Relationship ID (GSID) field. This is to lookup to the Relationship object and match one or more CSV headers with one or more fields in the Relationship object and fetch Gainsight ID (GSID) of a Relationship record into Relationship ID field. For more information on this configuration, refer Data Import Lookup.

To perform Lookup mapping for Relationship ID:

  1. Click Import Lookup button in the Lookup Mapping section. Data import lookup Configuration dialog appears.

12.Import Lookup.png

  1. Configure the Data import lookup as shown below:
  • Lookup type: Select Direct. Lookup for Relationship ID is always Direct. You can change this to Self in the custom lookup field mappings. (When you add new lookup mappings by clicking +FIELD MAPPINGS)
  • From: Relationship object is selected by default. You can select any other object in the custom lookup field mappings.
  • To Target field: Relationship ID field is selected by default. You can select any other field in the custom lookup field mappings.
  • Match by: Relationship Name in the CSV file with Name in the Relationship object. Click ADD ANOTHER to add another field to match. You can add up to six headers to fields matching.
  • Select the appropriate options in When multiple match and When no match found. These options are selected by default for Relationship ID field mapping. You can change them to other options in the custom lookup field mappings only.

13.Data Import Lookup.png

  1. Click APPLY to save this configuration.
  2. Click + FIELD MAPPING to add another custom lookup field mapping of a person associated with a Company.

14.Field Mapping.png

  1. Click PREVIEW to view the Person records that are associated to Relationships in Gainsight. You can see multiple relationships if there are multiple relationship associations to a person.

15.Preview.png

  1. Click ASSOCIATE RELATIONSHIPS to complete associating the person records to Relationships in Gainsight.

Resolution Key Configuration

Admins can select unique identifiers known as Resolution keys for person records from the fields of the Person object. These keys are used to identify unique Person records in Gainsight, while inserting new records or updating existing records in the Person object, through any data ingestion channel in Gainsight. These keys are honored across all of the Gainsight data ingestion channels, such as Salesforce Connector, Bulk Person upload through CSV, uploading People through Rules, etc.

Use case: Customers may be using other attributes (Ex: External Id) besides Email to identify contacts in other systems, and may want to apply the same configuration in Gainsight to identify person records. Admins can use any field from the Person object as the Resolution key.

There are major sections in the Resolution Key Configuration:

  1. Select Field: Add fields from the Person object to identify Resolution keys.

  2. Check Dependencies: This page displays the list of all the dependent ingestion channels into the Persons object (Ex: Upload People through CSV, multiple Rules with Load to People Action, Salesforce Connector, etc.)

  3. Review Data: If there are any duplicate person records found while checking in the system, this page shows the Download button to download the duplicate records in a CSV file. You can check the duplicate person records in the CSV file and navigate to the Data Operations page, either to delete or edit them. If the person records are synced from SFDC Contact object through Salesforce Connector, It is strongly recommended to edit or delete the person records at the source (SFDC) to prevent overwriting the changes in Gainsight.

To configure unique identifiers for person records:

  1. Navigate to the Administration > Person > RESOLUTION KEY CONFIGURATION.
  2. Drag and drop fields from the Available Fields section to the Selected Fields section.

Notes:

  • Fields that you see in the Available Fields section are from the Gainsight Person object.
  • The email field is selected by default as the Resolution key.

  • You can add a maximum of three fields as unique identifiers.

  • The operator between the unique identifiers is always AND. This means, if you add two or three unique identifiers, Gainsight person records are uniquely identified only if the combination of values in the two or three fields is unique.

Resolution Key 1.png

  1. Click Continue. The Check Dependencies page is displayed to show all of the data jobs/rules ingesting Person records into Gainsight. (Ex: Upload People through CSV, multiple Rules with Load to People Action, Salesforce Connector, Reports on the Person object, etc.)

Resolution Key 2.png

Notes:

  • The Check Dependencies page displays all of the Reports on the Person object. You can check whether these Reports have been grouped on the previous resolution key and should be corrected to group on the updated resolution keys. This configuration change on the Reports helps generate accurate reports, as required.
  • After changing the resolution keys, you should add new resolution keys in the field mappings of the Rule configuration, otherwise, these rules will fail in the next scheduled execution.
  1. Click Continue. You are navigated to the Review Data page which shows the Download button, if there are any duplicate person records identified per latest resolution keys. System takes some time to check duplicate records depending on the amount of person records in Gainsight and shows the Download button.
  2. Click Download to get the duplicate person records through a CSV file.

Resolution Key 3.png

  1. Check the duplicate person records in the CSV file and navigate to the Data Operations page either to delete or edit the duplicate Person records. For more information, refer to the Data Operations article.

Note: If the person records are synced from SFDC Contact object through Salesforce Connector, it is strongly recommended to edit or delete the person records at the source (SFDC) to prevent overwriting the changes in Gainsight.

  1. After the duplicate records are either deleted or updated, perform the actions 1 thru 4 again to see if there are any duplicate records still existing.
  2. Click Save to complete the configuration and save updated resolution keys.

Resolution Key 4.png

  1. Navigate to the dependent ingestion channels (respective rules and Salesforce Connector data jobs) and add the latest resolution keys to the field mappings.

Note: Once the Resolution keys are configured, existing data jobs/rules in the dependent ingestion channels will be failed, if the latest unique identifiers are not added to the field mappings.

  • Was this article helpful?