This article explains how admins can create a new project and configure the settings in the project.
This article explains how admins can create a new project and configure the settings in the project. Navigating to Administration > Adoption Explorer displays a list of existing Projects and also allows you to create a new project.
Create New Project
To create a Project:
- Navigate to Administration > Adoption Explorer.
- Click Create Project. To edit an existing project, click on the project name.
- In the Select Type of Project Setup pop up, select either Standard or Gainsight PX project setup type.
- Select Standard setup to ingest usage data from sources such as existing Gainsight MDA objects, Amazon S3 and Snowflake.
- Select Gainsight PX setup if you want to ingest pre-aggregated Feature usage data and Engagement data from Gainsight PX. For information on how to configure the Gainsight PX-based project, refer to the Enable Gainsight PX Data in Adoption Explorer article.
- Usage data can also be ingested from other sources after creating the project in either of the setup types.
- Click Continue.
Configure Basic Settings
To configure basic settings for a project:
In the Project Setup page, enter the name of the project.
Note: All the Objects created in this Project are stored in Data Management, and the name of the Objects start with the Project Name assigned. For example, if your project name is ABC Analytics, then the object name in Data Management is tagged with project name as ABC Analytics - Company/Person usage Info where Company/Person Time Series Daily are the out-of-the-box Adoption Explorer objects created at Company/Person level.
- In the Import usage data for section, select the option to ingest Company (Customer) and Person (User) level usage data.
- Select the granularity of usage data for Company and/or Person.
Note:If you select the Daily checkbox, the Weekly checkbox is selected automatically. Adoption Explorer rolls-up daily level usage data to weekly level.
In the Associate usage data identifier to the Gainsight record ID section, do the following:
From the Company object dropdown list, select the External ID field (a GS Company attribute) that uniquely identifies the Companies in Gainsight’s Company Object. This mapping creates a lookup for Customer identifier to the Gainsight's Company object, and resolves the external Customer/Company identifier in usage data to the Gainsight Company record.
- To enable this project in C360, External Id in the Adoption Explorer object must be mapped to the external identifier field in Gainsight's Company Object.
- Alternatively, you can also create a custom field in the Gainsight's Company object from the Data Management page, and load the external ids (customer identifier records) into that field, and then map with the External ID field in the Adoption Explorer object.
- From the Person/Company Person object dropdown list, select the Person Object or Company Person Object tab.
- Select the ID field (Person/Company Person attribute) that uniquely identifies the Person records in Gainsight’s Person/Company Person object. This mapping creates a lookup for AE PersonID to the GS Person/Company Person object, and resolves the external Person identifier in usage data to Gainsight Person/Company Person record.
Example Business Use Case: Andy works for a company called ABC as a Software Engineer, and as a consultant for XYZ company. Andy’s record with company ABC is stored in Person object but Andy’s record with company ABC and XYZ is stored in Company Person object. When you map Adoption Explorer Person identifier to Person Object, usage reports are created based on Andy’s contribution to ABC company. To get the details of a person's usage data from each company based on the person’s Role/Title in the company, map Adoption Explorer Person identifier to Company Person object.
- Select the Import usage data at instance level checkbox to ingest usage data at the instance level. Instance in Adoption Explorer refers to anything ranging from Company Subdivision, Locations, Departments, etc. For example, Gainsight is a Company, Gainsight India and Gainsight USA are the instances of Gainsight.
Note: Once the project is saved, this setting cannot be modified.
- I want to track usage data at my Company and Instance level: Select this option to track usage data at Company and Instance level in the project.
- I have one instance associated with only one company: Set the instance level with the Company. For example, ABC Inc and Goole Corp have attended Event 1, and AppleCad and MiroJec have attended Event 2. Here, not selecting this option means a single Instance (Event 1) is tied to multiple companies (ABC Inc and Goole Corp).
- Standard projects: For all the new projects in Adoption Explorer for which Instance level data is enabled, admins can select this option as required.
- Existing PX projects: This checkbox is not selected by default. To correct the default and historical data, admins must manually select this option, save, and run the project to see the new mappings.
- New PX projects: This checkbox is selected by default to ensure that an admin can select the same Parent Group ID in Gainsight CS when they resolve it in Gainsight PX. Adoption Explorer pulls the new mapping information when the project runs.
Select the Associate usage data identifier to the Gainsight relationship record ID checkbox.
From the Relationship Object dropdown, select the External ID (GS Relationship attribute) that uniquely identifies the Relationships. This mapping creates a lookup for AE InstanceID to the GS Relationship object, and resolves the Instance identifier in usage data to Gainsight Relationship record.
Note: If you are using Relationships and want to associate a Relationship to an Instance, you can map Instances in Adoption Explorer to Relationships in Gainsight. Ensure that you have already created a Relationship record per Instance, in Gainsight’s Relationship Object.
- Click Create Project. The project is created with basic settings.
Configure Advanced Settings
To configure advanced settings for an existing project, click on the project from the project listing screen. Select Edit Project Settings from the three-dot vertical menu.
You can configure the following options:
- Ingest entitlement data: Select whether to ingest entitlement data at the Company and/or Person level. The corresponding entitlement objects are created.
- Replace Null Values: Select the default values for External Company ID and External Company Name attributes. This value is used in case the value is null or not identified.
- Project Schedule: Specify the time at which the data ingestion begins from the external sources. The project schedule time is the Org time zone, and you can see the org time zone converted to the user time zone in the Schedule & Availability Info section.
- Notifications: Specify the email addresses without blank spaces in the Send Data Ingestion Success Notification To, Send Data Ingestion Failure Notification To textboxes.
- Include download link in the notification email: Select this checkbox to send download links in the notification email.
- Enter display name for the following fields:
- Company Id
- Company Name
- Person Id
- Person Name
- Instance Id
- Instance Name
Schedule & Availability Info
You can view the Schedule & Availability information in the Advanced Settings page.
Once you configure external sources in a project, all the configured data sources and the delay time in usage data availability are shown in this section.
Adoption Explorer supports the following data sources:
- Amazon S3 (S3): Usage data from S3 will be ingested into the Adoption Explorer objects in 24 hours.
- Gainsight: Usage data from Gainsight will be ingested into the Adoption Explorer objects in 24 hours.
- Google Analytics (GA): Usage data from GA is available after 48 hours, so in Adoption Explorer if any GA source is configured, data will be ingested into the Adoption Explorer objects in 72 hours.
- Salesforce (SFDC): Usage data from SFDC will be ingested into Adoption Explorer objects, in 24 hours.
- Postgres: Usage data from Postgres will be ingested into the Adoption Explorer objects in 24 hours.
- Redshift: Usage data from Redshift will be ingested into the Adoption Explorer objects in 24 hours.
- MySQL: Usage data from MySQL will be ingested into the Adoption Explorer objects in 24 hours.
- Snowflake: Usage data from Snowflake will be ingested into the Adoption Explorer objects in 24 hours.
If an Adoption Explorer object is configured with more than one data source type, schedule will happen at the farthest availability time of the data source. For example, if a Company Time Series (Daily) Object is configured with S3 and GA sources, the schedule will happen in 72 hours, as 72 hours is the farthest availability time.
This section displays an overview of the project schedule information, like:
- Last Run For Date
- Last Run Status
- Next Run For Date
- Next Schedule At (Org Time Zone converted to the User Time Zone)
Note: You can see the Schedule Info only when the project is in Active status.
RunForDate Vs ScheduleDate
- RunForDate is the date which belongs to the Usage Data. For example, if a User has viewed 10 pages on 2020-01-01 and if this information is tracked on Google Analytics, then “2020-01-01” is the RunForDate.
- ScheduleDate is the date on which the usage data from GA is ingested into the Adoption Explorer object. The maximum wait time for the usage data to be ingested into the Adoption Explorer object is 72 hours, so the schedule date will be on “2020-01-04”.
Once you have configured the project settings, you can now ingest usage data into the Adoption Explorer objects created. For information on how to ingest usage data into the Adoption Explorer objects, refer to the Configure Adoption Explorer Objects article.