Skip to main content
Gainsight Inc.

Gainsight Objects

Gainsight provides the following objects as part of its Data Management:

  • Standard Objects
  • Custom Objects
  • System Objects

Standard Objects

All customer orgs are provisioned with the following standard objects:

  • Company
  • User
  • Relationship
  • Relationship Type

These standard objects store important customer data like Company, Account/Relationship and user information in Gainsight's Matrix Data Architecture (MDA). This lets the users to perform actions from other functionalities in Gainsight application directly on the standard objects. For more information on the User object, refer Gainsight User Object.

You can view the standard objects in Administration > Data Management as shown in the following image.

Standard Objects1.png

A set of standard fields with predefined mappings are shipped by Gainsight. Customers can add custom fields, update schema of the custom fields, and implement Read and Join tasks (from Reporting, Journey Orchestrator, and Scorecards). Salesforce Connector helps you to import data from Salesforce to Gainsight standard and custom objects. Admins can import data into the standard objects from a CSV file through S3 Connector and Gainsight Bulk API. Admins can view and edit the existing records in the MDA standard objects Company, Relationship, and Relationship Type through Data Operation Admin page. Admins can also add new records in these standard objects through this page.  Once data is imported into the standard fields, Admins cannot delete it. 

You can load data into the Gainsight standard objects using the following different ingestion channels:

Gainsight Person

Gainsight Person is an object model that has unique records to represent people in the real world.

Let’s consider a person named John Damon who works at Acme and look at the attributes that we 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 attributes of John while working at Acme that includes Company name, Title/Designation, Office phone, Manager, etc.
  3. The attributes of John associated to a Relationship at Acme like a project implementation or business unit. In this scenario, the attributes are like Role, etc.

The above three categories of attributes are stored in the Person object model in the following three Gainsight objects:

  • Person
  • Company Person (Equivalent to Contact)
  • Relationship Person

For more information on the Gainsight Person object model, refer Gainsight Person Object Model.

You can load data into Gainsight Person through different ingestion channels, as required. For more information, refer to the Channels to ingest data into Gainsight Person article.

Standard objects have the following fields:

  Schema Editability? Data Editability?
Standard Objects Yes Yes
Standard Fields No Yes
Custom Fields Yes Yes

System Fields

  • GSID: Auto generated and unique

  • Created Date: System generated

  • Modified Date: System generated

No No


System Objects

These Objects are set up, shipped and controlled entirely by Gainsight. They are system driven and cannot be customised or modified by Admins. In these objects, neither the schema nor the data is editable. A good example for a System Object is Zendesk (support ticket data). Admins can view the system objects in Administration > Data Management.

Custom Objects

Admins can create and edit the Custom Objects and can control them. In these objects, the schema is editable and the data can be uploaded, used, and deleted. There are three system fields: GSID, GS Created Date, and GS Modified Date generated automatically in all the custom objects. These are system driven fields and cannot be customised or modified by Admins. Admins can manage the custom fields in Administration > Data Management.

You can load data into any Gainsight custom object using:

  • Was this article helpful?