Gainsight NXT Release Notes 6.22 February 2021

Ability to Fetch Adoption Explorer Logs via APIs

Gainsight now allows admins to fetch Adoption Explorer (AE) Project execution status, using Rest APIs. Prior to this release, there was no way admins could access and check the status of the AE Logs from the external systems. Sometimes, this became extremely critical for some of the customers, especially who were in the security businesses.

Example Business Use Case: All the teams who benefit from accessing AE do not always use Gainsight. Such customers expect better Gainsight integration with the systems of their choice. In such scenarios, AE APIs allow customers to access and check the AE job statuses from their external systems. Customers who have the development resources can use these APIs to build tighter and more customized integrations between Gainsight and other systems they use. 

For more information on how to fetch AE Logs via APIs, refer to the Adoption Explorer APIs article.

Summary Ribbon Widget

Adoption Explorer now added a new chart type called “Ribbon” to the chart options. This chart type allows Admins/Users to group a set of metrics in a single widget to give a summary or overview of the information. Visualization of the AE Layouts is now possible using this new chart type. 

Note: The set of metrics you can group can include both Measures and Dimensions.

To use this enhancement, navigate to Administration > Adoption Explorer > Click any project > Layouts > Usage Section >  Preview > Chart Type.

Example Business Use Case: Account overview or User overview are some of the best examples. For instance, there is a renewal up for a customer, and CSM wants to view a set of metrics such as Total Licenses, Used Licenses, and License Expiration/Renewal Date in a single widget, to get a holistic analysis of the information.

For more information on how to create a Ribbon Chart, refer to the Create Usage Section in a Layout article

Introducing Dynamic Filters in Benchmark Usage Section

In the Benchmark Usage Section, admins/users can now apply Dynamic Filter conditions on the Benchmark report other than Static Filter conditions. The benchmarking field can be anything such as the Industry, Location, ARR, Company Stage, etc. depending on the business need.

To use this enhancement, navigate to Administration > Adoption Explorer > Click any project > Layouts > Benchmark Usage Section.

Example Business Use Cases: 

• A CSM wants to filter and compare a Company’s ARR with a group of Companies ARR that fall under the same Industry.  
• A CSM wants to filter and compare a Company’s ARR with a group of Companies ARR based on the Location. 

For more information on how to apply Dynamic filter conditions on the Benchmark report, refer to the Create Usage Section in a Layout article.

Increased limit of CTA Types

Admins can now create up to 50 custom CTA Types per entity. At GLOBAL level, admins can add 45 CTA Types, apart from the five pre-configured Gainsight CTA Types. Admins can also view the count of active and inactive CTA Types. Previously, a maximum of 20 custom CTA Types was allowed by Gainsight. For more information on the limitation of CTA Types, refer to the Configure CTA Types, Reasons, Priority, Snooze article.

Ability to Create CTAs only if the Previous is Closed from Rules Engine

In the Create CTA Rule Action Type, Gainsight has now made an enhancement to avoid triggering of CTAs based on the same event.

In the Rules Engine > Create Rule > Setup Action > Call to Action 2.0 action type, when the admin selected “Create CTA once in” X days checkbox, the system triggered CTAs after X+1 days irrespective of the previously triggered CTA’s status (open/closed) due to which the CSM’s Cockpit page was piled up with several CTAs based on the same event. 

To overcome this situation, admins can now select the “Do not create the CTA if the previously created is not closed” checkbox to avoid triggering of CTAs based on the same event. For more information, refer to the Creating and Closing CTAs from Rules Engine article.

CTA No Longer Appears in ‘MY CTAs’ View When the Task Owner Closes the Assigned Task in the Same CTA

When a user is not the owner of the CTA but has closed the assigned task in that CTA, then the CTA no longer appears in 'My CTAs’ view of that particular user.  For more information about Cockpit, refer to the Cockpit List View article.

Highlight New and Unread Notifications in CI Section of C360

CSMs using Company Intelligence in the C360 section are now notified if there are any new posts available. CSMs can view the number of unread notifications highlighted in red when landed on the C360 page of the customer for which Company Intelligence is configured in C360.

However, when a CSM clicks on the Company Intelligence section, the highlighted number against the Company Intelligence section disappears immediately and the unread posts inside the Company Intelligence section in C360 are highlighted with red dots. These red dots indicate that these are the new posts and disappear only when the CSM moves to a different page.

In-App Company Intelligence Notifications

Gainsight now displays the Company Intelligence posts under In-App Notifications for the Companies that users follow. This enhancement keeps the users (CSMs, Account Managers, or Executives) informed on time so that they can take relevant action to either upsell or avoid churn.

In the My Settings > Notifications page, the On Gainsight checkbox must be selected for the Company Intelligence event to receive the in-app notifications.

Note: The in-app notifications are applicable only for the posts received through the Company Intelligence section on the C360 page.

An in-app notification contains the following details for each post:

• Type of Signal.
• Name of the Company to which the post belongs. The company name is hyperlinked to the related C360 page.  
• Title of the post which is hyperlinked to the source article.

The On Gainsight checkbox is selected and grayed out for the Company Intelligence event if the users do not opt for the Company Intelligence feature.

Gainsight App Menu in Zendesk

Gainsight App menu support is now available for the Zendesk connector (Horizon Experience). In your Zendesk org, visualize a Company’s summary, attributes, usage data, call to action, and organizational mapping in the Gainsight App menu. For more information, refer to the Gainsight App menu in Zendesk article.

Bulk Mapping of Zendesk Organizations

Bulk mapping feature is now available for the Zendesk connector (Horizon Experience). Map all the Zendesk Organizations to Gainsight Companies to automatically populate the Company name for each Zendesk ticket of a Zendesk Organization. For more information, refer to the Bulk Mapping of Zendesk Organizations to Gainsight Companies article.

Transform Data in Connector Jobs

In the Preparation step of a connector job, admins can now Transform data and Add Case Fields to get more meaningful insights from the customer data.

Example Business use case: The Transform function provides an the capability to create or modify new case fields. The new case fields can be used to modify the external field as per the consumption requirement in Gainsight’s data model. Case fields can be defined to populate different values for different case conditions. For example, External picklist values such as New, Open, and Closed can be modified to Active and Inactive to match Gainsight’s picklist values.

To transform a dataset:

1. Navigate to Administration > Connectors 2.0 > Jobs tab.
2. Click Create Job.

 

3. In the Name of the Job field, enter a name.
4. Click Next.

5. In the Data Source dropdown list , select a source.
6. Drag and drop the required object to the Preparation screen.
7. From the context menu of the dataset, click Transform.
8. Click Add Case Field.
9. In the Label field, enter the name for the case field.
10. In the Data Type field, select the data type as Boolean, Number, or String.
11. Click Case 1 to expand the view.
12. Click Add Filter to add a condition as per your requirement.
13. In the THEN field, select the field and the value to display the resultant data when the set conditions are met.
14. (Optional) Click +CASE to add another case field by following steps 3 to 7.
15. In the DEFAULT field, select a value when none of the conditions match.
16. Click Add.
17. Click Save.

Pivot Task in Data Designer

The Pivot task in Data Designer allows admins to transform the data available in a single column to multiple columns in one go, to a simplified and actionable dataset based on a scenario. Pivot task creates a column for every single data value in the table column. This enhances the data summarization process thus giving better insights into the data. Prior to this release, when admins tried to compare any data value across records, it used to take a lot of admin time in preparing the data. 

Pivot Function: Pivot rotates a table-valued expression by turning the unique values from one column in the expression into multiple columns in the output.

Key benefits of using the Pivot function:

• Summarizes data easily

• Makes data analysis easier

• Assists in finding data patterns

• Helps in making decisions faster

Note: Only one pivot can be configured per dataset. 

Example Business Use Case: A Customer Success Director wants to find patterns in CTA Type by CSM and optimize CTA Types, and so on. 

Using the Pivot function, you can directly convert the records (values) in the CTA Type Name column (single column) to multiple columns of individual CTA Type Names, grouped by CSM Name. For more information on how to Pivot on the CTA Type Name field, refer to the Pivot Task in Data Designer article.

Gainsight Introduces Data Management APIs

Admins can now fetch metadata of Gainsight Objects and Fields using Rest APIs. Customers who have the development resources can use these APIs to build tighter and more customized integrations between Gainsight and their systems/applications. For more information on how to use these APIs, refer to the Data Management APIs article.

Business Use Case: When a customer wants to integrate their application with Gainsight. The customer would want to understand how the data is stored in Gainsight, that is the structure of metadata in a Gainsight Object. Such customers can use these APIs to fetch the metadata and get an understanding of it, without logging into the Gainsight application.

PX as a Source in Query Builder

Admins can now select PX custom events as one of the participant sources in the Query Builder source type. Admins can select this source to improve customer journeys based on usage data. Like any other source/object in Query Builder, admins can add show fields/filters based on the selected PX custom event and also perform merge/transformation tasks.

Note: Admins must first configure the PX Connector in the Gainsight CS application. For more information, refer to the Gainsight PX Connector article.

Business Use Cases:

• Admins want to track the users who viewed article 1 or article 2 in the last 60 days.
• Admins can find the list of users who used the new application more than 10 times in the last 30 days.

To configure PX as a source in Query Builder:

1. On the Participants Configuration page, click the +SOURCE button and select Query Builder.
2. Enter a name for the Query Builder source. 
3. Click SAVE.
4. Click DATASET TASK. The New Dataset Task page appears.
5. Select the name of the PX connection which you have configured.
   Note: By default, Custom Events is selected in the events dropdown.
6. Select the source product name for which you have configured the custom event.
7. Select the event.
8. Click and drag the fields that you want to query to the Show section.
9. Click SAVE to create a query based on all Event attributes, account, and user attributes.

Limitations: The following are some of the limitations in using PX usage data:

• The Date field is mandatory and it must be bounded such that you need to have a start date and end date.
• Only the data from the past 180 days is considered.
• Event level data is not supported. Gainsight always aggregates EventID to Count (EventID) when dropped in the Show section.
• Only 100K records are fetched per rule.

Horizon Report Builder in Journey Orchestrator

Horizon Report Builder is now available in Journey Orchestrator both as part of the email content as well as when mapping report tokens.

For more information on how to share reports through programs, refer to the Sharing Reports with Programs article.

Note: If a program consists of an attachment and the report is previewed, an ‘All attachments cannot be viewed’ warning message is displayed. To view the attachment, admins can either send a test email or even download the attachment.

Reporting on Journey Orchestrator Custom Fields

Journey Orchestrator custom fields are now available to generate reports from Report Builder as well as used as a source in Query Builder under the AO Participants Custom Fields object name. Previously, the custom fields mapped in the program were not shown in the Report Builder and in Query Builder. 

Limitation: The actual custom field names are not available in the object since it is common across programs. It has generic names such as String1, String2, Date1, and Date 2. However, admins can update the names in the Report Builder.

PX as a Source in Rules

Admins can now fetch custom event data including Account/User and Global context attributes for custom events from Gainsight  PX custom events and perform any actions in Rules Engine. In the Setup Rule screen, admins can select the PX Connection and Product Name, for which all the configured events are displayed for selection. Like any other source/object, admins can add show fields/filters based on the selected event properties and also perform merge/transform tasks.

To fetch PX usage data, admins must configure the PX Connector in the Gainsight CS application. For more information, refer to the Gainsight PX Connector article.

Limitations: Following are some of the limitations in using PX usage data:

• The Date field is mandatory and it must be bounded such that you need to have a start date and end date.
• Only the data from the past 180 days is considered.
• Event level data is not supported. Gainsight always aggregates EventID to Count (EventID) when dropped in the Show section.
• Only 100K records are fetched per rule.

Support of Load to Gainsight Object Action Type in Real-Time Rules

Real-Time Rules now supports Load to Gainsight Object action type to load data into Gainsight objects. This action type is designed with a new field mapping experience where admins have to first add the fields for which they want to map. This is to provide an optimal experience, performance-wise, when there are a large number of fields coming from the event.

Limitation: Currently, this action type only supports Insert operation on Low Volume Custom Objects.

Sally Quick Insights Upgrade

IMPORTANT: Customers who have access to Sally and are onboarded to new Horizon Analytics will only be able to access the upgraded Quick Insights in Slack.

Previously, admins had to create a separate Quick Insight report in the Administration > Quick Insights page. The report was then cloned from the parent report and created a duplicate report in Sally instance, which was accessible for Sally users. The major disadvantage of this procedure was any change that was made to the parent report is not reflected in the quick insight report and vice versa. Gainsight is now upgrading the Sally Quick Insights feature with the Horizon Report Builder to increase the adoption of Quick Insights in Sally.

In Horizon Report Builder, admins can mark a report as a Quick Insight in the following two ways:

• In the Administration > Report Builder (Beta) page, click the Context Menu of the existing report to be marked as quick insight and select the Mark as Quick Insight option.

• In the Administration > Report Builder (Beta) > Create Report, select the Mark as Quick Insight option while saving a new report.

After the report is marked as Quick Insight, the report is accessible to all the Sally users. Any modifications to the report immediately reflect on the new Quick Insight report requested by the user. 

Note: A warning message appears when an admin tries to delete a report that has been marked as Quick Insight. 

Only the users who have access to Sally in Slack are allowed to mark a report as Quick Insight.

In Slack, all the tabular reports can be downloaded in excel format and the remaining chart reports are available in image format.

Assign CTAs to other Gainsight Users from Slack

Users can now assign CTAs to other Gainsight users when creating CTAs through:

• Slack Slash Command
• Slack Actions
• Sally Menu
• Company Intelligence News Posts

Previously, while creating CTAs from Slack, users could only assign them to self or CSMs.

Note: Users can assign CTAs to any user irrespective of license type and must search with a minimum of three characters.

Beta: Scorecard Widgets Designed for Clarity and Efficiency

In addition to the new Horizon Analytics, we have also redesigned and improved the look and feel of scorecard reporting with Scorecard Widgets.

Note: Starting with this release, early access to Scorecard Widgets has been rolled out in a Beta phase to the existing Horizon Analytics preview phase participants.

Admins with access can now configure Scorecard Widgets through the new Visualization tab on the Administration > Scorecard page. The Visualization tab is powered by the Horizon Experience and designed to be intuitive as well as consistent with other reporting features in Gainsight.

The enhanced Scorecard Widgets have new capabilities and tools which are designed specifically for scorecard data.
 

The following are some of the major advantages of the new Scorecard Widgets:

• New and improved User Interface based on the Gainsight’s Horizon Design System.
• Enhanced and redesigned Scorecard Report Builder pages.
• Alerts for stale scores and exceptions in Reports and Dashboards.
• The ability to highlight and filter for stale scores and exceptions in Reports and Dashboards.
• Unique icons for scorecard groups and scorecard measures to make them easily distinguishable.
• Easily separate manual measures, automatic measures, and groups.
• Create reports directly from the Scorecard administration page.
• Easy to use drag and drop functionality to build reports.
• The ability to freeze column widths.
• The ability to view comments and the “Last modified date” field in separate columns.

For more information on the new Scorecard reporting functionalities, refer to Beta: Scorecard Widgets Overview.

Gainsight Introduces Success Plan APIs

Admins can now fetch, create (with or without Objectives), update Success Plan, and get Success Plan configurations using Rest APIs.

Success Plan helps admins capture, track activity, and share progress on the customers’ key goals using Objective CTAs and their associated Tasks, but not all teams who benefit from accessing Success Plan always use Gainsight. They might have systems of their choice and expect Gainsight to integrate better with them. Customers who have the development resources can use these APIs to build tighter and more customized integrations between Gainsight and other systems they use. These APIs give Admins the capability to integrate Success Plan data and build out these workflows in other systems. 

For more information on how to use these APIs, refer to the Success Plan APIs article.

Example Business Use Cases:

• Capture your customer’s strategic goals and easily share progress updates with them.
• Automatically trigger Success Plans at important milestones in a lifecycle to ensure proper hand-off from one stage to another.
• Create individualized Success Plans to track the progress of granular customer relationships for various products, departments, or locations.
• Monitor goal attainment and visualize your project progress with intuitive Gantt Charts.
• Track team performance against customer objectives by incorporating Success Plan metrics in your management dashboards.