New Environment Settings

For any application, there can be multiple subscription being used. Gainsight has introduced environment settings in PX. Environment settings in PX can be used to differentiate subscription by their usage type. You can use these settings while creating new Products in your subscription. You can also configure all of your existing products with one of the environment settings. 

You may be using various environments for your application. You can now associate the Staging PX product with your staging application, QA product with your QA application, and so on.  Once you complete this process, you can test how an engagement looks, on your staging application and then push it to your production application for customers to view it. Similarly, you can test other features in multiple environments before pushing them to your production environment.  

Send Request Data as POST Method

Gainsight PX now allows you to send data request payloads as a POST method. Previously, data was requested from an application via the GET method. POST was used only if the Payload size exceeded a certain limit. Gainsight now provides you the ability to use the POST method for all data requests, irrespective of the payload size. 

To use this enhancement, you must modify the PX tag with an additional line of code. The code is "usePOST" : true. When you append this code to the PX tag, all the data requests are sent as a POST method.

Advantages of the POST Method:

• POST requests are never cached.
• POST requests do not remain in the browser history.
• POST requests cannot be bookmarked.
• POST requests have no restrictions on data length.

New Java SDK

Gainsight has now introduced the Java SDK. This SDK is an alternate and easy way to use Gainsight PX APIs. With PX REST API you need to write the code that sends requests to the end point. However, with the SDK all the basic level configurations are performed automatically. The HTTP Request to the endpoint, the parsing of the response, etc., are automatically taken care of by the SDK.  With the SDK, you only need to use the specific API based on the data required and everything else is performed by the SDK. 

To use the Java SDK, you must have the PX API key of your PX subscription. To learn about the APIs provided by the Java SDK, refer to the Gainsight PX Java SDK article.    

Gainsight PX Launch Adobe Extension

Gainsight has now introduced the PX Launch Adobe extension. You can use this extension to automatically insert the PX tag code to your web applications. You can find the Gainsight PX Launch extension from this site. This extension is similar to Google Tag Manager, but is much more powerful and allows you to decide when exactly the tag must be loaded. This extension allows you to perform the identify call, without any coding. Before using this extension, you must create a Property for your application in Adobe Extension. Once you create the Property, you can easily store this Extension in your property. You must also have the product key of your PX product to use this extension. 

To learn more about the configuration of this extension, refer to the Install PX Adobe Launch Extension article. 

Send Engagement Data to Segment

Gainsight now sends data to Segment from PX, thus facilitating a two-way sync between Segment and PX. Currently, you can only send in-app engagement data from PX to Segment. The data is sent as custom events to Segment, by using Segment Track call. To learn more about Segment Track call, refer to this segment article. This enhancement allows you to send PX data to any third party application via Segment.

The existing Segment widget is upgraded with a new tab called Push To Segment. This widget pushes data from PX to Segment. The widget will continue to serve the existing functionality of syncing data from Segment to PX.

 

Before configuring the widget, you must create a Java based Source in Segment. Once you create the source, you must note down the Write Key of your source. This key is required to configure the Segment Push widget. To learn more about creating sources in Segment, refer to this Segment article.

To use this feature: 

1. Navigate to Settings > Integrations.
2. Click the Settings icon for the Segment Push widget.
3. Click the Push to Segment tab.

4. Turn the toggle switch on. 
5. Select a product from the Product drop-down menu.
6. Select an environment from the Environment drop-down menu.
7. Paste your segment source key in the Segment Key field.
8. Click Add.
9. Click Apply.

The engagement data from the selected Product and Environment is synced to Segment. You can create multiple sources in Segment based on the number of products and environments you have. However, a source in Segment can send data to only one destination and not multiple destinations. 

The engagement data from PX to Segment is sent as Custom Events. Currently there are two custom events that are sent; GPX In-App Guide and GPX in-App Survey. The GPX In-App Guide event sends data for a Dialog, Slider and Guide engagements. The GPX in-app survey event sends data for all the surveys (currently data is not sent for a Multi-question survey and Email engagement). 

The list of parameters sent by the events are:

GPX In-App Guide Event Parameters

Field Name	Field Value	Description
Type	Guide, Slider, Dialog
ID	String	GPX engagement ID
Name	String
Interaction	Viewed, Viewed step, Completed, Clicked
Step number	Integer	In case of an in-app guide, slider the field will be populated with the step number.
Activation	Auto, Bot, Badge, JourneyOrchestrator
Execution ID		Runtime id for the current engagement to allow for event grouping.
Execution date	Date	In addition to the event timestamp, this field is a unified runtime date for the current engagement to allow for event grouping by instantiation timestamp.

GPX In-App Survey Parameters

Field Name	Field Value	Description
Type	NPS®, CES, Boolean, Rating
ID	String	GPX engagement ID
Name	String
Interaction	Viewed, Viewed step, Completed, Clicked
Score	Integer	In case of score based survey, the value will be passed via the score field.
Score type	Promoter, Detractor, Passive	Relevant to NPS® only
User input	String	Represents user input/comment/open text questions
Activation	Auto, Bot, Badge, Journey Orchestrator
Execution ID		Runtime id for the current engagement to allow for event grouping.
Execution date	Date	In addition to the event timestamp, this field is a unified runtime date for the current engagement to allow for event grouping by instantiation timestamp.

Use Badge Icon Independently

Gainsight PX now allows you to use the Badge icon independently without associating it with any of the steps of the Guide engagement. With this feature, you can now launch a Guide engagement with just the Badge icon, and some Tooltip content, associated with the badge icon. Previously, it was mandatory to use at least a single step with Badge icon.

This feature is very useful when you wish to have permanent tooltips on your application. You can just create the Badge icon, add the Tooltip content and launch the Guide engagement.   

To use this feature: 

1. Create a Guide engagement.
2. Select Badge from the Trigger By drop-down menu.

IMPORTANT: 

• The newly introduced Use Badge Tooltip check box allows you to display or hide the tooltip content, associated with the Badge icon. If you clear this check box, the badge icon will not display the Tooltip content.  

• You can clear the Use Badge Tooltip check box only if you have at least one step in your Guide engagement. 

3. Click Save.
4. Click Edit Guide In-app to associate the Badge icon with an element on the application.

5. Modify the default Tooltip content and add the required content. 
6. Click Save.

7. (Optional) Use the text editors to format the Tooltip content. 

8. (Optional) Use the Edit option to change the badge icon, position, trigger method, tooltip position, as required. 

9. Click Save.

Note: You can also configure the Badge and Tooltip settings from the PX application as well.  

New "Copy to Clipboard" Button

Gainsight has now introduced a Copy to clipboard button in the Audience Rules Section of Engagements. 

When you click this button, all the values inserted in the rule are copied. You can paste the values into the Audience section of another engagement. This feature is also available in the Segment Rules.

Business Use Case: Consider that you have created an engagement and added around 50 Email IDs to which you wish to send the engagement. After a few days, you need to send another engagement to the same Audience. Instead of inserting the Email Ids again, you can just copy the Email IDs from the existing engagement and paste them to the new engagement.

IMPORTANT: 

• This button is displayed only when you add values to the Rules.

• This feature can only be used on Account and User Rules.

• The Copy to clipboard button is displayed only when you are using either:

  • A Custom attribute of the String Data Type from the User object. 

  • A Default or Custom attribute of String Data type from the Account object.

To use this feature: 

1. Create an Engagement.

2. Configure the Audience section, with the User and/or Account rules.

3. Click the Copy to clipboard button. 

4. Paste the copied values, to the required location.