Skip to main content
Gainsight Inc.

Load to People Action Type (Beta)

Gainsight NXT


Note - BETA Article

Please note that this is a BETA document. You might notice changes in the final version of this document.

If you have any feedback, feel free to share with us at


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


Gainsight recommends reading the configuration of the Rules Details, Data Setup, and Schedule steps before reading this article. For more information, refer to the Create New Rule section of the Rules Engine Horizon Experience Overview article.

The Gainsight People 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 People Object Model, refer to the Gainsight Person Object Model article.

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. 

Data Setup can be achieved using the following two methods:

  • Select an Object: The data is ready to use and is stored in a single object.
  • Prepare Dataset: The objects are brought from different sources, transformed and merged.


To configure Load to People action type: 

  1. In the Action Setup step, hover over the dataset. The Add Action icon appears.

  2. Click the Add Action icon. The  Add Criteria slide-out panel appears.
  3. (Optional) Click Add Criteria to define criteria for the dataset before the action is run.
  1. Click Continue to navigate to the Add Actions step.
  2. From the Create Action drop-down list, select the Load to People action type.
  3. Select one of the following Operation options:
  • Update: This operation updates the existing records in the Person, Company Person, and Relationship Person objects. 
  • Upsert: This operation updates the existing records. If there are no matching records, new records are created.
  1. (Optional) Enter a description in the Description field.
  2. Click Add Source Fields to add fields from the source object. Since the Data Setup selected is Select an Object , you need to add the source fields.
  1. Select a mapping option from the following three options: 

    • Person Mapping: In the Person Mapping 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.
      In the following image the resolution key considered is email.

    • Company Person Mapping: In the Company Person Mapping section, click Define Lookup to map the company name.


    • Relationship Person Mapping: In the Relationship Person Mapping section, click Define Lookup to map the relationship name.


Note: Any values you select for Target Fields can be removed by clicking x.

  1. Click Save Actions to save the Action and run the rule. 

Note: If the Data Setup option selected is Prepare Dataset, then the fields you selected while preparing the dataset will be available while configuring the actions.

Upgrade to Microservices Architecture

Rules Engine is being upgraded to Micro-services architecture including the Load to People action. Although the functionality, such as configuring the Load to persons action, is unaffected, Gainsight has revised the status for data ingestion in case of duplicate records. Going forward, if duplicate records are encountered during data ingestion(into the Person, Company Person and Relationship Person objects), the status shown will be “Partial Success” and the error log file shows the list of duplicate records . However, functionally processing remains the same as before, only the unique records get ingested and duplicate records get discarded. Therefore you might encounter cases where despite not making any changes to the rules, the status reflected can be “Partial Success”. 

For example: Assume the following person record exists, John Smith with email as the unique identifier.If this record isn’t available in the Person object, the record will be ingested as it is unless there are other validations blocking it. 

Continuing with the above example, suppose, John Smith is associated with an account, Acme.In the next data load, John Smith will be rejected for insertion in the person object but will get inserted in the company person object.The job status in the above case will be Partial success as insertion in the person object failed. 

  • Was this article helpful?