Skip to main content
Gainsight Inc.

Load to People Action Type

Gainsight NXT

This article supports Gainsight NXT, the next evolution of the Customer Success platform. If you are using Gainsight CS Salesforce Edition, you can find supporting documentation by visiting the home page, and selecting CS > Salesforce Edition.

Not sure what your team is using? Click here.

 

Overview

Gainsight Person model stores unique records to represent people in the real world. This model stores person details and attributes of these people in association with a company or Relationship. For more information about the Gainsight Person Object Model, refer the Gainsight Person Object Model article.

This article explains how to use the Load to People Action Type to load data into the Person, Company Person, and Relationship Person objects. 

Note: Gainsight recommends to sync data from SFDC Contact into Gainsight Company Person through the Salesforce Connector out of the box Company Person Sync job. For more information, refer to the Salesforce Connector > Company Person Sync Job article.

Prerequisites

  • The data required to use this Action type is present in a CSV file and is imported by using an S3 Dataset in Rules Engine.
  • The CSV file has all the required fields (Email, Account Name, and SFDC Relationship ID).
  • The source dataset or CSV must have the fields that are identified as resolution keys in the Person Resolution Key Configuration. These field are used in identifying them as upsert keys and in mapping fields in the Load to People action type. 

Load Data to Rules Engine

You can load data into Rules engine from any of the following channels. 

  • Any Gainsight custom object: If your Data is present in a custom object, create a dataset to fetch data from the custom object. For more information on how to create a dataset, refer the Fetch Data section of the Folder and Tasks Creation article.
  • S3 Dataset Task:  If you store your business contacts data in a csv file and upload into any S3 bucket, you can create a dataset by fetching data in this csv file. For the detailed instructions on how to create a dataset from a csv file in the S3 bucket, see the S3 Dataset Task in Rules Engine article.

In this article, it is assumed that data is loaded to Rules engine from an S3 dataset. 

Setup Action: Load To People

This section explains how to configure the Load to People Action type. This example ingests data into Person, Company Person, and Relationship Person. However, you can also ingest data only to the Person object or only to the Person and Company Person objects. 

To configure the action type: 

  1. Navigate to the Setup Action page.
  2. Click + ACTION and select the name of your Dataset (Here S3 Dataset).
  3. From the Action drop-down menu, select Load to Action
  4. (Optional) Enter a description in the Description field.

1..GIF

  1. Select Update or Upsert as the Operation. Update operation helps to update the existing records in the Person, Company Person, and Relationship Person objects whereas Upsert operation updates the existing records as well as creates new records, if matching records are not found.
  2. In the Person section, map the fields that are identified as Resolution keys in the Person Resolution Key Configuration. There can be one or multiple resolution keys used for the identification of people in Gainsight. For more information on the Person Resolution Key configuration, refer to the People Management article.

Note: As soon as you perform field mappings for the resolution keys, they are automatically selected as Include in Identifiers.

2..GIF

  1. Perform other field mappings as required.

3..GIF

  1. In the Company Association section (associates Person with a Company), apply the following configurations in derived mappings:
    1. Click the Import Lookup icon in the Actions column for the Company ID target field. The Data import lookup configuration window appears.
    2. Configure the import lookup as explained below:
      1. Lookup Type: Direct
      2. From: Select Company
      3. For field matching between source and lookup objects, select Account Name and Name, in the Source dataset and lookup object (Company) respectively.

Account Name field represents the name of a company and it is a field to store company data in the dataset. When values in the Account Name field in the source S3 dataset and Name field in the lookup object (Company) match, it populates GSID from the Contact object to Company ID field in the Company Person object

Notes: 

  • Field name Account Name is used in the S3 dataset just for reference only,  you can create a field with different name.
  • You can also use other fields for mapping in the Derived mappings section. Gainsight supports upto six fields for mapping.
  • The derived mapping section is mandatory, to associate a Person to a Company.
  1. (Optional) Click ADD ANOTHER to add multiple fields matching.
  2. Select the option Reject record option from the  When no matches are found drop-down menu. If you choose other option, you may get undesired results.
  3. Select the Use any one match or Mark record with an error option from the When multiple matches occur drop-down menu.
  4. Click Apply.

4..GIF

  1. Perform other mappings as required.  
  2.  In the Relationship Association section, apply the following configurations in derived mappings:
    1. Click the Import Lookup icon in the actions column for Relationship ID target field. The Data import lookup configuration window appears.
    2. Configure the Import Lookup section as explained below.
      1. Lookup Type: Direct
      2. Populate GSID From: Select Relationship
      3. For field matching between source and lookup objects, select Relationship from the S3 dataset and SFDC Relationship Id, from lookup object (Relationship Person) respectively.
      4. (Optional) Click ADD ANOTHER to add multiple fields matching.
      5. Select either the Use any one match or Mark record with an error option from the When multiple matches occur drop-down menu. 
      6. Select the Reject record option from the When no matches are found drop-down menu. If you choose other option, you may get undesired results.
      7. Click Apply.

Note

  • It is not mandatory to map Relationship association. You must map relationship association only if you are using Relationships in your organization.  
  • It is mandatory to configure Derived Mappings, to associate a Person to a Relationship.

5. Snag_3a68ec4d.png

  1. Perform other mappings as required.
  2. Click Save.
  • Was this article helpful?